Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b3
Issue ID
908044
Regression
Yes
"UnwrapCL.exe has stopped working" error appears when importing FBX model with its .meta file if Avira protection is enabled
How to reproduce:
1. Download and install "Avira Free Antivirus", make sure that its "Real-time protection" setting is enabled
2. Open new Unity project
3. Drag and drop LayOut.fbx and its meta file to the Project window
Expected result: Model is imported without any errors
Actual result: "UnwrapCL.exe has stopped working" error appears
Notes:
1. To reproduce again, just right click Project window and press "Reimport"
2. Doesn't seem to reproduce when recording screen and with other .fbx files
Regression introduced in - 2017.1.0b2
Reproducible with - 2017.1.0b4, 2017.1.0b2
Not reproducible with - 2017.1.0b1, 5.6.0p3, 5.5.3p2
Comments (8)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
neosca
May 16, 2018 18:05
still getting issue in 2017.3.1f1
jobs
Apr 13, 2018 04:11
I have the same issue with 2017.3.0f3 ,2017.3.1
jobs
Apr 13, 2018 03:27
I have the same issue with 2017.3.0f3, I have no Avira
jobs
Apr 11, 2018 13:33
I have the same issue with 2017.3.0f3, I have no Avira
jobs
Apr 11, 2018 13:33
I have the same issue with 2017.3.0f3, I have no Avira
hicham_AAI
Apr 05, 2018 16:43
i still get this issue for 2017.3.1f1
SpencerMowrey
Feb 01, 2018 18:07
Just came across this with 2017.3.0f3. I have BitDefender and turning it off did not stop the errors.
Crevecoeur
Aug 23, 2017 11:57
I have the same issue.
I was not thinking it could be Avira. I tried and no more importation error spam.
Thanks