Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1179623
Regression
No
[VCS] UnauthorizedAccessExceptions thrown when interacting with the Probuilder Window under Version Control
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Add the Probuilder package
3. Connect it to perforce and submit the initial project
4. Open the Probuilder Window and click on the "Material Editor" (Tools -> Probuilder -> Probuilder Window -> Material Editor)
5. Observe the console
Expected result: the Probuilder settings file that is located in the project settings folder is automatically checked out when interacting with the Probuilder Window
Actual result: the Probuilder settings file is not automatically checked out and thus throws an UnauthorizedAccessException when trying to write changes to it
Reproducible in: 2020.1.0a2, 2019.3.0b1, 2019.2.3f1, 2018.4.8f1 (With Probuilder Version 4.1.0)
Note: the errors are also thrown when creating scripts or adding other packages
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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note (fix version 1.0.1):
Update the Settings Manager package to version 1.0.1+ in order to fix the issue