Search Issue Tracker
Fixed
Votes
12
Found in
2019.1.1f1
Issue ID
1156397
Regression
Yes
Environment variables dropped when using Unity Hub 2.0.0
How to reproduce:
1. Open cmd and write the following:
cd C:\Projects\Unity\HubBug_01
set PATH=%PATH%;C:\Projects\Unity\HubBug_01
set FOO_BAR=HelloFooBar
"C:\Program Files\Unity Hub\Unity Hub.exe"
2. In Hub, open "HubBug_01" project
3. Observe Console
Expected result: "Path: C:\Projects\HubBug_01" and "Foo bar: HelloFooBar" are printed
Actual result: "FOO_BAR not defined." is printed, nothing about path is printed
To get the expected result rewrite step 1 with last line changed:
"C:\Program Files\Unity\Hub\Editor\2019.1.1f1\Editor\Unity.exe" -projectPath
Reproducible with: 2.0.0
Not reproducible with: older Hub versions (user states, I was unable to test)
-
andrewpey
Dec 08, 2019 17:35
-
vmc_petter
Nov 19, 2019 02:03
This is a major problem for us as well.
Needs to be fixed asap.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Environment variable passing fixed in Hub v2.1