Search Issue Tracker
Active
Under Consideration for 3.15.X
Votes
0
Found in [Package]
3.15.3
Issue ID
HUBX-1596
Regression
Yes
[Windows 11 ARM] Providing command line options -a arm64 or --architecture arm64 downloads wrong editor architecture (x64)
Steps to reproduce:
- Open terminal (CMD)
- Try downloading any Unity editor using -a arm64 or --architecture arm64 command line options
- Example: "C:\Program Files\Unity Hub\Unity Hub.exe" -- --headless install --version 6000.3.0f1 --changeset d1870ce95baf -a arm64
\\
Actual results:
Version is downloaded with x64 architecture not ARM64
Expected results:
Version is downloaded with ARM64 architecture
\\
Reproducible with versions:
3.15.3
\\
Tested on (OS):
Windows 11 ARM 64
\\
Notes:
- Works as expected on MacBook M1 machines
- https://docs.unity3d.com/hub/manual/HubCLI.html - states these command line options should work
- Providing NO options, the downloader defaults to the correct architecture ARM64
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
- Shader Graph template titles blink and render incorrectly in “Create New Shader Graph Asset” window
- Profiler Captures List foldouts do not open when clicked on the foldout title
Add comment