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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment