It's odd because if you don't add a Windows 8 object under there, then you won't get any trouble over the project being in test mode, but if you add a Windows 8 object then the default for Test Mode is Yes and you can have trouble running the project once it's exported.

If you've added a Windows 8 object (under Object Types in the Projects tab) then you can set Test Mode to No.

Hi there. I'm Jeremy Foster (aka codefoster) and I work at Microsoft. I'm pretty new to game development in Scirra, so be nice when I ask questions. My focus is Windows 8 apps using HTML/JS, so hopefully I can offer some help in that area.

A friend of mine just published Angry Turds on Windows 8... made with Construct2.

BluePhaze, I think you're eligible, but I'm finding out for sure.

This is a very late reply, but I would set an expectation of a week. I've had apps take much less (less than a day!), but that can't be guaranteed.

There are only relatively subtle differences between the two environments and I would expect performance differences to be negligible. Some browsing of browser benchmarks that include IE10 (browser) and Windows 8 apps confirms this.

Actually, the IE10 performance is pretty great and the touch support is too. Check out ietestdrive.com and compare some of the demos there in various browsers.

I think accelerometer is fun to implement. It's sort of a novelty, however, in many games and you should definitely provide support for whatever input your user might be using. Actually your app will fail certification with the Windows Store if you exclude inputs. Rightly so too. If I downloaded a game and tried to play with my keyboard and mouse with no touch and it didn't work I would be disappointed.

FYI, VS2012 does target ARM processors. You can set your project to compile once for all processors (recommended), or if you have to create a different assembly for the different processors you can target just x86 or ARM.

It's been awhile. Did you get this resolved? There's a newer version of the WACK tool that's smarter than the old one and may help.

Here's the official statement as to why Windows 8 Store apps (which use the same engine as IE10) do not support WebGL...

blogs.technet.com/b/srd/archive/2011/06/16/webgl-considered-harmful.aspx

Regarding the 3rd and 4th points. The thing I like about the new design style is how simplistic it is. It gets out of the way and lets an apps design shine through. Windows up to Win 7 was developing its own style from the gray Windows Forms apps to the newer Aero styling, and with an explicit style choice like those, you never know if your style is going to be appropriate for the more than a billion different PCs that are running it. There's a big difference, for instance between contexts between a gamer and his PC and a businessman and his. The new design style doesn't really choose for you, so every app tends to look as good as the designer and developer chose. FWIW.

BTW, you should be careful with CPU detection. If you create a single app package that targets multiple CPUs, the certification process will make sure that all users have the same (good) experience. If you need to create different experiences for different processors, you need to create different packages per processor. Here's the way the certification requirements state it...

3.3 Your app must provide the same user experience on all processor types that it supports

If your app has a different user interface or functionality when it runs on different processor types, you must submit a separate app for each processor type and describe the differences in the Description of each app.

You can find all of the Windows 8 cert reqs here: msdn.microsoft.com/en-us/library/windows/apps/hh694083.aspx