Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.24f1
2022.3.16f1
2023.2.7f1
2023.3.0a12
Issue ID
UUM-61017
Regression
No
[Linux] Can't generate lighting with lightmapper set to Progressive GPU when using AMD or Nvidia GPUs
Reproduction steps:
1. Create a new project from the “3D Sample Scene (HDRP)” template
3. Click Window > Rendering > Lighting
4. Set Lightmapper to "Progressive GPU"
5. Click "Generate Lighting"
Expected result: Lightmapper is set to "Progressive GPU", no OpenCL errors are printed to the logs or console and it is possible to generate lighting
Actual result: Every time Lightmapper is set to "Progressive GPU" it is reset to "Progressive CPU" and OpenCL errors are printed to the Console, with more information in the log file.
Reproduced with: 2021.3.24f1, 2022.3.16f1, 2023.2.7f1, 2023.3.0a12
Couldn't test with: 2023.3.0a13, 2023.3.0b4 (UUM-61003: [Linux] Crash on BackupState::MemoryIDToFileID::operator() when creating a new project from “3D Sample Scene (HDRP)” template)
Reproduced on: Ubuntu 23.10, Ubuntu 22.04.3
Not reproduce on: Windows 11
Errors in the Console window:
Failed to find a suitable OpenCL device, baking cannot use GPU lightmapper.
Falling back to CPU lightmapper.
Logs:
OpenCL Error: 'clGetPlatformIDs(kMaxPlatforms, platforms, &numPlatforms)' returned -6667 (Unity cannot load OpenCL.dll. Please install the latest graphics driver.).
-- Listing OpenCL platforms(s) --
-- Listing OpenCL device(s) --
Light baking could not be started because no valid OpenCL device could be found.
Tested GPUs:
1. AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.49, 6.2.0-39-generic) Version: 23.0.4
2. AMD Radeon Pro WX 9100
3. Nvidia RTX 3080 with 525 drivers
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. The reason we've made this decision is that the engineers on the team are unable to repro this issue with an updated openCL version.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.