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)
Comments (2)
-
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Environment variable passing fixed in Hub v2.1