Use same colors for editor and running project for collision/path debug #90966
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This harmonizes the appearance of collision shapes and paths between the editor and running project, in both 2D and 3D.
This means that in 3D, paths are now green and shapes are now cyan instead of light blue.
Editor settings for 3D path and shape gizmo colors were removed, as these colors are now set in the project settings instead (they affect both the editor and running project). This paves the way to custom color support for CollisionShape3D, as it already works in a similar fashion in 2D.
Preview
Before
2D
3D
After
2D
3D
Note
Colors in the editor appear more faint, as unselected gizmo drawings have lower opacity in the editor (regardless of the node or color). If the node is selected, the visual output is identical to the running project.