Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
932897
Regression
No
HandleUtility.GUIPointToWorldRay returns different results depending on Event.current.type
To reproduce:
1. Open the project, attached by the tester (eventBug.zip)
2. Open the "scene" scene
3. Open Window -> MyWindow
4. Click in the Scene view to focus on it
5. Make sure to not move the mouse now
5. Press 'a' on the keyboard
6. Press 'r' on the keyboard
7. Observe the ray origin in the console
Expected: HandleUtility.GUIPointToWorldRay returns the ray with the same origin no matter what the Event.current.type is
Reproduced in 5.4.5p4, 5.5.4p2, 5.6.2p4, 2017.1.0f3, 2017.1.0p1, 2017.2.0b4, 2017.3.0a1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
low priority defect, we might get back to it at some point, but unlikely for the moment.