Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1059340
Regression
No
Noteable Disparity Between Texel Density of Imported and Generated UVs
Repro:
======
Download attached project. Set Scene View Mode to "Baked Lightmap". From the Lighting Settings window, ensure Baked Global Illumination is enabled. Also ensure "Auto" is enabled or click the "Generate" button. Observe the texel density checkerboard overlays in the Scene view.
Noted:
======
The imported cuboid and planes have notably different texel density between the imported UVs and those UVs generted by the Unity importer.
Expected:
=========
The texel density determined in the Lighting Settings tab should be consistent between objects regardless of whether these have been imported or generated in Unity. In the example project, the UVs are verified as being free of distortion, so this behaviour is unexpected.
Inconsistent texel densities could cause notable seam issues when juxtaposing geometry from different sources. We should be able to handle this.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment