Hundreds of features to explore
Games made in Construct
Your questions answered
Popular & trusted by schools and Universities world-wide
Construct 3 runs in the browser & works offline
Students do not need accounts with us
Our educational partners
Free education resources to use in the classroom
World class complete documentation
Official and community submitted guides
Learn and share with other game developers
Upload and play games from the Construct community
Game development stories & opinions
Beta versions are not as thoroughly tested as stable
New procedural terrain demo; more Instant Games updates; lots of bug fixes
Don't miss out on the latest and greatest new features in Construct 3.
In this release we have a new Procedural terrain generation demo by Iain which shows how to make an endless randomly-generated level. It's an advanced example that combines lots of features, so take a look if you're up for the challenge!
We've also got a few more Instant Games improvements. There's also now a warning on export if your project uses images larger than 4096 pixels - these won't load on most mobile devices and have been the cause of a number of "blank screen on mobile" type issues. Finally there's a range of other smaller additions and changes, and a big batch of bug fixes, including fixes for a few long-standing issues. We'd like to get a new stable release out soon, so please test carefully and let us know if there are any remaining issues!
Let us know with a thumbs up!
Procedural terrain generation is awesome. It is time to create some crazy big platform games.
Really liked the "Procedural terrain generation" example. Good performance with smooth chunk generation. There are some minor errors with grass chunks sometimes, could easily fix it with a manual check in the generation events.
Is there a limit for dictionary keys or is disk space (chunk save-file size) the only "true" limitation?
Thanks, I'm glad you liked it! We don't impose any limitation on the size of the dictionary, so it's upper limit is the JS heap size. You could switch to using localstorage instead, which is likely slower but would increase the max size to available disk space and effectively "save" the world for players. There are also ways to store the data that is more space efficient ( binary instead of JSON, run length encoding, Huffman coding, etc. ).
The grass error is a bit of a pain, but it's quite minor. I haven't investigated fully, but if my best guess is correct then most fixes will have semi significant trade offs. Still, fixing it is a good exercise for the user!
I very much like the fix about the multiple projects preview.
""Selecting objects in the Project Bar with no instances in the current Layout View no longer selects instances from across the whole project (avoids unexpected results changing properties in this case)""
But isn't this the only way we can change properties of all instances of an object project-wide? I don't believe that's a rare thing to do.
I have the same concern.
I made a feature suggestion as Ashley said. Go upvote!
It's not really meant for that - it only did that as an accidental side effect of being implemented at a time when C3 didn't have a way to edit object type properties only with no instances.
So then, forgive me if I'm missing something, but how are we supposed to change properties for an object project-wide?
Thanks for all the changes! :) Sorry for being so dense. What would be the new way to edit object properties across the whole layout?
Extra kudos for those dark theme issues adressed !
Did not correct the IFRAME bug to access external pages yet?
to bad,yesterday my C3 Clicense expired now back to my old friend C2 :(
Thanks for the update! The 4096px limitation on mobile device is also applied for a drawing canvas or i can make a drawing canvas bigger than 4096px?
It also applies, but in the case of Drawing Canvas it stretches the max texture size to the size of the object rather than failing to load.