Search Issue Tracker
Fixed in 5.3.5
Votes
48
Found in
5.3.4f1
Issue ID
790006
Regression
No
[Lighting] 'Bake Direct' job failed with error code: 5
1) Download the attached project
2) Open 30HzSample scene
3) go to the lighting window and press bake
4) observe the repeating error mentioned above
5) Observe the bake job never finishes.
Expected behavior:
Scene will bake with out error
Actual Behavior:
the follwing error is shown and light baking never finishes
''Bake Direct' job failed with error code: 5 ('Failed reading Bake Visibility Buffer file.').'
Error occurs <10 seconds after baking light.
Possible workaround, delete the GI Cache.
Goto Edit > Preferences, then GI cache then 'Clean Cache'
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
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
stocks109
Jan 06, 2017 17:07
Has anyone found a reliable way to fix this issue? Deleting the cache beforehand doesn't fix it.
Nearo1
Dec 20, 2016 08:48
'm on 5.5.0f3. This bug is still present and it's driving me crazy too.
FurDee
Dec 06, 2016 07:17
I'm on 5.5.0f3. This bug is still present and it's driving me crazy.
Jesper-Mortensen
Aug 18, 2016 12:34
This issue is an upgrade problem that is caused by having stale files in the GI cache. It is a failure on our side to properly track when files in the cache cannot be reused and must be recomputed. Basically cache content from 5.3.4f1 is not compatible with any of the later versions until 5.3.5p7 when we properly detect this issue and recompute the files. In order to resolve this issue the GI cache must be cleared. This is done by pressing 'Clean Cache' in 'Edit->Preferences->GI Cache'. Alternatively, upgrading to 5.3.5p7 will also fix the problem (as the cache will be cleared by the system).
eightbitz
Jun 27, 2016 08:56
I encountered this when porting my project from 5.3.4f1 to 5.3.5f1 on upgrading my Unity installation. I started disabling groups of objects until it went away. I enabled all but the last group of objects and it didn't reappear. Re-enabling that last group of objects in the scene caused it to appear again. By doing the same thing with the individual objects in the group, I was able to find the single object that was throwing the error on bake. I moved the object slightly in the scene and the error went away. Now everything's back to normal for me.
BadPritt
Jun 21, 2016 11:26
Upgraded to 5.3.5p4, since we were having issues building for the Rift and a light probe bug got fixed. Everything worked fine, except for this light-bake issue.
We need bigger maps for the GearVR to avoid a lot of smaller draw calls, so the smaller size light maps are not an option for performance. The light probe bug in earlier versions require us to upgrade at some point soon. Would be nice to have this fixed soon.
Morph
Jun 17, 2016 22:35
Found a workaround for me: I set Baked GI -> Atlas Size from 1024 to 512. Works for now but this should be fixed soon.
keepthachange
Jun 17, 2016 15:05
v5.3.5f1 i get this error, but its still playable. I am forced to use real time bakeing till its fixed
VincentMarin
Jun 15, 2016 06:33
Same problem after updating to 5.3.5f1
FairGamesProductions
Jun 05, 2016 16:30
Same issue for me in 5.3.5f1
Changing Atlas Size from 1024 to 2048 fixed the issue, but switching back to 1024 brings it back.