Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4
2019.3.0f6
2020.2
Issue ID
1225913
Regression
No
Binary to YAML conversion error is thrown importing certain packages and Asset Serialization Mode is set to Force Text
Steps to reproduce:
1. Create a new project
2. Under Edit > Project Settings > Editor, set Asset Serialization Mode to "Force Text"
3. Navigate to "https://assetstore.unity.com/" in a browser of your choice
4. Search for "Microsplat" by Jason Booth and press "Add to my Assets"
5. Click "Open in Unity"
6. Import the "MicroSplat" package from the Package Manager
7. Click "Import" again when prompted
Expected result: No error messages are thrown in the Console
Actual result: "Binary to YAML conversion: type UInt16 is unsupported" error is logged to the Console
Reproduced in: 2017.4.39f1, 2018.4.20f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Notes:
- The issue is not reproducible if Asset Serialization Mode is set to "Force Binary" or "Mixed"
- In 2020.1.0b5, two additional errors are thrown:
"Trying to access current progress scope, but the scope stack is empty"
"Trying to pop progress scope to invalid size (trying 1 stack size 0)"
-
Tonio1308
May 05, 2021 17:53
This issue is still present in 2019.4.25f1 but should be fixed.
-
NathanielAH
Jul 17, 2020 21:29
This issue is present in 2019.4.1f1 LTS.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a11