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'.
Comments (1)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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