V-sync issue in Wolfenstein 2 [AMD]

gegennaro102

Prominent
Nov 4, 2017
4
0
510
I've got an i5-6600k, RX 480 and 16gb of RAM, so I'm easily into recommended requirements.

When I turn on v-sync with Uber settings, frame rate drops from 60 to 30 fps causing a tremendous slowdown that affects gameplay.

If I disable v-sync, frame rate goes between 50 and 60 fps (sometimes even higher), but with huge and annoying screen tearing. What can I do?

I've already tried to activate V-Sync from the AMD control panel and disabling the one ingame, but it didn't work.
 
Solution
I'd have advised adaptive vsync as well if not for me playing on an AMD GPU and not having that setting either.

As far as I know AMD endorsed games don't use it because they try to get their customers to use Freesync instead. Seems odd though since a lot of people use TVs (myself included) which have neither Freesync or Gsync.

AMD are not good at marketing things though, so it's status quo for them.
Wolfenstein 2 is a coding mess. They've not only hardcoded Vsync to 30 FPS, the new AMD drivers for it didn't fix all the crashing problems.

Fortunately for me I only get minimal screen tear in cutscenes, and in game there's pretty much none. I did have bad artifacting at one point toward the end of the game though. I also saw a guy doing a stream on YouTube suffer bad artifacting in a spot where I got none.

Normally I'd say wait until proper patching or driver updates are implemented, but I'm not sure it will ever get fixed. Maybe modders can step up and at least offer a 60 FPS Vsync somehow.
 

gegennaro102

Prominent
Nov 4, 2017
4
0
510


Maybe I found a solution: with Rivatuner I set the cap at 55 fps (monitor is 60hz), in that way also with v-sync disabled the screen tearing seems to be less

 

Yeah if you mean RTSS, that's about the best FPS capping tool. It uses less RAM than others. I haven't bothered using it because for me it would only help on cutscenes. I may try it anyway just to keep the FPS window tight, I noticed during load scenes I get spikes up to 400 FPS or more, and that can cause the GPU to heat up. I might have less chance of artifacts t hat way.

Also, don't know if you're aware but AMD just released a 17.11.1 driver, so I'm going to try that. Many said the 17.10.3 driver made for this game didn't do a thing for them.
 

Not likely, and I wish people would stop getting on the Vulkan hate band wagon. It's more likely that MachineGames have never developed with Vulkan before. Id did fine with it on Doom 2016.

You'd think since ZeniMax Media owns both Bethesda and Id, they'd make sure Id was along on the ride to consult MachineGames on development, but it's as if they just didn't give a damn how shoddily the PC version was made.

This reminds me of how Rocksteady left a small team to make the PC version of Arkham Knight, and it was so bad Warner Bros had to pull it from Steam and do nearly a years worth of damage control.

You'd think publishers and their owners would learn by now since most sales happen within 3 months of launch, it's better to get it working right the first time than risk bad PR and tons of lost and discounted sales.

Bottom line, don't assume MachineGames is at fault here.

 
It's not hate bandwagon,the game runs very well and personally I have not encountered any essential problems,it's just the screen tearing/vsync issue and the problem could very well be on the driver or even windows side and nothing to do with the game,fact is that nobody has tons of experience with vulkan so stuff like this is just bound to happen.

Or maybe they "improved" the engine since doom came out and it's related to that,or it could be anything really.
 

Maybe, but you have to admit what you just said there is a total 180 from saying "I think it's because of how new vulkan still is".

Like I said, Id did fine with Vulkan, as is evidenced by how well Doom 2016 runs on even mediocre spec. It's common sense since Id is owned by the same company that owns Bethesda that they should have been used for consultation on how to implement Vulkan.

 

gegennaro102

Prominent
Nov 4, 2017
4
0
510


Yes I'm with 17.11.1 driver, the situation is still the same
 

king3pj

Distinguished
I turned off Vsync because I use a Gsync monitor but the default Wolfenstien 2 vsync setting for me was adaptive vsync. I would give that a try.

The way adaptive vsync works by turning off vsync when you are below your monitor’s refresh rate but turning it on when you are at or above the monitor’s refresh rate. This should stop your game from dropping to 30 FPS when the game dips below 60.

If you have a 60Hz monitor and you are getting 55 FPS adaptive vsync would turn vsync off and give you the full 55 FPS instead of dropping down to 30. You might get some tearing but gameplay should be smoother. In parts of the game where your hardware is capable of 60+ FPS vsync would kick in, cap you at 60 FPS, and eliminate tearing.

This is all assuming the adaptive vsync setting works properly in Wolfenstein 2. I haven’t tested it because I don’t need vsync with my gsync monitor.
 

gegennaro102

Prominent
Nov 4, 2017
4
0
510


Yeah, I believed that adaptive vsync would've solved my problem, but I just don't have the option, maybe it's because my monitor isn't neither gsync or freesync butbis a normal one
 

king3pj

Distinguished
Strange. In the Wolfenstein 2 game settings for me the vsync choices are on, off, or adaptive. I am using an nvidia card and a gsync monitor but it seems weird that the in game vsync settings would change for people with AMD cards and standard monitors.
 
I'd have advised adaptive vsync as well if not for me playing on an AMD GPU and not having that setting either.

As far as I know AMD endorsed games don't use it because they try to get their customers to use Freesync instead. Seems odd though since a lot of people use TVs (myself included) which have neither Freesync or Gsync.

AMD are not good at marketing things though, so it's status quo for them.
 
Solution