Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1333885
Regression
No
GetHolesLODInfo doesn't match the content of the HeightmapSubRegion holes array
Heightmap::GetHolesLODInfo returns kPatchHasSurfaceOnly for the patch I am interested in, but after extracting the HeightmapSubRegion the m_RawHoles are all 0 which means hole.
1. Download and extract this repro project: https://drive.google.com/file/d/1o5pdHh4roLg3tmj_1aJ0z4bMDo1kOIFa/view?usp=sharing
2. Compile an editor from https://ono.unity3d.com/unity/draft/changeset/f38b769664a471f66a9aeea3ca6cf6885c4ecb06
3. Open t1 scene;
Expected result:
One of the LOD related asserts should fire if the patch is fully covered by holes, but the returned holeInfo is kPatchHasSurfaceOnly:
Assert(holeInfo != Heightmap::kPatchHasNoSurface);
Assert(holeInfo != Heightmap::kPatchHasDirtyHoles);
Actual result:
Assert(holeCount != m_HeightmapSubRegion.m_RawHoles.size()); fires (entire patch is covered by holes).
The patch in question is (0,1) which corresponds to UV bounds 0.0, 0.25, 0.25, 0.25.
Notes:
This issue is preventing GI baking from working.
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:
GetHolesLODInfo Works as intended