Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a17
2020.1.0a18
Issue ID
1208466
Regression
Yes
[Lighting] Failed to find a suitable OpenCL device error is thrown on selecting Progressive GPU light mapper
Failed to find a suitable OpenCL device error is thrown on selecting Progressive GPU light mapper. Unable to switch to Progressive GPU for the first time.
Steps to repro:
1. Create a new Project.
2. Windows > Rendering > Light Settings.
3. Lightmapping Settings > Lightmapper.
4. Select Progressive GPU(Preview).
Actual Result:
Failed to find a suitable OpenCL device error in the console.
Expected Result:
No Errors in the console.
Reproducible in:
2020.1.0a18, 2020.1.0a17.
Working Fine in:
2020.1.0a16, 2019.3.0f5(4b9e60e5c3e9).
Environment:
Occurs only on Windows.
Stack trace:
Failed to find a suitable OpenCL device, falling back to CPU lightmapper.
Comments (5)
-
azeem_ehsan
Dec 03, 2022 02:30
I'm using Unity 2021.3.13f1 and unfortunately I'm new in Lightmaps generating but when I select the GPU Progressive , gives me the same "OpenCL not suitable" error , Because My GPU memory is also 3GB .
Can anyone suggest me some hack to control it
-
tnikolopoulos
Sep 18, 2021 18:52
yes please this makes no sense. GPU lighmapper works perfectly fine with 3 GB. We are currently stuck with unity 2019 version because of this reason. At least give us a way to hack it.
-
ValeryiaAndreevna11
May 29, 2021 01:41
https://docs.unity3d.com/Manual/VisualStudioIntegration.html
решение этой проблемы!Нужно подключить Visual Studio или кампилятор которым вы пользуетесь) -
ivanessb
Mar 06, 2021 06:11
I have the same issue, I almost lose 8 hours by finding the solutions for this error.
-
Rugbug_Redfern
Jan 08, 2021 18:53
This feels... a little dumb. Is there any way to force Unity to still use my GPU with 3GB of VRAM? I've used this GPU to bake lightmaps in previous versions and it worked perfectly. I really would rather not downgrade my unity version just to bake lightmaps.
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
This is expected to see the fallback to CPU in 2020.1, since your GPU has 3 GB of VRAM. Starting from 2020.1 GPU Lightmapper requires the GPU with at least 4 GB of VRAM and on GPUs having less than 4 GB of VRAM it should fallback to CPU Lightmapper.