Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
1
Found in
2019.2.0b6
2019.2.0b7
2019.3.0a6
Issue ID
1169942
Regression
Yes
Applying Import Setting changes while in Play Mode throws an AssetDatabase.ForceReserializeAssets exception
How to reproduce:
1. Open user-submitted project (Unity2019Test3)
2. Enter Play Mode
3. Select the 'test' asset in the Project window
4. Change some Import Settings(e.g. Max Size) and click 'Apply'
Expected result: the changes are applied, no errors are thrown
Actual result: "Exception: AssetDatabase.ForceReserializeAssets cannot be used when in play mode" error is thrown
Reproducible with: 2019.2.0b6, 2019.2.0b10, 2019.3.0a6, 2019.3.0a10
Not reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.11f1, 2019.2.0b5, 2019.3.0a1, 2019.3.0a5
Notes:
Also reproduced with .fbx asset
Comments (1)
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
- Crash on do_runtime_invoke when reopening a specific project after failing to build it
- Animations change speed when rigidbody is added
- Low FPS persists when re-entering Play mode after an extended session in a specific project
- ListView list items in UIToolkit get stuck when reorderMode is set to Animated and they are reordered using two or more fingers on touch devices
- Editor or player crashes when using a deeply nested Particle System with a sub-emitter that has multiple references
joshcamas
Aug 20, 2019 04:38
For now, while we're waiting for the fix in 2019.2, manually reimporting the asset in question after this error is thrown works :)