Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2019.3.0b1
2020.1.0a1
Issue ID
1180061
Regression
No
Editor spits Internal Errors when loading Scene asset with AssetDatabase.LoadAssetAtPath
How to reproduce:
1. Open the attached "BugReports1.zip" Project
2. Click on Example > ReadObjectsBug
3. Drag the "SampleScene.unity" asset in the Field on the Window
4. Press "Load at Path" button
Expected Behaviour: One error is printed warning the user to use another method for Scene files
Actual Behaviour: 11 internal errors are printed telling the user that some method that is used internally cannot be used with Scene files
Reproducible with: 2017.4.32f1, 2018.4.8f1, 2019.2.2f1, 2019.3.0b1, 2020.1.0a2
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
- Sprite Atlas Samples throw multiple warnings when changing the original Editor verion
- Deleting 2D Lights while Lighting Explorer is open throws “GUI Error” and “NullReferenceException” errors in the Console window
- "Couldn't open file for reading" error occurs when running binary2text on a file larger than 2 GiB
- AssetReference Variable will default to Texture Asset Reference Type when no Asset Reference is set and it's duplicated in UI Builder
- Unable to open projects for a period of time when closing "Project not found" panel in any way
Resolution Note:
Seems to be minor issue, right now LoadAllAssetsAtPath for scenes is not supported. Fixing it would require partial system rewrite