Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b3
2019.1.0a2
Issue ID
1124678
Regression
No
[GPU PLM] Editor crashes when switching to Progressive GPU Lightmapper with specific hardware on 2018.3
Reproduction steps:
1. Create a New Project
2. Switch the "Lightmapper" to "Progressive GPU (preview)"
Expected Result: "Lightmapper" switches to "Progressive GPU (preview)"
Actual Result: Editor crashes
Reproduced with: 2019.1.0a12, 2018.3.5f1
Did not reproduce on: 2019.2.0a4, 2019.1.0a1, 2019.1.0b3, 2019.1.0a13, 2017.4.20f1
Note:
Progressive GPU Lightmapper only implemented from 2018.3.0b3 and 2019.1.0a2
Reproduced only on a GTX 1050Ti GPU
Doesn't reproduce on an Nvidia GTX 760 and AMD Radeon R7 360 GPUs
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2018.3.X):
This is a crash in the driver, Unity 19.1 and up have a workaround for it. However as the work around is quite large code wise and as the GPU lightmapper is in preview in Unity 18.3 it won't be backported to avoid destabilizing the 18.3 version witch became LTS (long term support).