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
2019.3.4f1
2019.4
2020.3
2021.1
2021.2
Issue ID
1342577
Regression
No
Unity Accelerator data becomes corrupt when importing Assets
How to reproduce:
1. Install Unity Accelerator
2. Install Python 3.9 in "C:\Python39"
3. Extract the attached project "ACTest2.zip"
4. Open Windows Command Prompt
5. Set the current directory to the path where you extracted the project
6. Run "SimCorr.bat -e "[YOUR EDITOR LOCATION]\Unity.exe"
Expected result: No errors importing the Asset
Actual result: "Unknown error occurred while loading" error while importing the Asset
Reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b4
Could not test with: 2018.4.36f1 (not supported by Unity Accelerator), 2022.1.0a2 (does not connect to Unity Accelerator)
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
- An emoji is not shown in the UI Builder Viewport and the Game view when it is placed in the Labels text attribute and Usage Hints is set to Dynamic Color
- The Sprite Renderers are looking for Secondary Textures from the wrong page within the Sprite Atlas when the Sprite Atlas has a large amount of textures for packing
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
Resolution Note (2022.1.X):
Will be fixed as part of feature work for Ruby release.