You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read and understand the suggestion guidelines
Checked for duplicate suggestions
I checked for existing similar suggestions
Summary
This suggestion came from the knowledge of the following "bug" which is, to be fair, not a bug, just the way Construct 3 operates, and for good reason: Scirra/Construct-bugs#7604
Z elevation changes are expensive due to C3 needing to sort objects upon a Z change. It would be excellent if we could opt to enable/disable this via a setting per layer.
For my very specific case, I am making a 2D game but utilised 3D camera on its release, and decided to permanently incorporate this into my project primarily for 3D backgrounds. To make a snazzy depthy background, lets say a space starfield with sprites that move towards the player, this is achievable at lower object counts, but the more stars the better atmosphere this provides, but too many stars, the performance hit occurs.
I have other 3D background desires that would heavily use Z elevation (don't wanna just keep things flat, want to utilise the 3D atmosphere!)
I can imagine great potential for other uses beyond this, especially with those brave enough to tackle a fully-3D game.
I figure with auto-sorting disabled, developers can manage this themselves in very specific ticks and optimise much better.
Possible workarounds or alternatives
Whilst haven't tried, I suppose redesigning my game at a different orientation could allow me to use X and Y positioning for the objects moving closer.
I feel there is not many workarounds for other use-cases beyond my own.
Proposed solution
Setting to enable/disable "Sorting when Z Elevation changes"
Why is this idea important?
I feel giving fine control over this, without harming regular 2D games, would be greatly beneficial, especially for those looking to optimise.
Additional remarks
No response
The text was updated successfully, but these errors were encountered:
Reviewed guidelines
Checked for duplicate suggestions
Summary
This suggestion came from the knowledge of the following "bug" which is, to be fair, not a bug, just the way Construct 3 operates, and for good reason:
Scirra/Construct-bugs#7604
Z elevation changes are expensive due to C3 needing to sort objects upon a Z change. It would be excellent if we could opt to enable/disable this via a setting per layer.
For my very specific case, I am making a 2D game but utilised 3D camera on its release, and decided to permanently incorporate this into my project primarily for 3D backgrounds. To make a snazzy depthy background, lets say a space starfield with sprites that move towards the player, this is achievable at lower object counts, but the more stars the better atmosphere this provides, but too many stars, the performance hit occurs.
I have other 3D background desires that would heavily use Z elevation (don't wanna just keep things flat, want to utilise the 3D atmosphere!)
I can imagine great potential for other uses beyond this, especially with those brave enough to tackle a fully-3D game.
I figure with auto-sorting disabled, developers can manage this themselves in very specific ticks and optimise much better.
Possible workarounds or alternatives
Whilst haven't tried, I suppose redesigning my game at a different orientation could allow me to use X and Y positioning for the objects moving closer.
I feel there is not many workarounds for other use-cases beyond my own.
Proposed solution
Setting to enable/disable "Sorting when Z Elevation changes"
Why is this idea important?
I feel giving fine control over this, without harming regular 2D games, would be greatly beneficial, especially for those looking to optimise.
Additional remarks
No response
The text was updated successfully, but these errors were encountered: