Unity Issue Tracker - Having a workspace path with non-ASCII characters causes the connection to the Perforce server to fail when connecting
Closed
UUM-32798
Having a workspace path with non-ASCII characters causes the connection to the Perforce server to fail when connecting
Unity: Version Control
Windows
Perforce
Won't Fix
6.5.X
6.4.X
6.3.X
6.2.X
6.1.X
6.0.X
2023.3.X
2023.2.X
2023.1.X
2022.3.X
2022.2.X
2021.3.X
2020.3.X
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.
Reproduction steps:
1. Create a new project in a path that contains Non_ASCII characters
2. Open P4V
3. In the “Server:” section write localhost:1666
4. In the “User:” section, click on the New… button and fill in everything that is required, and press Save (email doesn’t need to be valid)
5. In the “Workspace” section, click on the New… button and change “Workspace name:” to something simple
6. Change the “Workspace root:” path to the newly created project folder and press ok
7. A window might pop up notifying that folder is not empty. Click on the No button
8. In the Open Connection window select OK and a created connection with project files should appear
9. In the Editor, go to Edit > Project Settings > Version Control
10. Change “Mode” to Perforce and fill in the Username; Password; Workspace; Server with the information used in server creation.
11. Click on Connect
Expected result: Connected to the Perforce server
Actual result: “Not Connected. Couldn’t fstat the project root directory…” error