Constant game hickup.

Bugs will be moved here once resolved.

Post » Tue Jun 04, 2013 12:42 pm

Closing, I don't think this is a C2 bug. Our old native engine sometimes dropped frames in windowed mode, because to v-sync 100% accurately means synchronising every 16ms to <1ms accuracy, and often OS tasks or other software steal just a little bit too much CPU time and it misses the sync. The visual appearance is one frame being displayed twice as long as it ought to (32ms instead of 16ms) every couple of seconds, which if you are watching with hawk eyes is just about noticeable as a "hiccup" or "jank". In real games like Space Blaster though, usually it's virtually impossible to notice, since the motion is slower and the contrast is lower. There's not much to be done other than boost the process priority. Going in to fullscreen (F11) might actually help, since the browser might boost its own priority when fullscreen, as well as closing all other running apps.
Scirra Founder
B
385
S
227
G
86
Posts: 24,146
Reputation: 190,845

Post » Tue Jun 04, 2013 12:56 pm

Thank you Ashley! Full Screen in browser on the PC fixed the problem!

I read that Android 4.1 fixes most of the problem because the VSync pulse is now used to start all the processing for the next frame.


Before I abandon this topic, can you please just give me a quick tip - How would I go on about fixing it on an Android 4.0 and below? The problem is visible there and that represents the majority of the android demographic.Xionor2013-06-04 13:04:05
B
10
S
3
Posts: 233
Reputation: 1,537

Previous

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 2 guests