Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.1.0b3
Issue ID
988324
Regression
No
[ReflectionProbe][VCS] Trying to bake only reflection probes while using perforce integration throws error instead
Steps to reproduce:
1. Set up perforce server and workspace
2. Create project inside workspace
3. Enable perforce integration and connect to server
4. Create new scene, disable Auto Generate in lighting window and add a Reflection Probe to scene
5. Save scene
6. Back in lighting window, click "Generate Lighting"
7. Open Version Control window and submit your changes
8. Return to lighting window and in dropdown near Generate Lighting click Bake Reflection Probes
9. Notice error that access to ReflectionProbe-0.exr is denied
Expected result: ReflectionProbe-0.exr is checked out and reflection probes are baked successfully
Reproduced with: 2017.2.1p2, 2017.3.0p2, 2018.1.0b3, 2018.2.0a1
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a3