How to make a game using what you already know Chris Gardner Senior Software Engineer T & W Operations, Inc.

Page Source: Image Source:

Page Source: Image Source:

Page Source: Image Source:

 Windows Store Apps  80% C# / WinRT  14% WinJS  6% Native

 Windows Store Apps  80% C# / WinRT  14% WinJS  6% Native  Source

 Windows Store Apps  80% C# / WinRT  14% WinJS  6% Native  Source  Undisclosed Page Source: Image Source:

Page Source: Image Source:

What do we really need to make this work as before Page Source: Image Source:

 Player Controlled Sprites

 Computer / AI Controlled Sprites

 Player Controlled Sprites  Computer / AI Controlled Sprites  Interactions

 Player Controlled Sprites  Touch  Computer / AI Controlled Sprites  Interactions

 Player Controlled Sprites  Touch  Mouse  Computer / AI Controlled Sprites  Interactions

 Player Controlled Sprites  Touch  Mouse  Keyboard  Computer / AI Controlled Sprites  Interactions

 Player Controlled Sprites  Touch  Mouse  Keyboard  Controller  Computer / AI Controlled Sprites  Interactions

 Player Controlled Sprites  Touch  Mouse  Keyboard  Controller  Computer / AI Controlled Sprites  Event Driven (Button Press)  Interactions

 Player Controlled Sprites  Touch  Mouse  Keyboard  Controller  Computer / AI Controlled Sprites  Event Driven (Button Press)  Time Driven (Automatically Created)  Interactions

 Player Controlled Sprites  Touch  Mouse  Keyboard  Controller  Computer / AI Controlled Sprites  Event Driven (Button Press)  Time Driven (Automatically Created)  Interactions  Collision Detection

 Player Controlled Sprites  Touch  Mouse  Keyboard  Controller  Computer / AI Controlled Sprites  Event Driven (Button Press)  Time Driven (Automatically Created)  Interactions  Collision Detection  State ( Score and Lives )

Kool Aid is Awesome Page Source: Image Source:

Do NOT do a Google Image search for “Binding”

Let’s do this…

 IT WORKS!

 Too many things on the UI Thread

 IT WORKS!  Too many things on the UI Thread  INotifyPropertyChanged must be called on UI

Let’s bend the rules a little Page Source: Image Source:

 Premise  Run everything you can in the background  When necessary, send small commands to UI

Because, who doesn’t love threads calling threads…? Page Source: Image Source:

 Cleaned up UI Thread  Added a LOT of complexity  Locks  await / async calls

Who needs rules, anyway? Page Source: Image Source:

 NOTE: This code is still in “BETA”

 By that, I mean the code runs so fast, the game is slightly unplayable…

Factory Smoke NOT Included

Thank You Chris Gardner