Search Issue Tracker

Duplicate

Votes

62

Found in

Issue ID

706367

Regression

Yes

Unwrapper gives different results between platforms

Global Illumination

-

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.

  1. Response avatar

    This is a duplicate of issue #754370

    Lighting Data incompatible between Windows and OSX

Comments (17)

  1. 8bd117982e62a8eb89d91171e828964a?d=mm

    kaushik.d

    Feb 04, 2016 05:50

    This seems to be finally fixed in 5.3.2f1. Worked when we baked on Windows with "generate secondary UV's" checked and imported fine on Mac.

  2. C485f9c7daedaa39d763fd66b7dbdb72?d=mm

    littlemuggo

    Jan 08, 2016 19:49

    Please fix. As temp solution, we have to re-bake every scene lightmaps on the platform (ie: iOS/Android) we are building too. This process takes a few hours at least... Please fix!

  3. A354ba6ddf9177cdbee1cfc76cc96591?d=mm

    562873336

    Jan 05, 2016 02:04

    Still happen in 5.3.0 between Mac and Windows(64bit).

  4. 76a6bc9026c968a55e4beb3aaf2ebc7e?d=mm

    jeremyfp

    Dec 18, 2015 20:55

    I like how voting is disabled for a "resolved" issue...

    Consider this a vote. The bug persists in 5.3.0f4.

  5. 65402a59a948474988587b8f4529d3de?d=mm

    variablestatekieran

    Dec 09, 2015 17:19

    This is still an issue with some meshes in 5.3.0f4!

  6. 52943ac6d1a7305ebe6f573de2cb1ac9?d=mm

    cooado

    Dec 03, 2015 04:47

    it's still happening on unity 5.2.0f3 personal edition.
    Baked on windows, messy on mac.
    Baked on mac, messy on windows.

  7. 8bd117982e62a8eb89d91171e828964a?d=mm

    kaushik.d

    Nov 30, 2015 21:14

    This is still a problem in 5.2.x . We have some pretty large levels, and it will be prohibitively expensive to re-bake everything on Macs for the iOS version of the game. Can someone please comment on when this will be fixed?

  8. 8d1210808be7a525b9c0b1cbfea2681e?d=mm

    echo4papa

    Nov 25, 2015 12:42

    Still experiencing this problem in 5.2.3f1 and 5.2.2p4

  9. 6777e24f5a2fcecda1635d049cacd351?d=mm

    masaki.iwasaki

    Nov 11, 2015 08:43

    Still happen in 5.2.2p1 between Mac and Windows(64bit).

  10. 8bd117982e62a8eb89d91171e828964a?d=mm

    kaushik.d

    Nov 05, 2015 13:55

    This is still happening in Unity 5.2. Baking lightmaps in Windows (64-bit 5.2.1f1) and looking fine. But when we export the package into Mac (5.2.0f3 ) the lightmaps are still messed up. Curiously, this is not happening on every scene - some Windows lightmapped scene are working properly on a Mac.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.