Designing Games or Windows 8 Digested


Here is a breakdown of the content presented in the video 2-106 : Shai Hintz : Designing games for Windows 8  from Build:

N `NOÄ
Windows 8 Input Specs

Often referred to as  accordance, hardware interaction with the user in the Windows 8 OS can be selected from the collection of:

  • At least 5 touch points (many with 10)
  • Sensors
  • Accelerometer
  • Gyros
  • Inclinometer
  • Compass
  • GPS
  • Camera
  • Microphone
  • XBOX Controller (via USB)
  • Light Sensor

Sensor Fusion

Combines the accelerometer, gyros and inclinometer to give a really precise (high granularity) input to work with augmented reality. Possible uses Sensor Fusion, are using a SHAKE gesture (shaking the  device) as a method to convey  struggling or escaping, or to use it a movement indicator to use the device as a window into another universe (virtual reality) ..(this reminds me of Alice’s mirror, or the dimensional window in Fringe)

Use the Platform

The default perspective for most apps is Landscape including Portrait support is optional, however in order to actually get certified for the windows store, you MUST support these interactions:

  • Snapped
  • Fill
  • Full

Rotate

Rotation is the process of going from Portrait to Landscape this is handled by the OS itself. when the player rotates the device you want to make sure it doesn’t effect the game play, one way to solve this is to pause the game.

OS events

There are a lot of events that can be thrown by the OS that may interfere with the experience of play for the user. Events such as: Loss of Focus, Loss of View the the Escape Key being pressed are naturally handled by pausing. Other events may need special consideration.

Pause

Make sure that pausing the game doesn’t effect the outcome of the game

Roaming

When the player starts to uses their device (tablet, PC, Phone, etc..) you will want to ensure that you properly manage the state as it goes thru the applications processes life-cycle  (Process Life-cycle Management or PLM) . Using checkpoints and background game play saving, as well as incorporating and planing for normal game states can give the user a good experience. One of the views of Microsoft that they have been very consistent on is that in Windows 8 the  play-pause-resume experience needs to be fluid and seamless across devices. What this means to a developer is that the game-play must be continuous across devices and feel ‘seamless’. One nearly necessary aspect of roaming is having consistent settings and options across devices, by leveraging the federated ID provided by the OS.

Control Schemes

Try to use as many control schemes as possible. for example in a FPR you could use mouse-look using the touch counterpart touch-look (examples C++, C++ & XAML). On a touch device the rt click is on by default. You can map input schemas such as click-to-go to tap-to-go rather readily. Some of the sample games such as Marble Maze use all of the inputs (scaled for sensitivity).

Menus

Command Windows Phone Touch tablet Keyboard Game controller
Play/resume “Play” button “Play” button “Play” button/ menu option Play item/option, triggered with (A) button
Game-mode to Menu-mode (pause) Physical Back key Swipe-in from top or bottom edge Escape key Physical pause button
Navigate in menus Touch taps Touch taps Arrow keys, enter key to select mouse clicks Digital D-pad
Previous menu Back control Back control Backspace key Escape key can work in addition Back(B) button

Player Accounts

You can get player accounts by connecting to gaming services, which has added benifits to your app such as tracking players progress, linkage to social networks and sharing, access to friction-free commerce.Also note that in some situations it can be helpful to leverage skydrive to pass larger pieces of information between devices

Game Code

Keep your game code abstracted from specific hardware configurations, having a layer of abstraction between the hardware and your game engine will make it easier to apply your game across form factors and devices.

References

3-107 : Chas Boyd : Core technologies for Windows 8 games (digested)

2-106 : Shai Hintz : Designing games for Windows 8

3-111 :  Justin Saint Clair : Gaming reimagined: Gaming case studies

2-106 : Shai Hintz : Designing games for Windows 8 (digested)

3-046 : Sam George/Ross Odwyer : Windows Phone 8: Native C/C++ Game Development (Havok)

Advertisements

About Larry Louisiana

I'm a Microsoft Partner Consultant.
This entry was posted in Computers and Internet, Controller, Digest, Graphics, News and politics, Programming, Sensors, Touch, User Interface (UI), Windows 8 and tagged , , , , , , . Bookmark the permalink.

One Response to Designing Games or Windows 8 Digested

  1. Pingback: Three Paths … | Ely Bob's space

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s