— it might be the case that turning webGL off has similar symptoms. I haven't done much testing with that.
czar this thread has revealed that not all FPS are equal. 30fps with the strain on the GPU feels very different than 30fps on the CPU. The reason for this is dt variation.
C-7 Wouldn't that be more performance intensive though?
Apparently Chrome is a multi-process browser so this is normal. I dunno why, or if it matters
Develop games in your browser. Powerful, performant & highly capable.
Rable to be honest I don't know a lot about mobile devices. If you can show that your dt is varying wildly it's likely the same problem, but if it isn't the problem probably lies somewhere else.
Great job guys! Really enjoyed it.
Aurel collisions aren't the only thing hurt by this dt variance. It also makes the game feel like a nightmare to control, and be basically unplayable.
Ashley are you still looking into this?
Problem Description
An object with the bumpmapping shader will clip when on a layer that's parallaxed and rotated.
Description of Capx
Move around in 8-directions and use the <> keys to rotate the layout. Note the clipping on the bumpmap.
Affected Browsers
Operating System and Service Pack
Windows 8.1
Construct 2 Version ID
r184
Ashley the best way to produce GPU throttling is to render lots of low opacity fullscreen sprites. The window size will affect this test. In my lagIssue capx I do this and it throttles the GPU pretty effectively (interestingly though it doesn't create as much dt variance as a real game. Maybe shader use also has an impact?)
My observations also mirror — in that it seems to be pretty much hardware-independent.
Yeah, I notice bad performance particularly on integrated graphics, but that's probably just because they are weaker in general.
Aurel didn't you say that you had some events that reduced timescale to 0.8 when below a certain fps? Maybe that's impacting it a bit?
Whoa, Aurel's dt log is even worse than mine! 0.89 to 0.01? Madness!
So, at least I'm glad that there's a real issue, and it's not just all in my head!
Yep, totally agree. The problem definitely lies on the graphics side. Are you still sure it's a Chrome issue?
Member since 5 Sep, 2011