Unity 5.2.1 crashes on FBX checked Generate Lightmaps UV

Make a new project, import any FBX, check automatic unwrap (Generate Lightmaps UV) and Apply :

• Crashes on windows 7 and also Mac OSX Yosemite :
• "UnwrapCL.exe has crashed" then unity crashes.

I tried deleting Library and Temp folder on OSX, still crash.
Unusable update !

Thank you,

SMaX

 

I can't find an issue tracker for this. We won't be able to upgrade either until this is fixed.

 

just got it when importing from asset store.
unity 5.2.1f1
windows 10 pro
i7 4GHZ
16GB ram
1tb ssd

 

Got same problem with 5.2.1 Also just tried opening project in 5.1.3p3 and got same error.

 

Ok Thank you.
Back to 5.2.0p1 then !

 

Ah damnit, you are right... Damn

 

Having the same exact problem. Im running windows 8.1 and had no problem until Unity decided to incorporate Microsoft Visual Studio. Not entirely sure if that has something to do with the crash but I cant even open my project now to work on anything because it says its missing prefabs. Unity you really need to get this problem resolved and soon.

Last known stable Unity update was 5.1.3 all the other have been giving me trouble.

 

If it has nothing to do with visual studio then it must be a coincidence that I started noticing this crash after updating to 5.2 and above. Visual Studio is a new feature added to 5.2 taking the place of mono development in 5.1.3 right?

 

I just started getting this bug as well.
I can't even work on my game, and I was suppose to have it released on Steam by the end of this month...

Earlier it was causing Unity to freeze whenever I clicked on something in the scene view, and now I can't even open it...


You said the patch that fixes it is supposed to be released about mid next week (if I understood correctly)?

 

I was having this problem too on a new Windows 10 Pro installation, crashed 3 times in a row when trying to import a 5.0.3 project. But that was from the project screen that pops up when you first start Unity.

I finally got it to load after making a new project, then from the File menu choosing "Open Project..". Everything seems to work fine now.

Why this works, I don't know...

 

Thanks Karl, it's nice to read you've already found and fixed this bug!

btw, seeing that Visual Studio was the new default coding/debugging program made me ridiculously happy!!

 

I'm to the point now where I am very scared to keep upgrading to different versions of Unity. It seems every new version introduces new bugs. Some of which are very fatal issues. So I don't understand why these issues aren't detected prior to releasing the versions of Unity. Doesn't unity have test projects that they can thouroughly test the product before releasing to the customer? I can't imagine that theese issues couldnt be detected at the Unity sites.
How could this work in 5.2.0, but suddelnly not work in 5.2.1??



I might just revert back to Unity 5.0.0 and keep it there.
I'm not trying to bash Unity, it is a great and intuitive product, but maybe the QA testing/Regression testing could be done a little better before a release.

As you can see, the issue has caused a significant issue to occur: the mesh reference is completely lost now in the scene (which means I lost the attached material, colliders, scripts, etc):




Luckily i backed up the project before installing the new version.
EDIT: I was able to re-import the asset which restored the materials, collider, so issue is not as severe as I originally thought. The only issue is just calculating the lightmapping UVs.
j

 

You can try the other 3d formats. It crashes on .fbx, but worked fine on .obj for me.

 

I, too, have this problem. Hope for a fix soon since I can't work on specific assets in the meantime.

 

After upgrading to 5.2.1p1 today, we've been seeing this on a lot of our FBXs - unticking 'Generate Lightmaps UV' is a workaround until the patch, but we've also got 1 FBX that causes UnwrapCL to loop forever (allocating more and more memory - I gave up as it approached half a gig). - is this likely to be fixed in the patch too?

EDIT : unticking 'Generate Lightmaps UV' also allows this file to import.

 

Hello, when would be ready the new patch? thanks!

 

Hello,
I was wondering if this was fixed in today's patch release (Oct 1)?
Patch 5.2.1p2
Because I didn't see anything in the bug fix listings which appear to be related to this issue
http://unity3d.com/unity/qa/patch-releases
Thank you.

 

Seems to be working for me.
(had same interrogation though...)

 

Ok, thanks. Maybe the fix just isn't listed.

 

We have had this problem as well - but the update from yesterday (Patch 5.2.1p2) didn´t help. Unity still freezes when checking on "generate light map UVS" - Working on a mac.

 

The latest 5.2.1p2 has seemed to of fixed the crashing I was experiencing but anchor override seems to still be broken.

 

Thanks for the heads up Karl! Its nice to know you guys are at least aware of the problem. I posted a thread called Anchor override and bumped it but no one has commented on the discussion from Unity or other fellow community members.

 

I can confirm it doesn't happen in the most recent patch release of Unity 5.2 here.

 

We have just moved up to 5.2.1p2 (we can't go any further at the moment due to other bugs).
Some of the FBX file that used to crash unwrapcl.exe now just cause it to hang indefinitely if 'Generate Lightmap UVs' is ticked.
I've just reported a bug (case 737857) and provided an FBX that demonstrates the problem.

 

FBX importer will hang (during lightmap generation) on complex geometry even in 5.1.3, so it is a good idea not to rely on it too much but instead generate lightmap coordinates in your 3d editor.

 

Or Unity could fix the importer
The model in this case is extremely simple, so I don't think its down to the complexity of the geometry.

 

All version since 5.2.1p2 have non-functioning legacy networking (RakNet) on PS4. I believe it's to be fixed in 5.2.2p1.

 

Hello,

I work on Unity 5.2.1f1 and i have the same problem with "Generate Lightmap UV" on some of my FBX. It crash with "UnwrapCL.exe has crashed" window.
Have you got a solution for this problem at the current time ?

Thanks in advance

 

Seeing this happen in 5.3.1f1

 

Using 5.3.1p3 on Mac OSX 10.9.5 and it hangs almost every time I bake a lightmap. Stuck at 5/11 Compositing | 1 jobs.
Scene has 2 low-poly meshes which are correctly UV-mapped.

 

whoa...good thing i read this before pooching my whole project.

 

I believe I may have found a fix. I had the same problem on one of my fbx files, and in the Maya UV editor, I noticed that there were multiple UV sets. I deleted all but the first UV set and the asset imported without crashing.

This was in 5.2.4f1

 

I have the same Problem in Unity 5.3.2 it crashed with fbx from 3ds Max 2016 :/.