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
When spawning a new MaterialGizmo (material inspector) using the Material Tip's "Edit Material" button, the window is either too small or too big when user scale is smaller or larger than 1 respectively. In fact, the inspector's scale is the square of the user scale.
This is due to the inspector being scale adjusted twice when spawned. This also causes issues when moving an existing one, as it also becomes smaller or larger depending on user scale.
Relevant issues
None found.
To Reproduce
Get material tip. Select a material. Be at a user scale other than 1. Use the "Edit Material" button on the context menu.
Expected behavior
The inspector should have exactly the scale of the user.
Describe the bug?
When spawning a new MaterialGizmo (material inspector) using the Material Tip's "Edit Material" button, the window is either too small or too big when user scale is smaller or larger than 1 respectively. In fact, the inspector's scale is the square of the user scale.
This is due to the inspector being scale adjusted twice when spawned. This also causes issues when moving an existing one, as it also becomes smaller or larger depending on user scale.
Relevant issues
None found.
To Reproduce
Get material tip. Select a material. Be at a user scale other than 1. Use the "Edit Material" button on the context menu.
Expected behavior
The inspector should have exactly the scale of the user.
Log Files
No response
Screenshots
How often does it happen?
Always
Does the bug persist after restarting Neos?
Yes
Neos Version Number
all?
What Platforms does this occur on?
Windows, Linux, Android / Quest
Link to Reproduction Item/World
No response
Did this work before?
No
If it worked before, on which build?
No response
Additional context
I have written a (tiny) mod that fixes this: https://github.com/Banane9/NeosCorrectGizmoScaling
Reporters
epicEaston197#0793, Banane9#5929
The text was updated successfully, but these errors were encountered: