Framerate capped to 30FPS at any resolution over 1080p over HDMI 2.0

[andrewc513]

This has been a lingering issue that I hoped would have gotten sorted out through these patches, but I guess not. :/

Current setup: Win10 x64, GTX 980 (driver 358.50), an Acer B286HK over DisplayPort 1.2, and an LG49UB8200 over HDMI 2.0 Both displays are fully capable of 3840x2160 at 60Hz. I only use one at a time (which depends on the type of game being played) but I have been playing several other games on the TV over HDMI 2.0 at 3840x2160 with a solid 60fps for many months now.

However, Arkham Knight simply cannot do anything more than 30fps on the TV once you go beyond 1920x1080.

What happens is that I can fire up Arkham Knight while on my monitor, and hone in my graphics settings, and I get my detail options just perfect to maintain 60fps at 2560x1440 (single 980 does not cut it for 4K). I quit the game, swap displays, and fire up the game on the TV with the same exact settings. Lo and behold, the settings that were just a moment prior going a full 60fps.... are now going at 30fps.

No combination of Vsync/resolution/detail options would let the game go beyond 30fps unless the resolution gets down to 1920x1080. Even 1920x1200 and all LOW details still only runs at 30fps on the TV. It's almost as if the game can't make the display negotiate signal according to HDMI 2.0 standards. (HDMI 1.4 topping out at 1080p for 60Hz signals) Same results with the latest drivers, and the previous 3 version. If I go back over to my monitor where I'm running over DisplayPort, and everything is back to normal as expected.. I can run at 2560x1440 at 60fps with a mix of high/medium detail settings.

By process of elimination, it must be something with the game itself not playing nicely with 4K displays when connected over HDMI 2.0.

Anyone else seeing this behavior? Known issue? Anything I can do to alleviate this? I'd rather be kicking back on the couch with the game, instead of slouching over my desk just to play at 2560x1440.

[Legion1183]

Game is capped to 30fps because it is a terrible port done by amateurs you have to go into the ini config file found under drive C or what ever drive you have the game on. Then Program Files X86, Steam, Steamapps, common, then find BAK, Engine, Config. You will open BaseSystemSettings using notepad or what you're preference is. ctrl f and type fps there will be a result of MaxFPS=30 change it to 60 or what you're preference is. Aobe that is adjusting abovce 60 may result in stability issues it is hit or miss because the game was designed from the get go for consoles not PC. Above 60 fps it is hit and miss the game was capped to 30 because the textures where built and designed to reneder to the speeds of the xbone 1. Only things we get to make it different is things that are in the NVIDIA gameworks. I have not had issues with above 60 fps my monitor is 120hz I have set it to that turned settings down and all extras off. I did not have stability but my hard drive is 7200 rpm 64mb cache, I despise rocksteady for allowing this. The reason we play here is not to watch a 30fps slide show we want motion picture smooth gameplay. Doing so should allow for the fps to go past 30 just do not be surprised if textures load a little slower since it was a team of amateurs that built the port for PC.

[andrewc513]

With all due respect Legion1183, I think you may have either skimmed over my post or just read the title, and missed the gist of what I'm describing. There's no inherent cap that I can't get past-- I clearly stated that I could run at 60fps at 2560x1440 on my 4K monitor over DisplayPort 1.2 fine. It's just the specific situation of displaying over to a 4K TV via HDMI 2.0 that the framerate seems to be stuck at 30fps once you go beyond 1920x1080.

However, to entertain the idea, I did in fact up that value to 60 in my own testing beforehand, and it has no bearing on the issue. And with the BaseSystemSettings file being unedited, there was never a problem getting 60fps. (With the exception of the bug at hand in this post, of course)