Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0b1
Issue ID
952468
Regression
No
[Handles] Handles on certain component bounding volumes are not drawn correctly when negatively scaled
Handles on certain component bounding volumes are not drawn correctly when their parent GameObject is negatively scaled.
When editing the bounding volumes of certain components, the editor handles won't be drawn correctly if the component is attached to an object with a negative scale. The handles of the faces that are facing the camera are dimmed while the handles that are facing away from the camera are bright - this is incorrect. Note that this issue affects the following components:
- Occlusion Portal
- Light Probe Proxy Volume
- Skinned Mesh Renderer
It does NOT affect other components that contain bounds that can be edited.
1. Open the attached project
2. Go to ManualTestScenes > BoxBoundsHandle.scene
3. Go to the scene hierarchy and expand the object group "Root - Scale All Negative"
4. Select the Occlusion Portal, Light Probe Proxy Volume or Skinned Mesh Renderer objects
5. Edit the bounding volumes of the object
6. The handles of the faces that are facing the camera are dimmed while the handles that are facing away from the camera are bright - this is incorrect
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note (2019.3.X):
This cosmetic issue is very low in our priority list and will be closed as won't fix. We don't recommend working in negative scale, we'll reconsider if this problem is getting more traction by the community.