ch1nas3n
Published
DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 gamemoderun %command%
If DXVK_FRAME_RATE was used, the mouse movements became choppy while playing the game. If a frame rate cape is needed, use the console or change the config file (seta com_maxfps). See the pcgamingwiki page for more information.
Futher more, when trying to use Mangohud, my game instantly crashed on mission start-up. Disabling/not using Mangohud solved this problem ofcourse.
gamemoderun mangohud DXVK_FRAME_RATE=90 %command%
Mission loading times are a bit long, because of the usage of the option "shader caching". While playing there were various moments where the game stuttered.
The ~45 FPS cap has been fixed and the game will play substantially better. Dare I say, even OOTB.
A possible fix is to lower the polling rate of your mouse. This is not the only Call of Duty game that has this issue. Atleast, it is not as bad as running Call of Duty Black Ops with a CFS scheduler.
Got a crash during a cutscene. Restarted the game and I watch the same cutscene and play the mission.
Personal note
State of the game
It was recommended to either play the game with the ~45 FPS cap or use another way to make the game more playable. I'm not fond to use the other way that was described on various forums, so I have left the game alone. Since the MW2 remaster issues is fixed with a DXVK commit* and I have finished that game. I was eager to find out how this game ran after a few years. I'm not sure when this is fixed, but I am grateful to the person(s) that have fixed this issue.
- DXVK commit - https://github.com/doitsujin/dxvk/issues/3227
Launch Options
I used the following launch options for this game. These launch options are not necessary and are based on my hardware configuration or my wishes.
Launch options
"mangohud DXVK_FRAME_RATE=156 WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,16,17,18,19,20,21,22,23 %command%"
More information
- manghohud: to confirm the previous ~45 cap was solved.
- DXVK_FRAME_RATE: I use a VRR display, so I cap the game to stay in my display's VRR range.
- WINE_CPU_TOPOLOGY: The game runs on a 7950X3D, I benefit from pinning the game on the VCache CCD.
WIN_CPU_TOPOLOGY=3:0,1,2 DXVK_FRAME_RATE=60 gamemoderun ENABLE_VKBASALT=1 %command%
Expect texture shimmering if you are playing without unofficial fixes and patches
Frame rates above 60 caused some bugs
WINE_CPU_TOPOLOGY=16:0-7,16-23 DXVK_HUD=compiler mangohud %command% -dx11
WINE_CPU_TOPOLOGY=16:0-7,16-23 DXVK_HUD=compiler mangohud %command% -nostartupmovies
WINE_CPU_TOPOLOGY=16:0-7,16-23 DXVK_HUD=compiler mangohud %command%
VKD3D_FRAME_RATE=90 MANGOHUD=1 WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,16,17,18,19,20,21,22,23 taskset -c 0-7,16-23 %command%
Using Vulkan as API, the game ran with a lower average frame rate. Use either DirextX 11 or DirectX 12.
8x TSSAA has ghosting issues.
WINE_CPU_TOPOLOGY=16:0,1,2,3,4,5,6,7,16,17,18,19,20,21,22,23 gamemoderun ENABLE_VKBASALT=1 mangohud %command%
This game needs a fix for GWFL. For more informatiom, please visit the following link. https://steamcommunity.com/sharedfiles/filedetails/?id=1904482007
With Proton version 4.11-13, GFWL installation script "can" succeed. If it does, the game is playable. Unfortunately, no game progression nor settings are saved. Using the fix, a proper offline profile is made and progression/settings will be saved.
DXVK_HUD=compiler,pipelines RADV_PERFTEST=gpl mangohud MANGOHUD_CONFIG=read_cfg,offset_y=75 gamemoderun %command%
Stuttering issues without GPL
RADV_TEX_ANISO=16 DXVK_HUD=compiler DXVK_FRAME_RATE=60 mangohud %command% -offline -offline_mode
Changed or disabled several things in the videoSettings.ini:
- Bloom
- MaxRefreshRate
- Motion blur -WindowStyleFinal
Cloud syncing of saves does not appear to be supported.
Tom Clancy's Splinter Cell Blacklist is a typical old Ubisoft game with CPU affinity problems. It only runs on core0 (this can be fixed with the taskset -cp command) and seems to use a maximum of two cores when changing the cpu affinity. Unfortunately, this has to be done when the state of the process (application) changes. For example, when a cutscene is played, the process goes to sleep. After the cutscene, the game only uses core0 again. This can be monitored with btop or htop and mangohud.
The game can be played without using the taskset cpu affinity fix, but will have worse frametimes (atleast on my system).
As listed by other users, the following fixes needs to be applied:
- Deleting or renaming systemdetection.dll file
- Using the offline command "-offline -offline_mode"
gamemoderun mangohud DXVK_FRAME_RATE=140 %command%
