Performance questions

Discussion and feedback on Construct 2

Post » Sun Aug 25, 2013 1:18 am

From https://www.scirra.com/manual/134/performance-tips and https://www.scirra.com/blog/83/optimisation-dont-waste-your-time

Game is freezing on some PCs for 1-2 seconds at a time (not a slow down of framerate, everything just stops for a second or two). Does this mean it's a processing/logic issue rather than a draw issue?

Object count affecting performance - does type of object matter here? For example, if I have dialogue or room layouts that are read into a 300+ separate arrays during initialization, does it matter at all?

Sound - is positional sound computationally expensive? [order of magnitude vs. normal sound?] What about 'stop all'? Wondering about sound optimization in general as one of the test computers cannot actually play the game unless sound is disabled. This is all via node webkit.

Thanks in advance!



B
9
S
3
Posts: 58
Reputation: 1,566

Post » Sun Aug 25, 2013 1:52 pm

Try the new profiler in r142 - it should help identify what is causing the long pauses. Note there was a bug in r141 which could cause poor performance in Chrome, so you should upgrade to r142 anyway if you're using that.

The object count's effect on performance depends entirely on what exactly you're doing. The best thing to do is keep an eye on things with the new profiler and see if anything's turning in to a CPU hog.

Sound is probably processed in parallel in a separate core, so is unlikely to affect the framerate.
Scirra Founder
B
387
S
230
G
87
Posts: 24,249
Reputation: 192,240

Post » Sun Aug 25, 2013 7:55 pm

@Ashley Yikes.. so going from v141 to v142 the node webkit .exe takes roughly double the amount of memory in task manager (from 200mb to 400mb). Do you know why that might be? I don't think anything else changed although now I've saved over my file like an idiot and am not sure if I can revert to the previous Construct version..

Debugger memory usage appears to be the same (50-60mb in images). The new profiler tool is really awesome btw! Wish I could see what draw calls are occuring because it takes up nearly 20% CPU when nothing on the screen is moving.. that seems wrong right? I have bad code that is telling the game to redraw something it doesn't need to draw?

Thanks so much for your help. ^^
B
9
S
3
Posts: 58
Reputation: 1,566

Post » Mon Aug 26, 2013 7:21 pm

Did anyone else see their memory usage bloat with node webkit's exe after moving from r141 to r142? I've reverted to a previous build since the memory usage increase was persistent and significant across the few computers I tested on.
B
9
S
3
Posts: 58
Reputation: 1,566

Post » Sat Aug 31, 2013 6:03 pm

Bump to the top with another performance question.. hard for me to test these things personally because my computers still function okay with the game.

Has anyone else seen a spike in RAM usage with the new Construct version when exporting to node webkit?

Also for collision detection, does checking distance before the collision detection help or does that add even more computational strain? (e.g., 50 bullets flying around.. turn off collision for things that are: distance(bullet.x,bullet.y,player.x,player.y)>200?

B
9
S
3
Posts: 58
Reputation: 1,566

Post » Mon Sep 09, 2013 1:36 pm

@Agni file a bug
B
12
S
3
G
1
Posts: 347
Reputation: 2,866

Post » Mon Sep 09, 2013 11:50 pm

I feel 143 is too buggy :(
B
12
S
3
G
1
Posts: 347
Reputation: 2,866

Post » Wed Sep 11, 2013 12:52 pm

I cant debug on mobile and my game hangs up for several seconds after you click play and gameplay starts. It works fine for 5 seconds or so, then there is 5 second pause and gameplay resumes normally. Its terribly hurting game quality.

m.blackmoondev.com/rrh

Compiled with 139PKrawczynski2013-09-11 12:57:54
B
22
S
7
Posts: 94
Reputation: 1,783

Post » Sat Sep 14, 2013 5:22 pm

Can mobile web performance be looked into?
I wouldnt mind sending Scirra employes zip file with game so they could look whats going on and why iphone/ipad have terrible performance.
Just give me email where it would be apriorate.PKrawczynski2013-09-14 17:23:06
B
22
S
7
Posts: 94
Reputation: 1,783

Post » Sat Sep 14, 2013 5:50 pm

I was doing some different tests as well. On Windows 7, via Chrome and Node Webkit, the game runs great (using C2 143). On Windows 8, via Chrome and Node Webkit, it runs like a dog. Horrible horrible lag. A difference of 30 frames per second between the two.
B
14
S
6
G
1
Posts: 143
Reputation: 1,795

Next

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 10 guests