Developing Smartphone Games

[Andy Sjostrom]

<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmtphn/html/smartphonegames.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmtphn/html/smartphonegames.asp</a><br /><br />I recently wrote an article for Microsoft Developer Network (MSDN) on the subject of Smartphone development, <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmtphn/html/smartphonegames.asp">"Developing Smartphone Games"</a>. If you are interested in how to avoid common Smartphone development pitfalls, you should check this out. I turned to Sven Myhre, CEO and developer at <a href="http://www.amazinggames.com/">Amazing Games</a>, to get some inside knowledge about writing efficient games.<br /><br />"How do you use your normal vectors? Are they used primarily for light calculations or visibility testing? I use a 2:8 fixed point format for my normal vector components, meaning I have a full -1.99609375 to +1.99609375 range available, with a 0.00390625 resolution. In other words, I have 8 bits of fractional resolution to cover a full 360 degrees with 1.4 degrees resolution. On a tiny screen like 176x220, no one can tell the difference if a point is lit with a (worst case) +/- 0.7 degrees wrong direction to the light. The benefit is that I can store both x, y, and z components in a singe word."<br /><br /><img src="http://www.pocketpcthoughts.com/images/smpdev_01.jpg" />

[Cardie]

I'd like to point out that all the fancy graphics ain't gonna cover up a crap game. Games such as Defender from the early eighties have survuived through gameplay, not just nice graphcis and ray tracing. Developers need to make sure they get the balance right, and perhaps bias the gameplay instead of the gfx slightly at the design stage.

[Andy Sjostrom]

I'd like to point out that all the fancy graphics ain't gonna cover up a crap game. Games such as Defender from the early eighties have survuived through gameplay, not just nice graphcis and ray tracing. Developers need to make sure they get the balance right, and perhaps bias the gameplay instead of the gfx slightly at the design stage.

You bet! That is 100% true!

[isrjt]

I have been wondering when you were going to post on this. I read it a few days back on msn. Thanks for bringing the technical developer stuff to this site.

[felixdd]

Graphics always come second to gameplay -- and most game developers know that. Some just get caught up with adding every little detail they begin to neglect gameplay -- an easy pitfall to get caught in.

But the screenshots look like mechwarrior....&lt;drool>...want mechwarrior....need mechwarrior...&lt;drool some more>

[ironguy]

"How do you use your normal vectors? Are they used primarily for light calculations or visibility testing? I use a 2:8 fixed point format for my normal vector components, meaning I have a full -1.99609375 to +1.99609375 range available, with a 0.00390625 resolution. In other words, I have 8 bits of fractional resolution to cover a full 360 degrees with 1.4 degrees resolution. On a tiny screen like 176x220, no one can tell the difference if a point is lit with a (worst case) +/- 0.7 degrees wrong direction to the light. The benefit is that I can store both x, y, and z components in a singe word."



It all becomes clear now...

No wonder I can't beat these games.

[suhit]

Before I post the link that I am about to post, I would like to say that I agree that good graphics aren't necessarily going to make a good game. However, a mediocre game may sell well due to very good graphics.

Anyways, I do like Fathammer's (http://www.fathammer.com/) XForge3D (http://www.fathammer.com/x-forge/products/products_engine.shtml) game engine. Plus it is supported on multiple OS/platforms -
Symbian OS™
Microsoft® Smartphone
Microsoft® Pocket PC
Palm OS® (version 5.x onwards)
Mobile Linux
(No, I do not own stock in the company :wink:)