My old C2 (browser) game runs very slow with the C3 runtime. What could be causing this? (SOLVED)

Post reply
0 favourites
  • 8 posts
From the Asset Store
Building "Collapsing Blocks" Browser Games
$7.99 USD
This is a single chapter from the Construct Starter Kit Collection and the Student Workbook from the Workshop.
PBMCube's avatar
PBMCube

  • For the past three years I have been making my daughter an egg hunt game for Easter. I just loaded last year's game, made with the C2 runtime, into Construct 3 and everything is moving like molasses. Any ideas what could be causing this slowdown?

    My game consists of 10 scenes (each 1920x1080) and a dozen or so fairly large egg sprites. I am also fading the images to black using a large black sprite that covers the screen. Is it the large images?

    NOTE: I was able to switch to the C2 runtime and it's pretty much back to normal, but I was looking forward to a slight framerate improvement from C3... definitely not getting that.

    Here is last year's version, using the C2 runtime: cuttergames.com/egghunt_2018

  • I wouldn't mind taking a look at it if you want don't mind sending the capx but if not I can only suggest maybe change the max texture size in project settings?

    Btw, I played it and I thought I was going to try one level but ended up finishing it chickka rakka chikka boom

  • It seems to be running fine here. Construct provides tools for you to check performance and investigate why things are slow if you run the debugger and look at the profile tabs. That's the first place to go.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • john Cutter

    impossible to say without seeing your code...

    I wouldn't think the image size would be a problem.

    those are well hidden eggs! I found 8 before I decided I should get back to work...

  • It seems to be running fine here. Construct provides tools for you to check performance and investigate why things are slow if you run the debugger and look at the profile tabs. That's the first place to go.

    To be clear, the version I linked was using the C2 runtime.

    When I load that program and choose the C2 runtime, it takes 12.89 seconds for my text message to scroll up the screen and the next scene to fade in. If I then choose the C3 runtime, the same sequence takes 56.25 seconds. So I'm clearly doing *something* wrong.

    Okay, I just checked the debugger with both the C2 runtime and the C3 runtime. I'm not an expert but everything *seems* okay, except I did notice a big difference in CPU usage. During the text scroll:

    C2 RUNTIME: 60 fps and 92% CPU

    C3 RUNTIME: 26 fps and 1.8% CPU

  • I wouldn't mind taking a look at it if you want don't mind sending the capx but if not I can only suggest maybe change the max texture size in project settings?

    Btw, I played it and I thought I was going to try one level but ended up finishing it chickka rakka chikka boom

    Because of the music and large image files my .capx is HUGE. But thanks for the offer. If I can't figure out what's going on I may take you up on it. :-)

    You finished it??? I'm kind of surprised (and impressed) because I tend to make some of the eggs way too difficult (as in practically impossible) to find. Gonna be better about that with this year's version. Heh.

  • C3 RUNTIME: 26 fps and 1.8% CPU

    If you look in the profiler tabs you can get much more detailed information about both the CPU and GPU usage.

    However given the low CPU usage and low FPS, I would guess you have an older device that's in the few % of systems that get kicked down to software rendering. The C3 runtime only uses WebGL so presumably with the C2 runtime you're getting canvas2d rendering only (which is possibly hardware accelerated, since it has lesser requirements). Try installing any software updates or updating the graphics driver. Most modern devices should be fine. Assuming you're using Chrome you can get more detailed information by visiting chrome://gpu in the address bar.

    Also the framerate shouldn't affect the speed anything happens if you correctly use delta-time.

  • Thanks for the reply, Ashley! I really appreciate Scirra's customer support. :-)

    I use Chrome so I checked out 'chrome://gpu' and discovered that my hardware acceleration was disabled, for some reason. I went into my Chrome settings and turned it on, and now everything is working as expected. Thanks for your help!

    (Actually, I'm now getting the same framerate and performance with the C3 runtime, but I noticed that my CPU usage has gone down a LOT, compared to C2.)

Post reply
  • 8 posts
Return to board index
Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)