Suddenly getting a "ERR_GFX_STATE" crash when loading my save with Vulkan. If I switch to DX12 it works... but then it'll crash randomly later because it's DX12 🙃
-
Ever wanted an RSS feed of all your favorite gaming news sites? Go check out our new Gaming Headlines feed! Read more about it here.
Red Dead Redemption II PC performance thread
- Thread starter GrrImAFridge
- Start date
yep, this started with me yesterday also. You can go into the settings folder in documents, delete everything but the xml file, and verify integrity and it worked the next time I launched it.........but the time after that it crashed with the same error msg.
So I swapped to DX12. And yep, crashes every couple of hours.
Game pls is jus wanna play you.
You don't need to though. In fact, your experience will almost certainly be better with it off, input lag-wise.
at the very least, I doubt theyll put it up unti lthe port is considered "fixed".
but also, I guess it could be that they're just trying to get as many ppl to buy it on their store as possible so they'hide' the steam version as long as possible.
I would expect the same. Steam refunds are far easier than trying to get one from Rockstar so they better have the game in good condition by next month. There is definitely still a ways to go because it still has completely stupid problems like map rendering incorrectly in fullscreen on Vulkan or the iOS companion app not working with PC. The fishing seems broken on controllers too for some reason, I had to switch to mouse and keyboard to even reel in a fish. It's like they started porting this game with a months old build or something.
I feel like the game looks a bit better in DX12 too but have to run on Vulkan because it runs better without crashes. I can't put my finger on what is the difference, will probably take some screenshots to see if I can figure it out.
I'm willing to get they do, due to the massively increased tearing.
No one cares about tearing in comparision to input lag. I love my Gsync monitor but when does anyone complain about that on PC forums or websites outside of Era? You guys are in a bubble here.
Data is difficult to source for this, but every way to find some points it in favour of my argument.
Google Trends results for "input lag" vs other variations I could think of:
Top Google result when searching "vsync on or off". Search this (or a variation) for yourself and click on a link. Nearly all of them say to turn it off. Almost every forum post, reddit post, anything, they suggest to turn it off because of lag.
The vast majority of popular video games on PC are multiplayer, which requires better reflexes and lower input lag. The average person couldn't care less about tearing, but they do know a bit about "lag", and they want to avoid it. In comparison to screen tearing, the majority of PC gamers prefer lower input lag from my results.
You can google all you want, but we don't actually have any hard data to back up your claim. Most PC gamers probably just use the settings presets available to them, and vsync on or off based on whatever the default happens to be. That's just how people tend to operate, lol.No one cares about tearing in comparision to input lag. I love my Gsync monitor but when does anyone complain about that on PC forums or websites outside of Era? You guys are in a bubble here.
Data is difficult to source for this, but every way to find some points it in favour of my argument.
Google Trends results for "input lag" vs other variations I could think of:
Top Google result when searching "vsync on or off". Search this (or a variation) for yourself and click on a link. Nearly all of them say to turn it off. Almost every forum post, reddit post, anything, they suggest to turn it off because of lag.
The vast majority of popular video games on PC are multiplayer, which requires better reflexes and lower input lag. The average person couldn't care less about tearing, but they do know a bit about "lag", and they want to avoid it. In comparison to screen tearing, the majority of PC gamers prefer lower input lag from my results.
No one cares about tearing in comparision to input lag. I love my Gsync monitor but when does anyone complain about that on PC forums or websites outside of Era? You guys are in a bubble here.
Data is difficult to source for this, but every way to find some points it in favour of my argument.
Google Trends results for "input lag" vs other variations I could think of:
Top Google result when searching "vsync on or off". Search this (or a variation) for yourself and click on a link. Nearly all of them say to turn it off. Almost every forum post, reddit post, anything, they suggest to turn it off because of lag.
The vast majority of popular video games on PC are multiplayer, which requires better reflexes and lower input lag. The average person couldn't care less about tearing, but they do know a bit about "lag", and they want to avoid it. In comparison to screen tearing, the majority of PC gamers prefer lower input lag from my results.
I can't remember the last time I had vsync on. Has to be double digit years. I enabled it after the last patch in this game lol. The tearing was so bad it looked like waves going across my screen anytime I moved. I haven't noticed any noticeable input lag but I will turn it off if they fix the screen tearing.
That's not what I said. I said in comparison to screen tearing, input lag is more important with the data we have available. Of course theres also a big segment who just don't care and don't notice it.
Maybe people have different ways of seeing things? Before I ascended to gsync glory and I had to choose, I always preferred having slight input lag over screen tearing. Screen tearing is extremely jarring for me while the input lag I barely noticed. Glad I don't need to choose anymore tho.
Not sure how this thread got off on this weird tangent, but as someone who primarily plays SP games on PC, screen tearing is way more distracting than how ever many ms of input lag vsync produces. I try to mitigate input lag where I can, but screen tearing will never be a concession I'm willing to make and I imagine that goes for a lot of people.
Yep. A lot of bullshit being spread in this thread and for no reason really.
The thing about screen tearing is there is a way to fix it. It is called Vsync :D (or any of its derivatives)
"More important" - for what? There are thousands of games outside of the competitive shooter genre where your response time is of course absolutely critical, even if you did leave vsync off doing those however, it doesn't mean you wouldn't accept slightly increased input latency (which can vary drastically game to game, regardless of vsync) for other games as opposed to tearing. What I'm going to accept in Fortnite is wholly different than the experience I expect in any number of single player games.
It's your preference. It's not 'data' - we know the 'data' you're speaking of - vsync off produces less input lag. Yes, no one is debating that. It's the price you have to pay to get it, which will vary depending upon the game genre, refresh rate, input method, personal taste, etc.
Except disabling vsync means that, if your frame rate exceeds your max refresh rate, tearing will begin.
When vsync is off, exceeding your monitor's refresh rate results in tearing. When vsync is on, exceeding your monitor's refresh rate isn't possible, but hitting the cap enables vsync. Capping your FPS a few frames below your maximum refresh rate and enabling vsync results in the ideal balance of input latency and no tearing.
Which is also what I'm using (well, mine has an OC to 165hz, but that's besides the point). You should enable vsync with a gsync monitor, since it'll prevent your framerate from exceeding 144FPS and reintroducing tearing. Use RTSS or Nvidia Profile Inspector to cap your framerate a few frames below your refresh rate (2 or 3 is enough), and vsync won't engage when you hit 144FPS.
Lol true. I can handle some screen tearing. It just got worse with the last patch for me. It was the first thing I noticed.
I'm normally not using vsync with gsync. And why should I, there is no tearing with Gsync. If a game is likely to exceed my displays refresh rate I just cap it 2-3 fps below that with RTSS.
Before the last patch I had to use vsync + gysnc with RDR2 in vulkan though. Gsync wouldn't work otherwise for whatever reason. This has been fixed now and all I can say: Running the game without vsync but just gsync feels way better. It was a noticeable change.
Before the last patch I had to use vsync + gysnc with RDR2 in vulkan though. Gsync wouldn't work otherwise for whatever reason. This has been fixed now and all I can say: Running the game without vsync but just gsync feels way better. It was a noticeable change.
I've been using Gsync monitors for years and I turn off vsync and cap my framerate with RTSS instead.
They recommend using vsync because the framerate shouldn't go over your monitor's refresh rate, but you could use other ways to cap it instead of using vsync.
Well that's placebo effect for you. GSync with VSync enabled does not introduce any extra input lag. For proof, please check battlenonsense GSync input lag tests
Normally, sure.
In this case it is a noticeable difference.
Gsync didn't even work in this one without V-Sync. Which is also something that should not have happened.
You won't find anything more comprehensive than this.
Can confirm, that's the guide I've used whenever I felt like I missed something or needed to tweak stuff on a new PC.
Is it working and just buggy, or have they not announced anything? With Vulkan and DX12 the developer has to explicitly manage the resources on each card, it's not a trivial amount of work. If they haven't said that it's coming then I wouldn't get your hopes up. SLI is extremely niche at this point and the newer API's just don't support it without the developer doing most of the work.
That's what I thought. The topic is interesting and complex enough to deserve its own thread.
Anyone else with an i7-7700K who tried the -cpuLoadRebalancing launch argument?
Rockstar recommends enabling it for 4c/8t CPUs, but, in my case, all it did was make all cores run with higher loads (up to 10-15% more) at higher temperatures (5-10C more), with an actual decrease in performance (5 FPS less, on average).
Rockstar recommends enabling it for 4c/8t CPUs, but, in my case, all it did was make all cores run with higher loads (up to 10-15% more) at higher temperatures (5-10C more), with an actual decrease in performance (5 FPS less, on average).
I thought it was mainly for i5s because of the issues those of us with them were having.
Unless you are getting hard stutters, I wouldn't use it. 8 thread cpu's should be just fine. Benchmarks showed them to do well.
Yeah I don't have anymore freezing issues with my 6600k, but the frame rate is still awful in towns. I've basically given up the 60fps dream for this game until I can be bothered upgrading.
This is probably the first time I haven't really been mad about capping to 30fps on PC, the game just looks mental at ultra settings. Can't get over how expansive the world feels with the grass density and near infinite draw distances.
This is probably the first time I haven't really been mad about capping to 30fps on PC, the game just looks mental at ultra settings. Can't get over how expansive the world feels with the grass density and near infinite draw distances.
Mouse cursor being in the middle of the screen is finally fixed for me after the patch.
This has been pretty all-encompassing over the years.
The Unlocked Volumetric Raymarch Resolution setting would constantly lead to crashes upon loading into story mode for me, I've attempted to load the game twice now in Saint Denis and it hasn't crashed, it seems that crashes related to this setting may have been resolved for me. Has anyone also experienced this? I run the game using the Vulkan API.
CPU: Ryzen 5 3600 4GHz
GPU: GTX 1080 Ti
Ram: Corsair Vengeance LPX 32 GB (4x8GB) 3000MHz CL15
Thanks for the heads up I will make sure to grab my current settings file before installing the patch so I can at least see what my current settings are to reset.
ugh what a pain in the ass
Note to those tweaking their settings again after this update: The "max settings" preset changes some things not listed in the graphics menu, so it's a good idea to set your game to the max preset before tweaking.
Regarding the vsync discussion - I always have it on, because tearing makes my eyes bleed. On a 60Hz display without g-sync/freesync/VRR vsync is a must for me.
www.testufo.com/stutter#test=stutter&demo=tearing
www.testufo.com/stutter#test=stutter&demo=tearing
I think it is also useful to highlight this passage... (from the -recently- added faq):