Beta versions are not as thoroughly tested as stable
3D mesh collisions; more 3D model improvements
27 October, 2026 ()
Email Me New Releases
Don't miss out on the latest and greatest new features in Construct 3
Notes
This week work continues on 3D collisions, and it now supports 3D collisions with mesh distortion. This means you can do things like use a 3D mesh for some terrain with various ups and downs, and accurately collide with it. Internally there's a new mesh collision optimizer that can efficiently handle collisions even for large meshes with dozens of rows and columns, resulting in thousands of triangles. We're looking to extend this to 3D model as well so the same system works for efficiently colliding with 3D model scenery and hopefully will have something ready within this release cycle, but for now 3D models continue to use bounding box collision.
In this release we've also changed ambient light to just be a color, instead of having a separate amount and color. The default ambient light is now (8, 8, 8) which corresponds to 3% (the previous default amount) on a 0-255 scale. This means you can directly choose the color of the ambient light, rather than setting a color and then what was essentially a multiplier for the color.
Other improvements in this release include a range of further improvements for 3D model, including fixing a performance issue, some script API updates, and a few other tweaks and adjustments. Happy testing!
Like this Release?
Let us know with a thumbs up!
Launch r508
New Additions
Support for 3D collisions with mesh distortion
Timelines: add action/script API to reset hierarchies in a timeline to their initial state
3D model: actions, expressions and script API to get and set the weight of an animation
3D model: 'Reset' action and script API to set a 3D model to its default pose
Changes
Gamepad: update GameInput (used for Steam) to v4.0.302
Layouts: remove ambient light amount, instead using ambient light color directly
Bug Fixes
'Slide puzzle' example incorrectly opened 'Slide puzzle 3D'
Some 2D vs 3D collision checks working incorrectly
Possible incorrect rendering of instances using 3D mesh distortion
3D model: unnecessary textures loaded after creating the first instance of a 3D model using 'Create object' action
3D model: start load of textures as soon as a new model is loaded
3D model: unload unused textures after loading a new model at runtime
3D model: 'Animation blend' mode not behaving as expected when set to 'Average'
3D model: models with no armature not behaving as expected
3D model: fix performance degradation over time
Properties Bar: changes to Z offset property of a 3D model incorrectly affecting X offset
Scripting updates
Timelines: fix 'stop' method not doing the same as the equivalent action
3D model: 'loadModel' method not resolving promise when setting same model
Share Construct 3 Release r508 Now