Monday, September 14, 2026

Separate-process renderer for GTA IV called b-bridge

b-bridge by gutbash is a separate 64-bit renderer based on RTX remix and DXVK which frees GTAIV.exe RAM formerly allocated for rendering.

 TL;DR It is a godsend for big modpacks.

"b-bridge moves the entire Direct3D 9 device into a separate 64-bit process. The game keeps a thin 32-bit `d3d9.dll` that forwards every call over a shared-memory channel to a 64-bit server, which renders through DXVK on Vulkan. On the test system this returned about 880 MB of address space to the game and held frame time at parity with in-process DXVK, allowing a 5 GB texture-pack stack to run where the same install previously crashed within minutes."

  • It is developed on nVidia GPU but works OK on AMD GPU too.
  • Works on 1.0.7.0/1.0.8.0/1.2.0.X Complete Edition.
    Note that 1.0.8.0 and later versions are more RAM-hungry. Vanilla 1.0.7.0 with b-bridge allocates up to 1.05 Gb but 1.0.8.0 allocates up to 1.45 Gb with same settings.
  • You must run GTAIV.exe borderless windowed. 
    Use Fusion Fix for this. On vanilla 1.0.7.0/1.0.8.0 use XLivelessAddon/ZolikaPatch BorderlessWindowed=1 .ini setting  + -windowed in commandline.txt.
  • Works OK with -managed GTAIV.exe parameter.
    On 1.0.7.0 RAM allocation is the same with -managed but on 1.0.8.0/1.2.0.X with this parameter game allocates  ~200 Mb less RAM (1.0.8.0 allocates up to 1.25 Gb with -managed, 1.45 Gb without -managed). 


GTA IV 1.0.7.0    1.0.8.0/CE

1.6 Gb            1.77 Gb    D3D9, no b-bridge              
1.6 Gb            1.57 Gb    D3D9, no b-bridge, -managed    
1.05 Gb           1.45 Gb    DXVK bundled with b-bridge             
1.05 Gb           1.25 Gb    DXVK bundled with b-bridge, -managed

No comments:

Post a Comment