Search Issue Tracker
Fixed in 2019.2.X
Won't Fix in 5.6.X, 2017.4.X
Fixed in 2018.3.X, 2019.1.X
Votes
2
Found in
5.6.1f1
Issue ID
934940
Regression
No
[Perforce] "Invalid AssetDatabase path" warnings when files outside of perforce are checked out
Steps to reproduce:
1. Set up Perforce workspace
2. Create project at least a level deeper than root directory
3. Create another folder in the root
4. Add files to the other folder
5. In the Editor set VC to Perforce and open Version Control window
6. In P4V, mark files from other folder for checkout
7. In the Editor observe warning messages show up:
"Invalid AssetDatabase path: D:/UnityProjects/PerforceInvalidDatabasePath/TestFolder/Egg.png. Use path relative to the project folder."
Expected: No errors show up, In VC window the files maybe don't even show up
Actual: Errors spammed in the console about an Invalid AssetDatabase path
Reproduced on: 5.5.4p1, 5.6.1f1, 2017.1.0p2, 2017.2.0b5, 2017.3.0a2
Note: Check correspondence with user for examples of file hierarchy and repro video
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
DongDodo
Sep 25, 2018 09:42
i getting this warning in version 2017.2.2f1.
BenVlodgi
Jun 29, 2018 22:25
I'm getting this problem in 2018.1.6.f1
Nathan_Timberline
May 09, 2018 20:03
I'm getting this too in version 2017.3.1f1, it's very annoying and doesn't seem to actually be a real problem with anything. I've resorted to just keeping the "Version Control" tab closed unless I'm using it directly. Would appreciate a fix for this or a better work-around.