Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.2.0b3
2018.3
2018.4
2019.1
2019.2
2019.3
2020.1
2020.1.0b4
2020.2
Issue ID
1232270
Regression
Yes
[Scene/Game View] Switching to 3D view while Navigating using Arrow keys in 2D view breaks the Navigation tool
Switching from 2D to 3D while navigating using arrow keys breaks the navigation tool and makes the scene camera go in the direction it was moving in, in 2D view.
Refer to the attached Video.
Steps to Reproduce:
1. Create a New Project (3D Template)
2. Switch to 2D View
3. While Navigating with Arrow Key, Switch back to 3D view
4. Navigate in 3D view with Arrow Keys/Just press Right-click (To Enter Flythrough Mode)
Actual Result:
Navigation only occurs in the direction it was moving in, in 2D View
Expected Result:
Navigation direction in 3D view should depend on the current Arrow key input
Note:
1. Entering Flythrough mode(Right-click + WASD) also doesn't work till Q or E is used to move up or down.
2. Unable to test on versions 2018.2.0a6-8 and 2018.2.0b1-2 due to this issue https://fogbugz.unity3d.com/f/cases/1022564/
Occurring on:
2020.2.0a5, 2020.1.0b4, 2019.3.7f1, 2018.2.0b3
Working Fine on:
2018.2.0a5, 2018.1.9f2
Environment:
Windows 10 and macOS 10.14
License type: Pro
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
Add comment