Search Issue Tracker
Fixed
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
1
Found in
5.5.1f1
Issue ID
883901
Regression
No
Mesh compression stores incorrect custom data in uv channels when using UnityEditor.ModelImporterMeshCompression.Low
UnityEditor.ModelImporterMeshCompression.Low stores incorrect uv data. Using Medium or High, stored data is correct.
To reproduce:
1.Open attached project
2.Open "Main.unity" scene
3.Select cube in the hierarchy window
4.In the inspector right click on "Mesh Compression Test (Script)"
5.Select "Store World Pos in uv4"
6.Right click on it again
7.Select "Set Compression Low"
8.Save the scene
9.Reload the scene
10.Select the cube from the hierarchy
11.Right click on "Mesh Compression Test(Script)"
12.Select "Log uv4 data"
13.Observe in console as the Transform Position values are different than in the inspector.
Expected result: stored values are the same as in the inspector
Actual result: stored values are different from the inspector
Reproduced on: 5.5.1f1 5.6.0b9
Unable to check for regression because no backward compatibility.
Win 10 Pro.
Screen recording attached.
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