Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
1
Found in
5.6.1xf1
Issue ID
913799
Regression
No
[Linux Editor] Building Progressive Lightmapper crashes Unity
Steps to reproduce:
1. Download the project attached by the user
2. Enter "scene" scene.
3. In Lightning Window under Scene tab, uncheck "Auto Generate"
4. Under "Lightmapping Settings" set Lightmapper field to "Progressive (Preview)"
5. Click "Generate Lighting"
Result: Unity crashes
Fixed in: 2018.2.0a6
Reproduced on: 5.6.1f1, 2017.1.0b8
Note: editor log doesn't contain a stack trace, just some lines about the lightmapper
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
Sirrah
Sep 17, 2017 14:26
The [tanks project](https://drive.google.com/open?id=0BwkcjTqCXtRNaEIxeG5Bdk9FV2M) linked from the [progressive lightmapper manual](https://docs.unity3d.com/Manual/ProgressiveLightmapper.html) crashes shortly after opening the `Complete/Scenes/CompleteMainScene`.
Reproduced on: Unity 2017.1.0xf3Linux, on an i7-5600U with Intel drivers and on a q6600 with a Geforce GTX 960 (Nvidia drivers).