Search Issue Tracker
Fixed in 2019.2.X
Votes
2
Found in
4.2.0b5
Issue ID
551153
Regression
No
[VCS] Using case sensitivity in Perforce causes files in Unity to claim that they are not part of the workspace
Steps to reproduce :
- create a new folder Users/(user)Projects/newproject
- open P4V and create a new workspace with the root in Users/(user)Projects/
- create a new project in Unity and move it into newproject folder
- open the project in Unity from the new path
- connect to Perforce using the newproject as a workspace
- set the log level to Verbose
- in P4V edit the workspace and change the capital Projects to projects
- create a new file in Unity and notice the warning in the console :
Version Control: Path '/Users/UnityTechnologies/Projects/newproject/New Unity Project 25/Assets/...' is not under client's root '/Users/UnityTechnologies/projects'.
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
enhawk
Jan 09, 2018 08:44
just had this problem, was easily fixable with capitalising the folder name. Seem like a nicer error message would solve this