Search Issue Tracker

By Design

Votes

0

Found in

2017.4

2019.3.0f6

2020.2

Issue ID

1215266

Regression

No

Cannot create a new Unity project in a shared network folder with r/w access

Asset - Database

-

Reproduction steps:
1. Set up a shared folder on a device in a local network with read/write access
2. Connect to that folder using another device in the network
3. Try creating a Unity project in the shared folder

Expected result: the project will be created
Actual result: the project is not created and you get an error message offering you to force quit. Force quitting throws a Fatal Error. The project created in the shared folder is not recognized by the Unity Hub (check note 3 and the images attached)

Reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b1, 2020.2.0a2

Notes:
1. In 2018.4.19f1 and earlier the project is created without any visible errors. Unity is trying to launch but never does
2. This was tested: local network set up on Mac High Sierra, connecting via iMac Catalina
3. Some files are created such as Assets, Logs, Temp, but this varies between versions. Hub recognizes that it is a project but is not able to launch it indicating that it does not have the Unity version on the machine (the version is unidentified).

  1. Resolution Note:

    Unity requires the use of memory-mapped files to work correctly, which in some operating systems doesn't work well or at all over network shares; due to that, opening projects from network shares is not supported.

Add comment

Log in to post comment