Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

0

Found in

2020.3

2022.1

2022.1.0a12

Issue ID

1369257

Regression

No

[GPU PLM] Fallback to CPU PLM with "Available GPU memory: 0 B" after launching GPU bake

Progressive Lightmapper

-

Steps to repro:
1. Pull ArchViz Pro vol.6 project (see the link in the case comments) and sync to the revision 1da1e66b8989;
2. Open 'AVP6_Desktop' scene;
3. In the Lighting window (Window>Rendering>Lighting) enable Progressive Updates checkbox;
4. In the Lighting window press Generate Lighting button.

Expected result:
The GPU PLM bake proceeds and finishes as expected.

Actual result:
Fallback to CPU PLM happens. The following errors are shown:
- Not enough GPU memory to fit an entire lightmap, disabling progressive updates. Available GPU memory : 0 B
- OpenCL Error. Falling back to CPU lightmapper. Error callback from context: Not enough GPU memory to fit lightmap in memory, even in tiled baking mode. Available GPU memory: 0 B
See attached Editor.log and screenshot.

Notes:
- Reproducible in Versions 2022.1.0a11, 2021.2.0b14, 2021.1.24f1, 2020.3.20f1;
- Reproducible on Windows with NVIDIA GeForce RTX 2080Ti GPU (NVIDIA drivers ver. 472.12);
- The issue seems to be project-specific; I haven't managed to repro on other projects so far;
- The issue might not reproduce consistently (in my case, having about 70% reproduction rate);
- Also reproducible without denoising and with a lower lightmap resolution (40);
- Although the issue is not officially a regression, I was able to bake this project successfully in the previous versions, so it might be caused by some backport that introduced it in latest LTS and tech stream Editor versions;
- The issue might be related to the GPU drivers;
- In some cases executing aforementioned repro steps it might lead to either Editor crash or to the different errors shown during the fallback to CPU PLM (see case comments);
- Restarting Editor or even OS doesn't fix the issue;
- Closing other applications that might occupy some RAM doesn't fix the issue.

  1. Resolution Note (2022.1.X):

    This bug will be fixed by enablement work that is in progress now. To that end we are postponing this and will retest once that lands.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.