Search Issue Tracker
Won't Fix
Fixed in 2017.2.X
Votes
0
Found in
2019.4
2021.1
Issue ID
924597
Regression
No
[Build] AssetBundles work incorrectly with GI Data
Lighting Data Asset is not assigned properly when using Asset Bundles with GI features
Steps to Reproduce:
1. Open the attached project (the Loader scene should be opened already - project available below as GIAssetBundleFailure).
2. Re-build Asset Bundles (Build >> Asset Bundles).
3. Play the scene, the test scene should now be the active scene.
4. Open Lighting Settings (Window >> Lighting >> Settings >> Global Maps tab)
5. Observe the Lighting Data Asset is not assigned where it should be (in this project LightingData), instead it says None (Lighting Data Asset).
Reproduced in: 2017.1.0f1, 5.5.0f3
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Resolution Note:
Lighting inspector in Unity Editor uses data that exists only in the Editor. When loading player built data (AssetBundles) the lighting inspector will have nothing to display.