Search Issue Tracker
By Design
Votes
1
Found in
2018.3.8f1
2019.1
2019.2
2019.3
2020.1
Issue ID
1173450
Regression
No
[Hub] Hub resets the Environment Variable path
Reproduction steps:
1. Open "Environment Variables..." -> "New..."
2. Set "Variable name" to "HOME" and "Variable value" a different path than the default ones (If the default is Disk C, then use Disk D)
3. Open "testpath.zip" project with Hub
4. "Test" -> "Print Home"
5. Notice in the Console that the output is not the path set to the "HOME" variable
6. Open "testpath.zip" project without Hub (Clicking the Unity.exe in File Explorer and opening an existing project)
7. "Test" -> "Print Home"
8. Notice in the Console that the output is the path set to the "HOME" variable
Expected Result: Hub doesn't reset the Environment Variable path
Actual Result: Hub resets the Environment Variable path
Reproduced with: 2020.1.0a12, 2019.3.0b10, 2019.2.12f1, 2019.1.14f1
Did not reproduce on: 2018.4.12f1, 2017.4.34f1
Hub Version: 2.1.3
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Closed as By Design following review with the dev team. This is an unsupported feature which could involve high risk to implement, so to maintain the stability of the product it was decided to close the issue.