Commit Graph
4 Commits
Author SHA1 Message Date
TapuukandTapuuk 2cb51103ac fix(game-env): the VRAM cap also caps the shared memory DXGI reports (#2607)
With a single GPU heap DXVK reports the whole heap as shared memory too, so games still saw ~8 GB as shared even with the cap on. Set dxgi.maxSharedMemory to the same value, like BattleNet already does.

Co-authored-by: Tapuuk <177422350+Tapuuk@users.noreply.github.com>
2026-11-14 14:50:12 -05:00
MaxsTechReview ea48036811 fix(game-env): the VRAM cap also applies to D3D9 games (#2372)
* fix(game-env): the VRAM cap also applies to D3D9 games

DXVK's D3D9 frontend ignores dxgi.maxDeviceMemory, so set d3d9.maxAvailableMemory to the same cap.

* fix(vram): leave DXVK's lower per-game D3D9 limits in place above the 4096 MiB default
2026-11-11 20:55:30 -05:00
Kurt Himebauch 6a681bcbc2 docs: clarify DX12 budget consumers and physical limits (#2148)
* docs: clarify DX12 budget consumers and physical limits

* docs: record controlled Thor gameplay limits
2026-11-05 19:04:11 -05:00
Kurt Himebauch d64205ba5b fix: report Vulkan memory budgets without rejecting allocations (#2014)
Extend the VRAM setting to Vulkan memory-budget reports for DXVK and D3D12 while preserving real heap capacity and allocation results, removing the hard rejection that caused game crashes in FIT and Discord tests.
2026-11-05 17:25:54 -05:00