Search Issue Tracker
Duplicate
Votes
62
Found in
Issue ID
706367
Regression
Yes
Unwrapper gives different results between platforms
In 5.x we no longer run the same unwrapper DLL on Windows and Mac. This means that when GI data is built on one platform with a certain set of lightmapping UVs (the realtime GI UVs are based on those, and the baked lightmaps use them too) the UVs produced on another platform during mesh import can be different.
The resulting mesh can thus have a different vertex count.
This is a regression compared to late 4.x.
This is a problem when loading the data built on one platform on another platform the UVs will not match with the output and one will see garbled output in the scene.
The realtime GI UV's patched from the snapshot can have a different count than the vertex count of the mesh and that leads to errors when batching:
"Failed setting triangles. Some indices are referencing out of bounds vertices. IndexCount: XXXX, VertexCount: YYYY"
Currently the only workaround is to rebuild lighting on each Editor platform.
Comments (20)
-
daafdasfa
Nov 02, 2015 15:58
This is NOT fixed in 5.2.2f1. I'm still running into the issue
-
62316e
Aug 13, 2015 21:44
Almost month passed. Any updates?
-
voporak5
Jul 21, 2015 20:08
Happened here too, and we have a system that auto-builds for us over night as well as when any SVN changes are detected so need this fixed asap.
-
gyd
Jul 09, 2015 15:07
it happened to my team even we build on Windows and update to Windows.
is it possible also an issue between 32bit and 64bit?
-
StealthStudiosInc
Jun 29, 2015 20:54
This has been a literal nightmare for us. We have spent weeks trying to 'solve' it until finally finding this page...
-
Tlaxtaquatl
Jun 29, 2015 20:52
This has caused a lot of headaches since my team has some developers working on pc and others on mac
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
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
This is a duplicate of issue #754370