Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.47f1
6000.0.20f1
Issue ID
UUM-82589
Regression
Yes
Unable to navigate in the Scene when the Readme.cs script of an Asset exists in the project
How to reproduce:
1. Open the “ReadmeBug.zip“ project
2. Fix any Console errors if there are any
3. Try to Pan/Rotate/Orbit with the Scene view Camera in the Scene view and observe
4. Try to select any GameObjects within the Scene view and observe
Expected result: The Scene view camera moves around and GameObjects can be selected
Actual result: The Scene view camera does not move around and GameObjects cannot be selected
Reproducible in: 2022.3.14f1, 2022.3.47f1, 6000.0.20f1
Not reproducible in: 2021.3.43f1, 2022.3.13f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Workaround: Delete the Readme.cs script in “Assets > StarterAssets > TutorialInfo > Scripts” in the Project tab
Notes:
- Could not reproduce the issue with other projects
- Requested by the developers to confirm this as a bug
- The Asset in question is “Starter Assets - ThirdPerson CharacterController”
- No messages/errors related to the issue are displayed in the Console
- The only available Scene view Camera manipulation is Zooming with the mouse scroll
- Scene view Gizmos are fully functional
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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
An exception is being thrown in the console window from the ReadmeEditor.cs. See below:
InvalidCastException: Specified cast is not valid.
ReadmeSystem.Editor.ReadmeEditor.GetAllRootReadme () (at Assets/StarterAssets/TutorialInfo/Scripts/Editor/ReadmeEditor.cs:278)
ReadmeSystem.Editor.ReadmeEditor.GetReadmeRoot () (at Assets/StarterAssets/TutorialInfo/Scripts/Editor/ReadmeEditor.cs:292)
ReadmeSystem.Editor.ReadmeEditor.SelectReadme () (at Assets/StarterAssets/TutorialInfo/Scripts/Editor/ReadmeEditor.cs:73)
ReadmeSystem.Editor.ReadmeEditor.SelectReadmeAutomatically () (at Assets/StarterAssets/TutorialInfo/Scripts/Editor/ReadmeEditor.cs:59)
UnityEditor.EditorApplication.Internal_CallDelayFunctions () (at C:/Work/git-unity1/Editor/Mono/EditorApplication.cs:400)
That error is sent from a method that is registered to the EditorApplication.delayCall callback. Once an error is thrown from that callback, the other methods that are registered to it don't get called. In recent changes to the Scene view shortcuts, we register a method to that callback to set up the contexts of those shortcuts. Because that error is thrown, the shortcuts are not set up properly and that's why the shortcuts don't work in the Scene view. The error thrown from the ReadmeEditor.cs needs to be addressed in order for the shortcuts to work.