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
- Crash on SortByExecutionOrder when interrupting the .androidpack import process
- ShaderGraph tab header changes the icon to the VFX Graph icon when ShaderGraph and VFX Graph with the same name are both opened
- The Build Profiles window has usability issues when the panel takes up less than 30% of the screen width
- Inconsistent ShaderGraph RGBA channels compared to the Inspector when "Alpha Is Transparency" is used
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
Add comment