Search Issue Tracker
Won't Fix
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|https://github.com/Unity-Technologies/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
- Blender FBX file import triggering incorrect errors
- Overlay UI opaque colors are shown incorrectly in the Player when a HDR display and Linear Color Space are used
- [D3D12] HDRP DLSS resource state is reported incorrectly when when calling ClearUnorderedAccessViewFloat
- URP Decal Projector does not render decal when in Play Mode with a specific project
- Frame Debugger does not display individual Draw Calls in the Game view or the Player when using Camera Stacking
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.