Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0b9
Issue ID
922705
Regression
No
Windows Standalone build uses twice the RAM on Vulkan than on D3D11
Windows Standalone build uses twice the RAM on Vulkan than on D3D11. Scene with Main Camera and Directional Light (newly created) uses ~60MB when built for D3D11 vs ~110MB when built for Vulkan.
Reproduction steps:
1. Create new project
2. Set graphics API for Windows to Direct3D11
3. Build and run
4. Observe the RAM usage in Task Manager
5. Close the player
6. Set graphics API for Windows to Vulkan
7. Build and run
8. Observe the RAM usage in Task Manager
Reproduced on: 5.6.0a1, 5.6.2p1, 2017.1.0b9, 2017.1.0f2, 2017.2.0b2
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