Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a13
2019.1.0b1
Issue ID
1120755
Regression
Yes
[CPU PLM] Baking stalls when baking a project containing illegal geometry
Steps to repro:
1. Open attached project and 'MaterialTypes' scene;
2. In the Lighting window press 'Generate Lighting' button.
Expected result:
Illegal geometry (containing line and/or point geometry) is ignored and the bake proceeds and finished successfully.
Actual result:
Baking stalls with the following errors:
- `[PathTracer] AddGeometry job with hash: 6dc2d92b85d9b592a751b4d831830fbd failed with exit code 1.'
and
- '[PathTracer] Failed to add geometry; mesh is missing required attribute. Please make sure mesh contains positions, normals and texcoord0.'
See attached video. Regression introduced in 2019.1.0a13.
Notes:
- Reproducible in 2019.2.0a3, 2019.1.0b1, 2019.1.0a13;
- Not reproducible in 2019.1.0a12, 2018.3.3f1;
- Reproducible on Windows and Mac;
- Reproducible only with CPU PLM; not reproducible with Enlighten and GPU PLM.
- In trunk (2019.2.0a3) different error is shown:
'[PathTracer] Failed to add geometry for mesh 'Line001'; mesh is missing required attribute(s). Please make sure the mesh contains at least positions, normals and texcoord0.'
and the baking is still stalled.
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
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
tcz8
Nov 20, 2019 21:35
Same error over here on 2018.4.12f1
djgriff
Oct 20, 2019 09:37
Has anyone found a solution to this as of yet?
Thanks
Daniel-Gutierrez
Jul 18, 2019 12:31
I have the same error - though it didn't show an error message on 2018.3.14f, it only started showing them when I upgraded to 2019.1
Artline
Jul 02, 2019 12:15
How can I solve this error?