Don't Miss Out

Follow us now so you don't miss new releases!

Construct 2 Release r142

There is a more up to date Stable Release! Download the latest Stable release instead here.

118.9 mb, Windows 8/Windows 7/Vista/XP

Wednesday, August 21, 2013

New this build: a 'Profile' tab in the debugger, and more debugger improvements!


Profiling means inspecting the performance of some software to identify which parts are the slowest. It displays the CPU time spent running events, broken down to each event sheet and further down in to each event group; the CPU time spent in the physics engine; the CPU time spent on issuing draw calls (i.e. how much time the CPU spent telling the GPU what to do - the GPU still does the actual rendering, but just issuing draw calls can often use a lot of CPU); and the remaining time spent in the Construct 2 engine. Here's what it looks like reporting on Space Blaster:

Construct 2 r142 profiler

This helps us quickly see that although the overall CPU usage is low (so there's not a real problem here - remember don't waste your time), at that moment the most CPU consuming events were in the bladeenemy sub-group of the enemies group. So if performance was a problem, that would be a good place to start looking at optimising.

Remember the profiler only shows you what the CPU is doing. Unfortunately it's not possible to retrieve the time spent by the GPU rendering anything, so it's possible the framerate is limited by GPU rendering, which would not show up anywhere in the profiler. The best way to spot that case is if both the framerate and overall CPU are low, you're probably bottlenecked by rendering. On top of that, the 'draw calls' measurement can be misleading in some cases: some browsers will try to complete rendering in that time, making it higher; others will simply forward all the calls to another thread then continue with the rest of the code, meaning it's doing the same amount of work, but the value will measure as a lot less (since it didn't spend much time in the current thread). So remember the measurements may not be exactly accurate.

The profiler is only available with a license. Another reason to upgrade from the free edition!



Debugger: new Profile tab (licensed only)


Debugger: highlights the instance currently being inspected in the game, with a dotted red outline and occasional flashing. This can be disabled (using the 'Highlight' checkbox under the new 'Tools' section) if it is distracting.


Debugger: 'Destroy' button to destroy inspected instance in the new 'Tools' section


Debugger: if a value is edited it is now highlighted in bold. Note if the value changes in the game, it un-bolds it. However this is useful for tweaking values and being able to quickly see which ones you've changed.


Debugger: new 'Container' section with links to other instances in container with the inspected instance


Keyboard shortcut: Ctrl+F4 to debug project from first layout


New 'Falling blocks' advanced example, which makes use of recursive functions.


New experimental 'Water background' shader


Experimental live twitter feed to start page - let us know if you think this is distracting/annoying/useful


Debugger: now can save and load while paused


Node-webkit: updated to v0.7 (based on Chrome 29)


r141's change for testing strings case insensitively turned out to perform appallingly in Chrome. The change has been reverted, but should still create slightly less garbage than pre-r141.


Turret behavior: improved accuracy of predictive aim when targets first enter range


Node-webkit: Browser 'Close' action now calls window.close() instead of App.quit() which should hopefully avoid some crashes on close


Debugger: Physics CPU measurement moved from System inspect to Profile tab

Bug Fix

Javascript error debugging a layout with no event sheet set

Bug Fix

Fixed broken 'Touch - zooming' example

Bug Fix

Sprite: animations could get stuck after using save/load


dodo021 5,814 rep

Very nice update ! Thank's Scirra team !

Wednesday, August 21, 2013 at 5:52:00 PM
piszozo 3,386 rep

thank you for your hard working on C2. <3

Wednesday, August 21, 2013 at 5:53:41 PM
Squid 5,575 rep

Great work. Keep it up.
Have a great day.

Wednesday, August 21, 2013 at 5:56:09 PM
mammoth 9,706 rep

The debugger was already awesome and now it's even better! Thanks!

Wednesday, August 21, 2013 at 5:57:44 PM
firebelly 7,294 rep

Love this!

Wednesday, August 21, 2013 at 6:03:00 PM
zenox98 62.9k rep

Twitter feed should be configurable so we can choose to see it or not. I quite like the start page but have no interest in seeing a twitter feed.

Wednesday, August 21, 2013 at 6:09:18 PM
Kyatric 76.0k rep

Great update overall.
I have to agree with zenox98, since I already have a twitter feed in one of my browser's tab opened most of the time (and I'm already a Scirra follower), it kind of acts as a double-use in my case, and will also mean that C2 will make regular "updates"/use some bandwidth to check for the feed which I'd prefer it not to (especially considering most of the time I spend very little time on the start page even if it is still active in background once I'm started/I've opened the project I'm working on).

Wednesday, August 21, 2013 at 6:13:56 PM
ArcadEd 22.2k rep

I gotta say guys, this debugger is nothing short of incredible. Thank you.

Wednesday, August 21, 2013 at 6:14:45 PM
bon4ire 6,078 rep

Thanks a bunch!

Wednesday, August 21, 2013 at 6:16:44 PM
alextro 24.7k rep

Now I have too much to see on debugger, which is good? :)

Wednesday, August 21, 2013 at 6:29:26 PM
sosensible 10.3k rep

I really appreciate the working on the debugger it is great

Wednesday, August 21, 2013 at 6:49:59 PM
wizsg 2,207 rep

Great job guys!

Wednesday, August 21, 2013 at 6:58:12 PM
Nickydude 11.3k rep

Never use Twitter and you also have a link already on the Start page so i'd suggest nice try but no thanks.

Wednesday, August 21, 2013 at 7:08:54 PM
aerirprown 3,645 rep

Profiling looks very useful. Great update.

Wednesday, August 21, 2013 at 7:23:12 PM
SergioRM 6,968 rep

Magnificent work! even better than before. What's next?

Wednesday, August 21, 2013 at 7:24:49 PM

Leave a comment

Everyone is welcome to leave their thoughts! Register a new account or login.