Low FPS in C2 games is more crippling than it should be?

Discussion and feedback on Construct 2

Post » Sat Oct 18, 2014 1:32 pm

Throttling data, on desktop computer:
Chrome v38: 10-20 rects
Firefox v33: 40-50 rects
IE v11: 50-60 rects
ImageImageImage
B
71
S
21
G
231
Posts: 3,691
Reputation: 129,358

Post » Sat Oct 18, 2014 7:39 pm

Ashley wrote:BTW I tried that test in IE11 and the dt variation is sometimes much smaller (22-24ms) but it still looks pretty bad on the motion. Are actual games any better or worse in IE11? (I think a bug report with a title like "Chrome does X worse than IE11" should get their attention - it's worked before :P)


Subjectively, I've always noticed that IE seems 'smoother' than chrome/firefox, even if chrome/firefox is reporting lower cpu usage/higher frame rates. I haven't tested many other people's games in IE, but I've tested a number of my own projects.

It would be nice if there was some way to indicate to browsers that a page should be run in 'high performance mode', ie, long GC delays should be avoided if at all possible, display performance takes priority, and all logic should be compiled to the highest efficiency code possible, ASAP (preferably on another thread, like IE does).
Don't lose your work. Backup your game with Dropbox.
B
44
S
10
G
10
Posts: 1,106
Reputation: 9,202

Post » Sat Oct 18, 2014 9:03 pm

@blackhornet - you should report the min/max dt at 45 FPS, is that what your data is?
Scirra Founder
B
395
S
232
G
88
Posts: 24,371
Reputation: 193,762

Post » Sat Oct 18, 2014 9:23 pm

Chrome: 7 - 50ms
Firefox: 20 - 25ms
IE: 15-30ms

This is at around 50 rects on all browsers (60-70 for IE actually) I didn't check if any of the browsers are using the GPU (I'm on a dual GPU machine) but I don't think they are.
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Sat Oct 18, 2014 9:30 pm

On my laptop, Intel HD4600,

Chrome v39 (beta), 22.1 to 25.5 ms
Firefox v33, 16.4 - 31.3 ms
IE 11 v 11, 20.8 - 26.2 ms
A big fan of JavaScript.
B
74
S
20
G
69
Posts: 2,208
Reputation: 43,838

Post » Sat Oct 18, 2014 9:53 pm

Hmm, interesting results from @Colludium - Did you every try it out on Chrome 38?

Something else I'm a little worried about is that this test doesn't account for the significant input delay that I also experience when this GPU lag is happening. @Ashley, could you ever reproduce that?
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Sat Oct 18, 2014 10:17 pm

@sqiddster

I tried to revert but v39 is now the latest release. It's worth adding that I'm running the x64 version of chrome. Here are my complete chrome beta / stable results:

Chrome v39 (Version 39.0.2171.27 m (64-bit))
19.1 - 25.2 ms; however, there are spikes to a max of 39.7 ms every 5 seconds (lasting 2 seconds)!!

Chrome Beta (Version 39.0.2171.27 beta-m (64-bit))
19.3 - 25.7 ms; the same spikes to a max time of 43.1 ms every 5-6 seconds (lasting 1-2 seconds).

Edit to add - judging by the version numbers, it seems that I should expect very little difference between these tests (QED).

Mmmmmm!!
A big fan of JavaScript.
B
74
S
20
G
69
Posts: 2,208
Reputation: 43,838

Post » Sun Oct 19, 2014 12:05 am

Actually while Chrome 38 gives me a terrible dt variation (typically 8 - 45ms), Chrome Canary seems a lot better, ranging only 21-24ms. It also subjectively looks better - it's not perfectly smooth in Canary (obviously, since at 45 FPS there's no choice but to skip some frames), but it doesn't have the eye-straining extreme juddering which Chrome 38 has with its wide dt variation. So it may be that it's already been fixed and we only need to wait for Canary to come through (currenty v40).

Can anyone with affected games give them a spin in Canary and say if it seems any better? You can install it side-by-side with normal Chrome: https://www.google.co.uk/intl/en/chrome/browser/canary.html

Canary might have also improved the input latency so you can test that with it too.

BTW in the test I posted earlier the rectangle count is completely irrelevant, it's only aimed at measuring the dt variation.
Scirra Founder
B
395
S
232
G
88
Posts: 24,371
Reputation: 193,762

Post » Sun Oct 19, 2014 1:46 am

Canary showed a definite improvement, both ingame and in the throttle test.

There are still some severe issues though - I get a lot of spikes and jerkiness even at relatively high FPS's, and the input lag definitely isn't solved.
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Sun Oct 19, 2014 2:05 am

As Squidster mentioned, disabling webGL greatly improves performance. I tried it and it helped a lot. Is that an issue with webGL or is it because effects are disabled? I'm using Chrome version 38 with Windows 8.1 32 bit.
Image
B
20
S
4
Posts: 382
Reputation: 2,974

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 32 guests