Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35946
Regression
No
GPU lightmapper reverts to CPU while baking APV
Steps to reproduce:
- Clone Modern-Sponza project from GitHub;
- Additively load Sponza and SponzaLightingDay scenes;
- In the Lighting window, select Probe Volumes tab;
- Make sure the Min Probe Spacing value is set to 0.5;
- In the Scene tab, make sure that Lightmapper is set to Progressive GPU;
- Generate lighting.
Expected result:
- Bake finishes successfully on a GPU.
Actual result:
- Lightmapper reverts to CPU (see [^Editor.log]). No warning is printed in the console nor the editor log.
Notes:
- Reproduces in: 2022.1.24f1, 2022.2.5f1, 2023.1.0b16;
- Doesn't reproduce in: 2022.3.7f1, 2023.1.9f1;
- Reproduces on Windows;
- Observed using NVIDIA TITAN V and AMD RX 580 GPUs;
- Doesn't reproduce with NVIDIA 3080;
- Only affects the GPU lightmapper;
- Doesn't reproduce when using sparse probe volumes (when Min Probe Spacing is set to 1 or higher);
- System memory (RAM) usage spikes right before lightmapper reverts to CPU.
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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note:
We tried to reproduce this issue and could not. We tried with 2022.3 and 2023.1 both on Mac and Windows, and we were not able to repro it at all.
We reached out to the original reporter of the bug, and they could no longer repro it either.
Therefore we believe this issue has been fixed by other improvements/refactors.
Resolution Note (2023.2.X):
We tried to reproduce this issue and could not. We tried with 2022.3 and 2023.1 both on Mac and Windows, and we were not able to repro it at all.
We reached out to the original reporter of the bug, and they could no longer repro it either.
Therefore we believe this issue has been fixed by other improvements/refactors.