Search Issue Tracker
Fixed
Votes
12
Found in
5.2.1f1
Issue ID
739221
Regression
No
[Freeze] Generate Lightmap UV's takes too long on certain model
Steps to reproduce:
1. Open attached project.
2. Select the wallCanyon_01LoA asset in the assets folder.
3. Open the model tab in the inspector
4. Select Generate Lightmap UV's & hit apply
5. Unity freezes
Reproduced with Windows 10 (64 bit) on 5.3.0b3 (b6181bece87a) and 5.2.1f1 (44735ea161b3)
OSX 10.11 using 5.3.0f1 (b948b362cb65)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Danbamzam
Oct 23, 2024 03:22
This issue is clearly not fixed. Why is it marked as fix? Many people are still having the same problem. I am still having this problem in unity 2022.3.22f1.
DomeCreator
Jan 23, 2023 09:42
I'm facing the same issue, editor freeze and not responding on 2023.3.14 LTS.
I thought that original texture was to heavy (16000x16000) but changing it to 1024x1024 give me the same result.
Could you please reopen the ticket ? I can give you a project with the issue.
BackdoorStudio
Jul 11, 2020 18:40
I've got same issue - unity 2019.3.7f1
BackdoorStudio
May 14, 2020 13:13
Unity 2019.3.7f1 same issue
BackdoorStudio
May 14, 2020 13:12
Unity 2019.37f1 same issues
AngelGabriel
Aug 30, 2018 07:42
Update: eventually (after at least 2 hours in my case) the "Hold On" pop-up vanishes. And, based on the improved results of the light map baking the light map UVs were correctly generated.
So... it seems like the issue (for Unity 2018.2) is that the progress bar does not provide an indication of progress.
(An estimated time to completion and/or jobs remaining would be nice in addition to the progress bar.)
AngelGabriel
Aug 30, 2018 04:01
Encountering what seems to be the same same issue in Unity 2018.2.0f2, Windows 10.
(1) Import exported to binary FBX (2019 version) by 3Ds 2019. (Model is somewhat complicated, with multiple levels of detail present for some objects.)
(2) Select "Generate Lightmap UVs" with default settings & hit "Apply"
(3) A "Hold On" window appears with an empty progress bar and the model listed beneath.
(4) Unity consumes about 18% of CPU, 5GB of memory, makes no progress & is non responsive.
mattfabius
Jun 24, 2018 04:39
I also experienced this problem on Windows 10 in Unity 2017.3.1f1. What was infuriating was that it froze Unity, so I had to force quit it, but then when I would go to open the project back up it would continue trying to generate the lightmap uvs before the editor opened which would cause it to freeze. I thought I was going to have to start my entire project from scratch, but luckily I figured out that if I ended certain tasks as soon as they popped up like UnwrapCL.exe and Maya, I could get it to stop.
MauroRobert
Jun 08, 2018 13:06
This problem unfortunately still exists in 2017.3.0 and 2018.1.0, specifically when trying to generate lightmaps for an fbx with many elements. Personally, I can track down which element UVs are causing the crashes, but an unwanted side effect is the entire import switches back to a 'default asset', which means you may lose a lot of progress.
superfryme
Jan 13, 2018 20:54
yep this problem still exists. my model was too complex. ill have to break it down into smaller model sections to fix this issue ;-)