Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a8
Issue ID
1023001
Regression
No
Editor crashes on applying import settings in play mode
Editor crashes on entering in play mode with unapplied changes on a model from model import settings
Steps to reproduce:
1. Create a new project.
2. Import any 3D model.
3. Select imported model in Project tab.
4. Change some import settings from Inspector tab (Model, Rig, Animation, Material).
5. Enter in play mode.
6. Select "Apply" from "Unapplied Import Setting" popup.
Expected Result:
Model should change with respect to changes in import setting.
Actual result:
Editor crashes on selecting "Apply" from "Unapplied Import Setting" popup
Reproducible with:
Unity 2018.2.0a8 , 2018.2.0a1 , 2018.1.0b13, 2018.1.0b1, 2017.3.0f3, 2017.2.0f3, 2017.1.0f3 , 5.6.0f1
Environment:
Only on Mac 10.13 , 10.12
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team