Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.3.2
Issue ID
HUBX-475
Regression
No
[Hub] Project is created in a wrong directory and a wrong drive when using Network Path in the Location field
How to reproduce:
1. Open File Explorer
2. Create a new folder anywhere on your computer and name it "LocalServer"
3. Right-click on the new folder -> Give access to -> Specific people -> Share it with your current Windows user
4. Right-click on This PC -> Map network drive
5. Click Browse -> Select the "LocalServer" folder created in the 2nd step -> Finish
6. Open Unity Hub
7. Click NEW
8. In the Location field insert the Network Path of the Network drive used in the 5th step (e.g. \\\\DESKTOP-QM33MTU\\LocalServer)
9. Give any name to the project and click CREATE
Expected results: the project is created in the specified location
Actual results: the project files are created in the Hub installation directory and an empty folder with the project name is created where the whole project should be
Reproducible with: 2.3.2, 2.4.0
Notes:
-The exact network path can be found by right-clicking on the folder created in the 2nd step -> Properties -> Sharing
-The path format seems to be important for reproducing the issue and using the drive letter won't reproduce the issue
-The correct path is logged to the "info-log.json" file and the correct path is passed to the Editor judging by the "Editor.log" file
-The actual location for me seems to always be the E: drive (usually the folder where Hub is installed but not always) while the network drive is hosted in drive D:
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
There are no fixes planned for this Bug
Resolution Note:
Team looked investigated this issue but did not manage to successfully reproduce it. Closing as this will not be a priority to work on in a near future.