Search Issue Tracker
Won't Fix
Won't Fix in 3.3.X
Votes
0
Found in [Package]
3.0.0-beta.6
Issue ID
HUBX-720
Regression
No
[Hub] Available space does not take temporary files into consideration
Reproduction steps:
1. Open Unity Hub
2. Go to "Installs" > "Install Editor"
3. Select any Unity Editor version
4. Observe the available space
Expected result: The Unity Hub available space matches Systems available space
Actual result: The Unity Hub available space is smaller than Systems available space
Reproducible with: 3.0.0-beta.6
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:
There are no fixes planned for this Bug
Resolution Note (3.3.X):
The available space is correct. However for Mac the system shows the available space in GB, and for windows the actual space is in GIB.
1GB=1000MB
1GiB=1024MB
For the HUB application we calculate and convert the values in GIB for all operating system.
Hence there is a difference in how much available space you see in Mac and in the hub application.
https://massive.io/file-transfer/gb-vs-gib-whats-the-difference/