Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a9
Issue ID
609788
Regression
No
Enlighten - initial memory usage information is wrong
To reproduce:
1. Open the example enlighten project
2. Open lightmapping window
3. Clear and wait for it to rebake
4. Note the amount of memory used - for me it's 8mb
5. Open the maps tab and toggle "Compressed" on/off - the memory changes to 2.7mb, which is the correct amount
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
Add comment