Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.1.0f3
Issue ID
937733
Regression
No
WorldToScreenPoint projecting stops working correctly after rapid camera movement
How to reproduce:
1. Download attached project
2. Open "DEVMechanics" scene and press Play
3. Press "Y" Button and select nav point "Bravo" (move the mouse around to see how the nav point target responds)
4. Center nav point in screen and then press both Left shift and Right Shift buttons to move (wait till stops)
5. Move mouse and see how nav point target responds
Expected result: After the player performs a warp jump (rapidly advancing to another part of the scene) WorldToScreenPoint method should work the same as in the beginning of the game (before warp jump).
Actual result: After the player performs a warp jump the projection matrix appears to get out of sync. Objects are over projected from where they should be as the player moves
Reproduced with: 2017.1.0f3, 2017.1.0p3, 2017.2.0b5, 2017.3.0a1
Note: Incompatible with 5.5, 5.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Add comment