Search Issue Tracker
Fixed in 5.0.4
Votes
0
Found in
5.0.1p2
Issue ID
693316
Regression
No
[Lightmap] Static Batching and AssetBundle-Export shift Lightmap-UVs
1) Open the scene "SourceScene". Note that this scene uses a lightmap where all transparent pixels have been colored red. Please don't re-bake the lightmap, otherwise the bugs won't be visible.
2) Export the scene into an AssetBundle using the "Build/AssetBundle" menu.
3) Open the scene "TargetScene" and enter play mode.
4) Press the "Load" button in the Game-UI
5) After loading the scene from the AssetBundle, the game camera should be focused on a scene-part where the UV-shift is most visible. Please compare the placement and size of the red borders along the road with the original mesh in the "SourceScene".
6) Please also take a look at the screenshots "NoStaticBatching.png" and "StaticBatchingAndBundling.png" for a more extreme case from our production-scene.
Reproduced: 5.0.1p2, 5.0.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment