How to fix choppiness and stutters in GTA IV

TL;DR - to fix GTA IV stutters if your GPU supports Vulkan try DXVK method, if it doesn't support Vulkan then go to 4-step DxWrapper method (should help in all other cases). Do not combine methods below, use only one of them! If you are still not satisfied with gameplay then you may have to read the rest of the article and/or downgrade to version 1.0.4.0

---

Contents

The problem.. 1

The solution. 2

DxWrapper method (should help in most cases). 2

dgVoodoo method. 2

WineD3D method. 3

DXVK method. 3

Summary table. 3

Appendix. 4

Why default D3D9 output is slow.. 4

Total VRAM in GTA IV.. 4

-managed GTA IV commandline.txt parameter. 4

GTA IV VRAM management with different methods. 4

Default D3D9 with dxwrapper. 4

Wined3d. 5

dgVoodoo. 5

DXVK. 5

Reference links. 6

 

The problem

If your game starts OK but stutters like crazy when you’re driving in Algonquin near the park or flying in a helicopter near a bridge, read on.

I tried everything apart from 1.0.4.0 downgrade that was claimed to fix the problem:

·         draw distance tweak (far clip)

·         shadow fix (older version shaders for deferred_lighting)

·         increase memory limit in pc\stream.ini

·         different commandline.txt params that remove limits like -nomemrestrict -norestrictions -percentvidmem 100 -availablevidmem {N} -reservedApp 0 -managed

·         disable hyperthreading in BIOS setup (Xeon E5-2689 8c/16t CPU)

·         set high priority for game exe

The methods above helped FPS a little but did not fully address the stutter issue – it still kicked in after driving around a little.

The solution

During my research I found that many people reported enabling steam overlay helped them and – surprise! - DXVK works magic on GTA IV e.g. even translating Direct3D calls to Vulkan is faster and has consistent fps+frametime. So I came to the conclusion that the game itself is not the culprit here and choppiness/stutter is clearly a renderer issue as this crappy legacy D3D/DDraw renderer problem is very common with older games and it’s usually solved by:

1.       Fixing native Windows D3D9 renderer with DDrawCompat – game looks as intended, gameplay is pretty smooth

2.       Avoiding slow native renderer altogether and translating output to superior DX11, OpenGL or Vulkan renderers – game looks nearly as intended, gameplay is silky smooth, 3-5 fps may be lost in translation 8) but DXVK method may even yield fps!

I tried different methods from two groups above with GTA IV and they were the only reliable ones that helped to achieve smooth gameplay and consistent frametime in Algonquin.

DxWrapper method (should help in most cases)

ATTENTION: if you have fairly recent GPU that supports Vulkan you may probably get smoother experience by using DXVK method below! Remove DxWrapper if you later decide to go with DXVK.

·         Install Ultimate ASI Loader (already installed in FitGirl repack, file dsound.dll). You must download 32-bit version Ultimate-ASI-Loader.zip, it contains dinput8.dll, unpack it to GTA IV folder and (optionally) rename it as dsound.dll

·         Download dxwrapper (the guide was tested on v1.0.6334.21 which loads DDrawCompat v0.2.1 by default. Later versions not tested), unpack dxwrapper.asi/.ini into GTA IV folder or plugins subfolder

·         Edit dxwrapper.ini
  [Compatibility]
  DDrawCompat                = 1

·         ATTENTION: DDrawCompat on multi-core CPU will load 1st core at 100% by default. To load cores evenly the following must be enabled in dxwrapper.ini:
[DDrawCompat]
 DDrawCompatNoProcAffinity  = 1

For recent dxwrapper versions in this section also set
DDrawCompat21 = 1

---

  Optionally may enable antialiasing here if it is not already enabled in nVidia/AMD driver settings:

  [d3d9]
  AntiAliasing               = 1

Optionally may also enable borderless windowed mode here (don’t forget to disable it in FusionFix):

[d3d9]
 EnableWindowMode           = 1
 FullscreenWindowMode       = 1

 

If the game crashes with "D3D reset failed" message after changing graphics setting while playing try EnableD3d9Wrapper=1 parameter in dxwrapper.ini. This parameter is required to enable D3D9 wrapping code in recent versions of dxwrapper.

(Fir AMD GPUs only) in Radeon Software/Adrenalin find AMD shader cache setting and set it explicitly to "On" instead of default "AMD Optimized". (both tips contributed by user MagicAl6244225)

 

Pros:

·         Game looks as intended - native renderer is used

·         Fast, as it does not translate anything, just fixes output

·         Has rudimentary antialiasing

Cons:

·         older DxWrapper version may sometimes freeze when you quit the game, fixed in latest version.

·         FusionFix's cutscene definition fix may not work, YMMV.

 

dgVoodoo method

Read reference article #2 in Reference links

Quick guide

1. Download dgVoodoo2.
2. Put dgVoodoo.conf, dgVoodooCpl.exe, D3D9.dll from MS\x86 to GTA IV folder
3. Run dgVoodooCpl.exe, on DirectX tab configure VRAM size (it is saved in dgVoodoo.conf), and disable dgVoodoo Watermark, press Apply
4. Add to commandline.txt line -availablevidmem {N} where {N} is the same size as VRAM for dgVoodoo virtual adapter in dgVoodoo.conf

Pros:

·         Silky smooth with DX11 (DX12 in latest WIP builds) renderer

·         many antialiasing options

·         pretty stable and problem-free e.g. starts / exits OK

Cons:

·         A little slower than dxwrapper

·         default watermark - must turn it off in configurator

·         night lights are visible through solid walls or helicopter

 

WineD3D method

Read reference article #1 in Reference links

Quick guide

1. Download WineD3D. For OpenGL output download Pre-Vulkan v4.5. WARNING: game start not guaranteed, latest version at the time of writing v5.13 did not work for me at all, v4.5 sometimes may also not start, YMMV.
2. Unpack d3d9.dll, libwine.dll, wined3d.dll to GTA IV folder

Pros:

·         silky smooth - framerate/frametime are rock solid and more stable than with dxwrapper.

Cons:

·         Must change the resolution on the first run - it will start correctly next time

·         often can't start the game at all – must remove -managed from commandline.txt and/or try different earlier builds, YMMV

·         3-5 fps slower than DxWrapper

 

DXVK method

Read reference article #3 in Reference links

Quick guide

1. Make sure your GPU is Vulkan-capable and you have installed latest release or beta drivers for it
2. Download DXVK. ATTENTION: DXVK after v2.0 requires Vulkan 1.3 compatible driver. If your GPU/driver supports Vulkan 1.2 or lower you must download DXVK v1.10.x or earlier!
3. Unpack .tar.gz file, put d3d9.dll from dxvk-{version}\x32 subfolder to GTA IV folder. File dxgi.dll from DXVK is optional on Windows as game will work without it and it may cause problems with DXVK 1.8.1 and above.
4. (This step is optional for later DXVK builds) Create in GTA IV folder file dxvk.conf that contains
   dxgi.maxFrameLatency = 1
   d3d9.maxFrameLatency = 1
5. Add to commandline.txt line -availablevidmem {N} where N should be a little less than actual VRAM size e.g. for 2Gb GPU specify 1983 and not 2048 here. To find the exact number run dxdiag and look for the "Display Memory" on Display tab or start the game with default D3D9 renderer and ExtendVidMem (read "Total VRAM in GTA IV" in Appendix), look in ExtendVidMem.log that was created.

Running GTA IV with DXVK v2.X

Later DXVK versions use Vulkan 1.3 feature Graphics Pipeline Library (GPL) to improve rendering. It compiles shaders for graphical pipelines beforehand and manages pipelines so there's no need to maintain cached pipelines in state cache file. The shaders are mostly precompiled during game launch and loading screens.

ATTENTION: GPL implementation is very driver-dependent and some late nVidia drivers have memory leaks and Vulkan settings that may cause problems with DXVK and GTA IV. I had hitches in 7 of 10 game launches on affected nVidia drivers 535.98, 536.23 (Vulkan v1.3.241). Older 531.79 (v1.3.236), beta Vulkan driver 532.17 (V1.3.250) and 536.40 (v1.3.241) work OK.

How to test if your driver is affected

• Create new savegame in Broker safehouse to spawn at night e.g. go to bed at 19:00
• Enable HUD in dxvk.conf (dxvk.hud=full) or use other OSD e.g. MSI Afterburner to display frametime graph
• install Fixed Shaders Collection (for 1.0.7.0 and above) or latest FusionFix (for 1.2.0.x) that bundles it
• Delete or rename state cache file GTAIV.dxvk-cache
• Launch the game, it should load your newest "Broker safehouse at night" savegame.
• After spawn in the apartment rotate the camera - there should be no frametime spikes
• Go downstairs and out - there should be no freeze when you open the door to the street
• Drive right along the bank to the docks - there should be no frequent hitches that feel like stutter during driving
• If your game has been butter smooth so far exit the game and retest at least 10 times

Workarounds if your driver is affected but you can't install another one:

• Use DXVK-gplasync, enable async and state cache in dxvk.conf
  dxvk.enableAsync = True
  dxvk.gplAsyncCache = True
  This will not eliminate hitches when shaders are compiled for the first time but will make hitches less severe and fully eliminate them on subsequent launches after state cache is saved.
• (Not recommended) disable GPL in dxvk.conf with dxvk.enableGraphicsPipelineLibrary=False, this will enable old pipeline generation mechanism and state cache file.

Running GTA IV with older DXVK versions

(for Steam users) disable Vulkan shader caching in the Steam options (the tip contributed by user MiesThies). DXVK must be able to read/write to its state cache file and it is crucial for removing stutters, see "State cache" section at DXVK page for details. The file is called GTAIV.dxvk-cache and by defailt it is created/modified by DXVK in game folder where GTAIV.exe is but Steam may mess with this and redefine DXVK state cache location to something like {path}\steamapps\shadercache\12210\DXVK_state_cache where DXVK may have trouble accessing it.

DXVK may at first be laggy as it builds state cache, it is normal - the more you play the smoother it will become e.g. do several missions or run built-in benchmark at least 3 times and you will see.

If the game starts OK and after loading your savegame it shows black screen with only minimap and mission marker or skydome visible the workaround is to reinit display. Go to Graphics settings and change shadow quality, press Space to apply - this will reinit display and everything will become visible, then press Esc several times to revert to your original shadow setting and return to the game.

Pros:

·         silky smooth

·         higher fps than any other method, YMMV

·         full VRAM utilization using -managed

·         built-in frame rate limiter (only for versions 1.9+, to enable put d3d9.maxFrameRate=60 into dxvk.conf)

Cons:

·         nVidia driver antialiasing options do not affect DXVK Vulkan output. DXVK built-in MSAA only works on very old games and not on GTA IV. As a workaround you may enable antialiasing with DXVK using SweetFX.

Summary table

 

Method	Renderer	Smooth	Start / exit	FPS	Game looks	Anti aliasing
DxWrapper	Default D3D9	☆	☆	☆☆	☆☆	☆
dgVoodoo	DX11/12	☆☆	☆☆	☆	☆	☆☆
WineD3D	OpenGL (v4.5), Vulkan	☆☆	☆	☆	☆
DXVK	Vulkan	☆☆	☆☆	☆☆	☆☆	☆

 

So there you have it - test for yourself and choose whatever fits your configuration. Feel free to share your experiences with different methods and your specs in comments below.

Appendix

Why default D3D9 output is slow

Possible causes are:

·         Low-end GPU. It is not the main culprit as even the most low-end GPU e.g. gt610 that I used to have on my old rig is capable of smooth output via alternative renderer (as shown by WineD3D and dgVoodoo).

·         Poorly optimized driver. Example: on the same Xeon E5-2689 PC with Windows 10 build 2004, GTA IV default D3D9 output on gt610 with older driver very rarely loads all cores and is choppy, but on gt730 with the latest 451.67 driver all cores are loaded and default D3D9 output is very smooth. Of couse these GPUs have different number of shader units and different architecture, but nevertheless underutilization of CPU cores on older driver exists.

·         Poor compatibility of a driver with particular Windows build. It is confirmed, that older driver that was developed for earlier Windows build may not perform as well on newer Windows build, and newest driver that was developed for latest Windows build may not perform as well on earlier Windows build. So you should try your luck with latest beta drivers for your specific Windows build.

·         DirectX implementation specifics on different Windows versions. For example, I have no DxWrapper and WineD3D start/exit issues on Windows 7 and on Windows 10 with newest nVidia driver.

Total VRAM in GTA IV

 ExtendVidMem module (dinput8.dll in FitGirl repack)

·         Detects total VRAM and automatically sets -availablevidmem in the game, works for default D3D9 renderer and Wined3d

·          -availablevidmem {N}  in commandline.txt takes precedence over ExtendVidMem. Example for 2Gb VRAM videocard with ExtendVidMem: game detects 2048 mb without -availablevidmem {N}, but detects exactly {N} mb  with explicit -availablevidmem {N} .

-managed GTA IV commandline.txt parameter

This parameter is supported only on GTA IV 1.0.6.0 and above.

By default the game allocates VRAM and loads textures as needed. It results in lags that are due to world loading when Niko walks out from safehouse hall to the street, VRAM usage immediately goes up.

-managed  instructs the game to use D3D runtime managed resources. Using -managed with DirectX does not yield much, but using it with DXVK (which in this case acts as D3D runtime) allows it to preload all needed resources into VRAM e.g. DXVK fully utilizes VRAM during savegame load. This has huge impact on GTA IV performance and overall smoothness – when all needed resources are preloaded the game is enjoyable even on a lowest-end PC with fairly decent GPU e.g. it is silky-smooth at 1280x1024 with High textures, on my ancient Socket 939 Athlon 64 X2 4200+ o/c 2.6 Ghz, 3Gb RAM, gt730 2Gb GDDR5.

GTA IV VRAM management with different methods

The VRAM usage examples in this section are based on the following scenario:

·         walking out of Algonquin safehouse near the bridge, driving along the park to the end of avenue where roadblock is

·         Numbers are as reported by MSI Afterburner for Vulkan-capable Gt730 GDDR5 2Gb at 1280x1024, High texture quality

·         Very low-end Windows 7 PC (2-core Athlon 64 X2 with specs above) so your mileage may vary.

Default D3D9 with dxwrapper

·         Allocates VRAM and loads textures as needed, world loading lag

·         fps less than dxvk, YMMV – on Xeon E5-2689 with newest drivers it is faster than dxvk

~200mb VRAM after game load, ~580mb VRAM at avenue end, number is the same with or without -managed, -percentvidmem 100.

Wined3d

·         Allocates VRAM and loads textures as needed, world loading lag, does not support -managed in commandline.txt – with it the game will have infinite loading screen

·         Works with ExtendVidMem, may use -availablevidmem {N}  in commandline.txt

·         Game load is slowest, probably because it does not support IV.EFLC.ColAccel.asi

·         Lowest fps of all methods, but very stable frametime - overall fps lag but no choppiness during driving

 ~620mb VRAM at avenue end

dgVoodoo

Virtual adapter configuration in dgVoodoo.conf:

  [DirectX]
     VRAM = {N}

{N} should not be the exact amount of VRAM but a little less e.g. for 2Gb videocard enter 1983 here and not 2048, or else the game may not load savegame. To find the exact number run dxdiag and look for the "Display Memory" on Display tab or start the game with default D3D9 renderer and ExtendVidMem, look in ExtendVidMem.log that was created.

·         Requires explicit -availablevidmem {N} where {N} is the same size as VRAM for dgVoodoo virtual adapter, without it GTA will use default VRAM size 512 mb and may drop texture quality to low.

·         -managed works, loads world/textures more aggressively

·         Still does not use full amount of VRAM even if it is available: preloads much of the textures during game load, no major stutter/choppiness, but has noticeable lags when loads new world/textures.

·         Second fastest after dxvk, YMMV

~230mb after game load, ~700mb VRAM at avenue end without -managed
~400mb after game load, ~900mb VRAM at avenue end with -managed

 

DXVK

May have in dxvk.conf:

dxgi.maxFrameLatency = 1
d3d9.maxFrameLatency = 1
d3d9.maxAvailableMemory = {N}      (optional. Explicit N that you specify here will be reflected in GTAIV_d3d9.log)

·         Requires explicit -availablevidmem {N} in commandline.txt, without it GTA with dxvk will detect only 512mb. Cannot rely on ExtendVidMem to automatically supply VRAM size, it is recommended to disable it. To find the exact {N} run dxdiag and look for the "Display Memory" on Display tab or start the game with default D3D9 renderer and ExtendVidMem, look in ExtendVidMem.log that was created.

·         Full VRAM utilization, with -managed all textures are preloaded during savegame load and walking out safehouse to avenue is not choppy as with wined3d.

·         Aggressive VRAM allocation using -managed -nomemrestrict may crash the game with error dialog
GTA IV FATAL ERROR: RESC10
 GTA IV FATAL ERROR: Out of video memory - Please re-boot your system
3145272 696725

·         On a system low on RAM game may crash on savegame load or after the game loaded and Niko drove around Algonquin a little bit with error in GTAIV_d3d9.log
err:   DxvkMemoryAllocator: Memory allocation failed

·         Very low CPU utilization, good for low-end systems

·         has built-in MSAA (untested), nVidia driver antialiasing options do not affect DXVK Vulkan output

 

With -availablevidmem 1983:

·         1061mb without explicit d3d9.maxAvailableMemory in dxvk.conf

·         1061mb with explicit d3d9.maxAvailableMemory in dxvk.conf but with -percentvidmem 100 in commandline.txt

·         1189mb with explicit d3d9.maxAvailableMemory = 1983 in dxvk.conf
   1190mb without -reservedApp 0  in commandline.txt
   1446mb with -reservedApp 0 -nomemrestrict in commandline.txt. -norestrictions does not affect VRAM usage, it just allows to set arbitrary graphics settings in the game even if your videocard does not support them, by default the game does not allow that.

·         1902mb with -managed, game may freeze/crash on low RAM system as DXVK will be unable to allocate more RAM on loading comedy or cabaret club. Possible workaround is to lower -availablevidmem or remove -nomemrestrict and add correct -memrestrict {value}

 

 

Reference links

1.       Translation to OpenGL using WineD3D https://steamcommunity.com/sharedfiles/filedetails/?id=691816599

2.       DirectDraw output fix using DxWrapper or translation to DX11 using dgVoodoo - if WineD3D/Vulkan does not work for some reason https://steamcommunity.com/sharedfiles/filedetails/?id=1573821562

3.       Translation to Vulkan using DXVK https://www.reddit.com/r/pcgaming/comments/gsn6w8/dxvk_works_magic_on_gta_iv/