Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2020.1.0a17
2020.1.0a18
Issue ID
1208704
Regression
Yes
Second time GPU lightmapper is chosen with no supported GPU, no fallback to CPU happens
The baking get stuck when the static object starts to bake with Progressive GPU light mapper the second time.
[PathTracer] Failed to add geometry for mesh 'Cube'; mesh is missing required attribute(s) error is thrown in the console.
Prerequisites: you'll need to have the machine with GPU having <4GB of VRAM
Steps to repro:
1. Create a new Project.
2. Create a static Cube game object.
3. Windows > Rendering > Light Settings.
4. Lightmapping Settings > Lightmapper.
5. Select Progressive GPU(Preview).
6. Bake
7. Lightmapper falls back to CPU.
8. Select Progressive GPU(Preview).
9. Bake
Actual Result:
-Baking stalls when the static object starts to bake.
-[PathTracer] Failed to add geometry for mesh 'Cube'; mesh is missing in the console.
Expected Result:
-Baking should not be stuck.
-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:
[PathTracer] Failed to add geometry for mesh 'Cube'; mesh is missing required attribute(s). Please make sure the mesh contains at least positions, normals and texcoord0.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
GI: Fixes an issue in the GPU->CPU fallback logic when no valid OpenCL context could be created.