Construct 3 lets you make your own game from your browser - no coding required! Create your first game from scratch with Construct 3's free game engine.
Learn to build your own games with hundreds of game maker tutorials. Construct 3 also comes bundled with lots of templates and example game files.
Create games rapidly and prototype new game ideas quickly. No tool lets you create games faster and easier than Construct 3. You currently have Javascript disabled, if you want to start building your own games with Construct 3 you'll need to enable it then refresh this page!
What's New in r110
Release r110 was published on 23 Jul, 2018
In this release you can now export projects using the C3 runtime. There was quite a lot of work to implement this and it's still quite fresh, so we don't recommend publishing any important projects with the C3 runtime yet. However if you're interested in trying it out let us know how it goes and be sure to file any issues! Note that due to some serious bugs in Safari, C3 runtime exports are unlikely to work correctly on iOS 11 / Safari 11. These issues should be fixed in iOS 12 / Safari 12, so things should be working better once that's out.
An all-new debugger for the C3 runtime is also now in development. We hope to share it with you soon!
We've also added a new setting that lets you always view expressions in English. This may be useful for anyone using Construct set to a non-English language. For compatibility reasons expressions still have to be entered using English expression names. We try to make this easier by showing translations wherever possible, but some users (particularly bilingual users who also know English) would prefer to just work with expressions entirely in English. Now you can uncheck Translate expressions in Settings and expressions will always display and autocomplete in English. In this mode Construct will still show translations where possible to help you out, but these don't affect how expressions are displayed or typed.
This release also disables WebGL 2 on Android. This is a rather unfortunate step we've had to take since we've had a number of reports of what appear to be GPU driver issues with WebGL 2 on some Android devices. (GPU driver issues are nothing new - see our blog for a number of posts in the past on the subject!) This means no Android devices can use the benefits of WebGL 2 for the time being, even if they were previously working with WebGL 2, but they can continue to use WebGL 1. No other systems are affected, so Windows, Mac, Linux and Chrome OS can continue using WebGL 2. Hopefully the issue on Android will be resolved soon and then we can re-enable WebGL 2 on Android.
Finally there are a few more C3 runtime updates and, as ever, more bug fixes. We hope to make a stable release soon so please test carefully and let us know if there are any more outstanding issues!
