Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.33f1
6000.0.6f1
Issue ID
UUM-73924
Regression
Yes
Scene view Camera cannot be moved when using the mouse, WASD keys, or the move tool
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Base.unity“ Scene
3. Open the Scene view tab
4. Try to move around with the mouse, WASD keys, or the move tool
Expected result: The Scene view Camera moves around
Actual result: The Scene view Camera is irresponsive and does not move around
Reproducible with: 2022.3.14f1, 2022.3.33f1, 6000.0.6f1
Not reproducible with: 2021.3.39f1, 2022.3.13f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Resolution Note:
This problem is actually caused by the use of UXF's code in the user project. This is because a method is incorrectly using the EditorApplication.delayCall callback. In recent changes to the Scene view shortcuts, we register a method to that callback to set up the contexts of those shortcuts. Because this called is done incorrectly in the UXF code the shortcuts are not set up properly and that's why the shortcuts don't work in the Scene view.
I contacted directly the code owner of the Unity experimental framework github. However, feel free to report that to them on your side as well.
To fix your problem, just modify the line 65 in the ReorderableArrayInpector.cs to properly use the delayCalls with += instead of = :
EditorApplication.delayCall += () => { EditorApplication.delayCall += () => { FORCE_INIT = false; }; };
Thanks