Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
Issue ID
1067913
Regression
No
Scene is marked dirty after subsequent precomputes
When precomputing multiple scenes sometimes the localfileID of the lightingdata asset reference in a scene file will change. This will happen even when the number of scenes involved in the bake doesn't change. This is a problem for teams that use perforce and have exclusive check out turned on for scene files. Prevents a build machine from checking in bake lighting results and results in broken light bakes. Really big productivity issue for any team baking lighting and using perforce.
I "think" the following code in WriteLightingDataAssetJob.cpp on line 211,
// Get rid of existing LightingDataAssets
if (m_OnDemandBake)
LightingDataAsset::DestroyLightingDataForLoadedScenes(false);
maybe the cause of this. Don't think it's guaranteed for the lightingDataAsset to be assigned the same instance Id after deletion.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment