The config option only has an effect if you're running the game at a refresh rate greater than 60 Hz or with vsync disabled. If you're running this through proton then it probably just doesn't work because the game requests a 60 Hz mode, fshack doesn't actually perform a mode change, but DXVK still thinks it's running at 60 because we still see all available display modes. Not really something we can fix properly on our end without relying on some really dodgy heuristics (which I might implement anyway, but you know, it's still going to be dodgy).
On the other hand I don't want to change DXVK's behaviour here since it would force DXVK's frame limiter on some games even on setups with actual 60 Hz displays, which is just going to result in a terrible experience.
Alright, thank you for the explanation. I'm going to stick with the environment variable for this game then.
@ranplayer The config variable should now work in more scenarios as of https://github.com/doitsujin/dxvk/commit/61025c0079cfc452f0a6e65a022905053f904174
Were you looking for a built in dxvk config so it's capped at 60 out of the box to work around those issues?
I see on pcgamingwiki the game might capped when playing online but not solo? Unless i misunderstand that. Some people on protondb seem to supply the -r argument which i think kicks in the ingame limiter.
This game has the speed tied to the frame rate. For monitors with refresh rates higher than 60 makes the game extremely fast. This issue has been pointed out in the pcgamingwiki as well.
I've tried to lock the frame rate to 60 using the properties
d3d9.maxFrameRate=60anddxgi.maxFrameRate=60with no success, but using the environment variableDXVK_FRAME_RATE=60does work.Software information
System information
Apitrace file(s)
Log files
kofxiii_d3d9.tar.gz