Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0b7
Issue ID
964264
Regression
Yes
2017.3 Regression in mesh memory size usage
1. What happened
Profiler reports mesh memory size at around 8-9 MBs for the given scene, while other versions (17.1, 17.2, 18.1) have it at ~300 KBs.
Compared to: 2018.1.0a2, 2017.2.0p1, 2017.1.2p2
2. How we can reproduce it using the example you attached
- Scene 'Scene'
- Play
- See Profiler > Memory > Meshes
>>> It is expected to be similar to other versions ~ 250-400 KBs. Actual: ~8.5 MBs
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