Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
2022.3.69f1
6000.0.66f2
6000.3.6f1
6000.4.0b6
6000.5.0a5
Issue ID
UUM-133555
Regression
No
[Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
How to reproduce:
1. Extract and open the attached “IN-128003.zip“ project
2. Open the SampleScene located in Assets/Scenes
3. Select the Gizmos GameObject in the Hierarchy
4. In the Inspector under the “ER Gizmos (Script)” component, click “Spawn Gizmos“
5. In the Scene View Look at the spawned Gizmos and try moving the camera (rapidly zoom or pan around)
Actual result: Glitchy square visual artifacts appear very shortly near spawned gizmos
Expected result: Editor behaves as expected, no glitchy square visual artifacts appear
Reproducible with: 2022.3.71f1, 2023.1.0a1, 6000.0.66f2, 6000.3.6f1, 6000.4.0b6, 6000.5.0a5
Reproducible on: macOS 26.2 (M1 Silicon)
Not reproducible on: Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from the user code, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
In the current report, the user is calling Handles.SphereHandleCap.
This function should only be called during events corresponding to the last parameter assigned to it (in that case repaint events). Adding a check on the event type before calling it fixes the issue:
" if (Event.current.type == EventType.Repaint)
Handles.SphereHandleCap(..,EventType.Repaint);"
This has to be done this way as the method can also be called during Layout/MouseMove events to calculate handle distance to mouse.
We cannot change this in the method itself at the moment as it could introduce regressions to certain user projects. However, this element is definitively lacking at the moment in the function documentation and I'll see to update the documentation accordingly.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
Our investigation indicates the issue originates from the user code, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly.
In the current report, the user is calling Handles.SphereHandleCap.
This function should only be called during events corresponding to the last parameter assigned to it (in that case repaint events). Adding a check on the event type before calling it fixes the issue:
" if (Event.current.type == EventType.Repaint)
Handles.SphereHandleCap(..,EventType.Repaint);"
This has to be done this way as the method can also be called during Layout/MouseMove events to calculate handle distance to mouse.
We cannot change this in the method itself at the moment as it could introduce regressions to certain user projects. However, this element is definitively lacking at the moment in the function documentation and I'll see to update the documentation accordingly.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.