Windows 8 App performance vs IE 10 desktop

I'm in the process of testing a game I have created for the windows 8 app store. I've added a FPS and render method text to the app and see that desktop IE 10 is rendering canvas2d as expected. Also, the FPS is 58-60fps. When I export to windows 8 and run as an application I am only seeing 35FPS while everything is in motion.

Why such a big difference between IE10 desktop and IE10 in a Windows 8 App.

Please help.

Thanks.

<img src="smileys/smiley5.gif" border="0" align="middle" />

In theory it should be the same, but I think thehen is aware of some Win8 app bugs that cause poor performance. I think MS are aware of it and Windows 8.1 may fix it.

That's not what I wanted to hear. :-(

I was planning to present at a conference of Microsoft developers on building games for Windows 8 with Construct 2.

I guess I have to really trim back my game.

Does anyone know what specific features I would need to stay away from? I removed all the physics behaviors in an attempt to speed up but that did not yield much. I guess all I have left is to reduce the number of sprites.

Thanks.

do you test in visual studio ? I have a big perfomance drop when launching my app from visual studio but works good when launching from the start menu

BINGO! (And I don't mean BING+O)

Launching through visual studio was the problem. I'm back to the same performance as IE 10 on the desktop.

Thanks so much.

I hope Internet Explorer 11 uses WebGL could integrate webGL in Windows 8 app

Yeah, always test direct as an app as opposed to running through visual studio when gauging performance. VS does a lot of debug stuff that slows it down.

One quick note on this...I was helping another dev out during my Office Hours today, who was running into this perf issue, on a game using the Physics behavior.

Something that might not be obvious (I missed it initially), you can get the same improvement in performance even running from Visual Studio if you use the "Run without debugging" (Ctrl+F5) command.

Switching the build from debug to release won't help, if you still run in debug mode from VS.