Beta versions are not as thoroughly tested as stable

Beta versions are not as thoroughly tested as stable

Beta branch

Construct 3 r436

Updated preview menu; new example; bug fixes

22 April, 2025 ()

Email Me New Releases

Don't miss out on the latest and greatest new features in Construct 3

Notes

This week's beta release includes a couple of smaller improvements and a batch of bug fixes. The preview button menu in the main toolbar now has options to add another preview, i.e. opening a second preview window. This is particularly useful for multiplayer projects, and was previously only accessible by a keyboard shortcut (holding Alt). The Multiplayer object can now also send binary messages much like the script API can - note this is different to binary transfers, as sending a single message is subject to maximum message size limits, but can also be sent with different transmission modes like unreliable mode.

Other than that there's a range of bug fixes, including for flowcharts, timelines, and a regression in the WebGPU renderer. We've also got a fun new example Bewitched torches. Happy testing!

Like this Release?

Let us know with a thumbs up!

UpvoteUpvote 22 DownvoteDownvote
Launch r436

Changelog iconNew Additions

Not favoritedFavorited Favorited 9 favourites
Main toolbar: add options to start an additional preview window to preview button dropdown
Not favoritedFavorited Favorited 4 favourites
New example 'Bewitched torches'
Not favoritedFavorited Favorited 9 favourites
Multiplayer: send binary messages from event system

Changelog iconChanges

Not favoritedFavorited Favorited 9 favourites
Improve error logging if opening a project with a corrupt image file

Changelog iconBug Fixes

Not favoritedFavorited Favorited 6 favourites
Audio: scheduled playback not always working correctly in worker mode
Not favoritedFavorited Favorited 3 favourites
Error opening example 'Traffic jam'
Not favoritedFavorited Favorited 5 favourites
WebGPU: possible crash rendering lots of content with f16 support (regression r435)
Not favoritedFavorited Favorited 7 favourites
'Wait for previous actions' in a function could incorrectly wait for actions from caller event
Not favoritedFavorited Favorited 4 favourites
Changing instance tags did not enable save button
Not favoritedFavorited Favorited 4 favourites
Flowcharts: path finding links not shown properly
Not favoritedFavorited Favorited 4 favourites
Flowcharts: produce smoother path finding links
Not favoritedFavorited Favorited 4 favourites
Timeline bar: keyboard shortcuts activating unexpectedly when the bar is in a popup window
Not favoritedFavorited Favorited 3 favourites
Timeline bar: crash when the bar is refreshed while in a popup window

Share Construct 3 Release r436 Now

  • 6 Comments

  • Order by
Want to leave a comment? Login or Register an account!

  • The multiple preview is an amazing addition.

  • Здравствуйте! Можно ли когда-то ждать peer to peer? Чтобы игра не заканчивалась с уходом host?)

  • "Improve error logging if opening a project with a corrupt image file"

    That's also a great change! I wish in general C3 showed more information when project is corrupted. Yes, you can check the console, but it isn't often reliable too.

      • [-] [+]
      • UpvoteUpvote 1 DownvoteDownvote
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 1 points
      • (2 children)

      There are thousands of ways a project could be corrupted, and many of them probably can't show any good or actionable error message (e.g. should Construct be able to say "the second half of this JSON file is overwritten with all zeroes"? Is it even useful to you if you see that?) We occasionally make improvements only where we see it happening with real projects and there's both a good and actionable error message we can show.

      • What I mean is just more info to work with! For example, if you have invalid layer name in layout file, error itself is shown correctly, but there is no information of a file name and maybe an object name that have this problem. And only thing you left with is to try to debug barely readable minified code to try to find any hints from variables (i had to do it myself multiple times, its not just in theory, though I don't remember what exactly were the errors sadly).

        Also some basic output in the construct's error window would be nice too, so people who are not so familiar with dev tools would be able to have some idea of the problem

        Load more comments (1 replies)