Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.1.0f3
Issue ID
935329
Regression
No
Mesh Renderer field Max Angle fails to stitch objects with a specific number in Lighting Object maps Preview
Steps to reproduce:
1. Download project "Auto UV Max Angle misbehavior.zip" and open in Unity
2. Open scene "Show Scene"
3. Click on one of the objects in which name is "45°"
4. Go to Lighting tab -> Object maps -> Preview
5. Choose Realtime Charting
Expected: objects "45° (Max Angle = 29°)" and "45° (Max Angle = 28°)" should be stitched in Lighting tab Object maps Preview
Actual: objects are not stitched
Reproduced on: 2017.3.0a1; 2017.2.0b4; 2017.1.0f3; 5.6.3f1; 5.5.4p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
Add comment