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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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