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
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Resolution Note:
low priority defect, we might get back to it at some point, but unlikely for the moment.