Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a9
Issue ID
1075976
Regression
Yes
[VCS] Building lighting without checking out previously baked lightmaps throws errors and marks baked lightmap for delete
Steps to reproduce:
1. Open attached project in perforce workspace
2. Connect to perforce server and submit project there
3. Open scene SampleScene
4. Bake lighting
- Notice that after baking is done Lightmap files are not checked out
5. Bake lighting again
- Notice errors:
Can't clobber writable file /Users/juliusj/perforce-workspace/lighting-issue/Assets/Scenes/SampleScene/Lightmap-0_comp_light.exr
Can't clobber writable file /Users/juliusj/perforce-workspace/lighting-issue/Assets/Scenes/SampleScene/Lightmap-0_comp_dir.png
Can't clobber writable file /Users/juliusj/perforce-workspace/lighting-issue/Assets/Scenes/SampleScene/ReflectionProbe-0.exr
Reproduced with: 2018.2.6f1, 2018.3.0a9
Partially reproducible: 2018.1.9f2 (only issue in step 4)
Not reproducible: 2017.4.10f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment