Search Issue Tracker
Fixed
Fixed in 2022.3.68f1, 6000.0.60f1, 6000.2.8f1, 6000.3.0b7, 6000.4.0a1
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
Issue ID
UUM-109482
Regression
No
'Unwrapping.GenerateSecondaryUVSet' does not work with submeshes when they have offsets on baseVertex
How to reproduce:
1. Open the “LightmapUVBug.zip“ project
2. Open the “SampleScene“
3. Select "Mesh.065" and focus on it in the Scene view
4. In the Inspector, right-click the "Lightmap UV Gen" Component, and select "Generate Lightmap UVs"
5. Observe the Scene view and the mesh in it
Expected result: Some different submesh vertices are connected
Actual result: Different submesh vertices are not connected
Reproducible in: 2022.1.0a1, 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Though this has not been tested locally, the user has mentioned that the problem can be worked around by removing the offset of the baseVertex before calling the method
- The mesh can be restored by right-clicking the "Lightmap UV Gen" Component and selecting "Restore Original Mesh."
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note (fix version 6000.4.0a1):
Fixed in 6000.4.0a1