Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a6
2019.3.0a11
Issue ID
1172861
Regression
Yes
[Perforce] Errors are constantly spammed when Inspecting scripts that are outside of the client's root
How to reproduce:
1. Create a new project in your prefered workspace
2. Connect it to Perforce
3. Open the Package Manager and add a package from disk (For example, render pipeline core from: https://github.com/Unity-Technologies/ScriptableRenderPipeline)
4. In the Project Window, open the added package's folder and select any of its scripts
Expected result: no errors are thrown
Actual result: errors about the script being outside of the client's root are constantly thrown and the Editor performance is hampered
Reproduced in: 2019.3.0a11, 2019.3.0a6
Not reproducible in: 2019.3.0a5, 2019.3.0a1, 2019.2.0f1, 2019.1.13f1, 2018.4.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Add comment