Search Issue Tracker
Won't Fix
Votes
3
Found in
2018.3.0a1
2018.3.8f1
Issue ID
1140054
Regression
No
Unity crashes when enabling Mesh Renderer Lightmap Static
How to reproduce:
1. Open attached project "map"
2. In Hierarchy select TerrainBag/Default Terrain0/LowPolyTerrain
3. In Inspector tick Mesh Renderer/Lightmap Static checkbox
--------------------------------------
Observe crashing
Reproduced with: 2018.3.11f1
Could not reproduce with 2019.2 as the checkbox has been removed.
Does not reproduce with 2019.1, but ticking checkbox constantly produces these errors:
[PathTracer] Failed to add geometry; mesh is missing required attribute. Please make sure mesh contains positions, normals and texcoord0.
[PathTracer] AddGeometry job with hash: 66b0b10e164295898602f480784ec297 failed with exit code 1.
-
pokerFace
Dec 20, 2019 20:38
Sorry for question, but can you explain, what do you mean on "to make sure that the meshes used for baking (lightmap static objects) have positions, normals and texture coordinates"?
All objects have positions and texture coordinates (if they have UV map).
So I don't understand what i have to change to avoid PathTracer error? -
Jesper-Mortensen
Apr 29, 2019 07:45
This has been fixed in 2019.1.
The workaround for earlier versions is to make sure that the meshes used for baking (lightmap static objects) have positions, normals and texture coordinates.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This has been fixed in 2019.1. The fix is not easily backportable. The workaround is to ensure that positions, normals and texcoords are available on meshes used for baking.