OK.... I'm going to find time this evening to check this out! It's looking good!

The inspector is ace for everything but performance measurement - although the profile tab is awesome for identifying dirty events. That's why I always use a debug text object with a huge list of set-text options that I toggle enabled when required.

If cycling through an array hurts at 60hz, how will the owner of a 144hz monitor fair? I don't have the luxury... Might see if my TV is 100hz when I get home.

!

I guess a browser back in focus check will be required to negate this....

You can import sprite sheet animations from Toon boom into C2. However, IMO, you're better off using Spriter - I last tried Toon Boom a couple of years ago but, after discovering Spriter I haven't looked back. The plugin has been developed by Brashmonkey in consultation with Scirra, so you can drag your work directly into the C2 editor. It's not perfect but if you're a one-person team then it's probably way good and powerful enough.

Your numbers are very likely wrong.....Chrome will happily use up 100% of the cpu if you give it that much work.

My numbers were wrong because I was reading from the App Running section of the Task Manager; it was late and I was tired . Chrome was actually demanding nearly 14% of my CPU when the in-game in-thread time was indicated as 60% cpuutilisation. Since making the first post I have already reduced the amount of array work being done at little cost visually to the game, but there is still room for improvement.

Some good notes in the blog - I will re-read (and try to digest) it! Just to prove that I'm not going bonkers - here's a screen shot from my game (not the demo - the array work happens on a later level and the cpu use in the demo is low). This shows 2 modes of 2 graphics processors in use - normal and max'd out. As you can see,the use of Chrome sits at approx 15%; as Ashley says, there's no easy way to determine how much of which core is being allocated to the game, but it might be reasonable to assume that, with 4 cores and 8 logical processors, that one of those logical processors is being fully utilized. I never expected a little array work to cause so much pain! As you can see, the idle and max'd out values are better when not using intel integrated graphics...

Thanks everyone for the responses and thoughts - some good refreshing of stuff I should have already known, and a lesson about Intel integrated graphics...

... when i test my game in windows phone browser it performs better than chrome on my desktop... :p

! This is so disappointing, yet somehow hilarious...! Html5 is such a good idea but never properly embraced. I hope that W10 & Edge & universal apps perform as well as IE11 does now...

Essentially, C2 is single threaded for the most part, all that logic uses 1 out of 8 threads on your i7 CPU. It can max out on 1 thread, when it shows 99% CPU use, the game will bog down and frames will be dropped, regardless of your GPU....

Also if you want gamers to play it on Intel HD graphics, don't use WebGL shaders....

This and your following advice are gold. I hadn't really NB'd the implications of this limitation before. Luckily I think I'm going to get away without using shaders - only lots of blend modes - but the 50% max is good advice.

So, let's hope W10 provides what it promises, or it'll be a long wait for hardware to improve so Chrome really becomes viable...

rekjl, I'm not sure what to make of it really - the point that causes me consternation is the browser demands almost a negligible amount of computer cpu time - even when it's in focus and the user is doing nothing else - but it allows the game to become max'd out with jank etc because the allocated cpu time for the javascript is not enough... Now, this might just mean that things cannot be done faster on one thread in javascript, which doesn't bode well for the future of html5. If that's not it, I just don't understand the philosophy behind the design and wandered if anyone could shed light on it or thoughts on if it's worth a discussion with google. My my public maths, using intel HD4600, my game is allowed to jank in chrome because of cpu demand even though the computer has 98.8 cpu available (I know, probably not accurate even though it's from the task manager, but you get the idea).

Just to expand on the above. I have been testing on a reasonably powerful laptop (i7, GTX 870 with 6GB / Intel HD4600 3.4 GHz) all of my previous testing was done using the HD4600 (I want the game to run well on average hardware if possible). However, changing to the run the game with NVidia card support, when running NW and Chrome, the game does not suffer any CPU spikes or slow-downs... which implies that the browser is able to offload some of it's work to the more powerful GPU, enabling it to handle the array functions without a hitch. Not what I expected as other indications are that my intel card is supported by chrome. So the lesson is to tell game playing customers that they need to own high-powered hardware, I guess... :/

I have a question regarding cpu utilization. I realize that this might be better directed right at Google, and they will be my next port of call - but before I (as one man with limited technical experience in this field) ask a multi-billion dollar industry leader to consider making changes to their browser, I need to check my understanding of what goes on under a browser's hood...

When I monitor my in-game CPU utilization using events I find there are occasional spikes (on my laptop) greater than 50% and that these correlate to lots of stuff happening as can be seen in the Javascript Console / Timeline - most of them are my own fault so I have been working hard to optimize my events and layouts. Spikes above 75% tended to be accompanied by drops in framerate, not GPU related - data manipulation in an array is my suspect here because, when I turn those events off, cpuutilisation reduces markedly. I can't do without the array data crunching (well, I would rather not...) so I need to work around this limitation. One thing struck me as rather disappointing - with a cpuutilisation value of 75%+, my Chrome use of my laptop's CPU was just 1.2% and didn't noticeably change when my game became more demanding and started to jank. My game was using 75% of 1.2%!

Has anyone else noticed this / does anyone care / have any suggestions? My thoughts are that Chrome should be capable of simply demanding more CPU access when running a demanding game, so games like mine can run all of their data processing unimpeded. Perhaps a game maker could raise a flag to permit this to happen. Am I being naive - is Chrome's access to processor time controlled by Windows or can it demand more if it needs it.

OK MadSpy,

After a rather large amount of heartache and poor maths, I have managed to create the following (still undergoing tweaking, but you'll get the idea):

There are still a few more fine adjustments I think I can make to this... I'll let you know when it's done!!

MadSpy

lol. I am trying to create a gradient effect but I'm having CPU utilisation issues....

Problem Description

If your browser window loses focus (by clicking on another tab / open program) whilst you have a key pressed then, on becoming focused again, the engine registers that the key is still pressed even if it is not. The problem becomes rectified after you press then release the same key again.

Attach a Capx

capx

Description of Capx

The capx contains an object that can be moved left and right by holding down the arrow keys, using events.

Steps to Reproduce Bug

• Hold down Right arrow key and, with the key still pressed, change desktop focus - then release the arrow key
• Return to the browser window and observe the object is still moving right
• Try pressing Left arrow key and then release (+ observe object stops moving) then press the Right arrow key again - and observe that, when you release the key, the keydowns are subsequently correctly sensed

Observed Result

As per above.

Expected Result

When the layout's browser is in focus, all key-is-downs should be correctly sensed irrespective of their condition when the browser lost focus.

Affected Browsers

• Chrome: (YES)
• FireFox: (YES)
• Internet Explorer: (YES)

Operating System and Service Pack

W8.1 x64

Construct 2 Version ID

r206 64 bit