I need your help to figure out Airscape's performance issues

Discussion and feedback on Construct 2

Post » Mon Mar 02, 2015 12:59 am

DrewMelton wrote:Is there no way to make this an option in-game like at an options menu?


Once in-game I don't think there's a way to change the renderer.

Would be good if we can toggle at runtime with WebGL on or off, like a -command line. That would be great for these situations.

Is there a way?
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Mon Mar 02, 2015 2:03 am

@Silverforce, you're right - it's not possible to change the renderer during runtime (unfortunately). See Ashley's response here.
A big fan of JavaScript.
B
74
S
20
G
69
Posts: 2,205
Reputation: 43,832

Post » Mon Mar 02, 2015 2:59 am

Turning off webGL is not a solution. Canvas2D is still slow, definitely too slow for my purposes.

I really can't believe that a high-end intel integrated GPU cannot run webGL at one third of the speed of a two year old tablet, or a five-year old budget mac. It's completely crazy if this is the case. If it's really just a hard limitation of webGL, then webGL is not suitable for games, period.

I'd really like to hear what @Ashley has to say about all of this.

I tried out some Unity webGL benchmarks and they seemed to perform well, although with no no-webGL reference point it's hard to say anything definitive there.

I can't just tell my users that they can't use integrated graphics. Everyone in this day and age expects 2D games to be able to run on the most basic of machines. When you factor in the GPU fallback problem, the situation becomes worse.
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Mon Mar 02, 2015 3:18 am

You'll need to collaborate with Scirra on this, let them test the capx examples on Intel graphics and see whats going on.. if its really an Intel problem, perhaps they can submit bug reports to Intel's driver team.

If its a C2 problem, then they can improve it.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,614

Post » Mon Mar 02, 2015 9:05 am

Silverforce wrote:You'll need to collaborate with Scirra on this, let them test the capx examples on Intel graphics and see whats going on.. if its really an Intel problem, perhaps they can submit bug reports to Intel's driver team.

If its a C2 problem, then they can improve it.


Hopefully it's the latter, as Ash has said it's pretty tough getting help from driver vendors :(

Browser vendors are far more receptive to bug reports than driver vendors BTW, so if you're worried about problems caused by third parties, driver bugs are a far worse and far more significant problem with native engines! I'll take the browser vendors any day...
"Construct 4 lets YOU make advanced games! (but not play them)" Construct Classic - Examples Kit Dropbox is a pile of trash and if you need my old files PM me! :)
B
116
S
41
G
17
Posts: 2,201
Reputation: 19,539

Post » Mon Mar 02, 2015 9:18 am

Yep. I tried talking to NVIDIA about the GPU fallback problem (They basically have a forum for bug reports) and it didn't get very far :(
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Mon Mar 02, 2015 9:37 am

I'm super sad for you, man.
I really hope you'll find something. Please keep us posted!
Image | @AurelRegard on twitter
B
19
S
6
G
1
Posts: 307
Reputation: 2,500

Post » Mon Mar 02, 2015 9:58 am

@Aurel have you ever noticed this problem? Or is your game simply optimized so well that it runs well even with this terrible performance? ;)
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Mon Mar 02, 2015 10:51 am

WebGL is up to 20x faster at per-sprite rendering on some systems, and in real-world examples can double the framerate. I can't remember ever testing a system that measured slower in WebGL mode than canvas2d, and I've tested a lot of devices! Normally the only reasons it could be slower are large, constantly changing text objects (which are slower in WebGL mode than canvas2d), or the extra work of running shaders. However there may be other reasons it appears slower. The graphics control panel tools that some graphics chips ship with (e.g. nVidia control panel) have the ability to override the rendering settings that applications choose. For example Construct 2 asks for a WebGL context with antialiasing disabled, but if you've modified the settings (or if the control panel has really stupid defaults) it might force it enabled, and for some reason not apply that setting to the canvas2d context. Antialiasing on a low end chip will completely murder performance, and then you end up with it looking like WebGL is a lot slower than canvas2d. So I'd double check all those settings.
Scirra Founder
B
395
S
232
G
88
Posts: 24,367
Reputation: 193,744

Post » Mon Mar 02, 2015 12:11 pm

@Ashley

The Intel HD Graphics control panel is pretty basic, but it did have an option to turn off anti-aliasing. I tried it and there was no difference, so the settings don't seem to be the cause of the problem.

Image

Anyway, I've tried four machines, one basically factory fresh, all with the same results. So I highly doubt it's a weird config issue. Do you have access to an Intel HD Graphics machine to test on?
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: Lof, mihirolover and 9 guests