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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
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