I really like this new update and I had a bunch of ideas for past month that I wanted to make with this new feature, however while play-testing this new feature, I found out that the collisions are as if the Z elevation was on 0. (In other words, no matter what object the Z elevation is at, the collision for that object is always on 0)
Suggestion: The collision sizes and position should match how the object is viewed instead of being stuck as if it's on 0, even though the object is not.
Reason: I want to create 3D platform puzzle games where the objects change in Z elevation and affect the collisions, as the current state of Z elevation, it's nothing but used just for visual effects when it has the potential to provide more gameplay mechanics.
Our goal is to keep the logic of Construct games in 2D. This means all the gameplay - and collisions - still work in 2D, even if some objects can be raised or lowered on the Z axis using the Z elevation feature. Since allowing 2D collisions taking in to account perspective is an unusual feature that doesn't seem to have any useful real-world applications, we don't intend to support that.