Pshhh... I'm totally jerking Jokes aside... with all of the experimenting I've been doing with Insanity's Blade, I'm finding that it might be other issues and not C2/ExporterTypeX.
I'm saying this because I took a Windows 7-32bit machine with a 460gtx - all drivers up to date - replaced it with a way more under powered card 8600gt and blam - game went from unplayable to occasionally jerky (probably old 5400rpm drive and crap ram).
Then on my lunch break yesterday, I downloaded our steam build on my work machine. This is probably an early i5 with a 450s. Clean install of windows a couple of months back. I use it for work/unity. I was expecting the game to run bad as It's a pretty bare bones work station. Nope - 60fps - not one little hitch. All drivers up to date. Game ran smoother than on my i7 with 16gb ram and an GTX860m.
Clean install machines seem to run games in Node Webkit no problem - I bet it I installed a fresh build of windows 7 on my older machine, the game would run without a hitch. The problem is finding what app/drivers are causing the hitching. The old machine does it every half second. But you don't really notice it due to all the action on the screen.
I'll keep messing around with different machines - and obviously I'm going to get hit with the "your game won't run on my 10+ year old dumpster find, you suck, give me back my money!!!" Mails like when we posted the Demo and early access on Desura. Maybe these findings can at least prove useful to make a FAQ about frame rate issues and drivers
Oh - We also made a batch file to launch the game with node-webkit commands, this is clearly helping the frame rate:
--disable-threaded-compositing --ignore-gpu-blacklist --enable-zero-copy --disable-application-cache