RDR2 Moonshiners PC Patch - 1232.13 (1.15) | 13/12/2019

[extremeL]

13 hours ago, Spider-Vice said:

Also, it's holidays, don't expect anyone to fix anything until the first week of January.

I don't think a company will fix the products they broke years ago.

[Dryspace]

4 hours ago, Spider-Vice said:

Wow that has nothing to do  with what I described in my post (i.e. overcomplicates)

Well...I don't think that's fair at all. I responded to exactly what you described in your post. If you meant something else, fine, but I can't read your mind!

 

And I don't think I overcomplicated anything...I admitted that I enjoy talking about vsync, because unfortunately I disagree about what everyone knows: In my experience vsync is possibly the single most misunderstood, yet common aspect of gaming. I'm sure there are technical aspects that I don't yet know about.

 

Just as one example, you may be surprised at how many people think that screen tearing is caused by the framerate exceeding the display's refresh rate--as if it's exceeding the design specs of the display and physically breaking down!

[Dryspace]

3 hours ago, Doodling Hitman said:

...my pc froze. Not just the game.

Just a thought--Are you sure about your temps? No chance you could be getting incorrect readings?

 

The reason I ask is that when you put a few things together:

 

1. You complain that your fans are really, really loud (i.e. you're noticing them more because they're going full-blast).

2. You are experiencing crashing.

3. You have experienced at least two system freezes/hard locks while in-game.

 

...it certainly sounds like a possible overheating issue. If your CPU really is topping out at 75C then your temps are okay, but I would get a second and third reading of your core temps from different sources.

[Paper Mario]

4 hours ago, Dryspace said:

Just a thought--Are you sure about your temps? No chance you could be getting incorrect readings?

 

The reason I ask is that when you put a few things together:

 

1. You complain that your fans are really, really loud (i.e. you're noticing them more because they're going full-blast).

2. You are experiencing crashing.

3. You have experienced at least two system freezes/hard locks while in-game.

 

...it certainly sounds like a possible overheating issue. If your CPU really is topping out at 75C then your temps are okay, but I would get a second and third reading of your core temps from different sources.

I'm quite sure about my temps now. First I used Speccy which I know doesn't always read the actual temps, but I also used msi afterburner. It stayed below 70c this time, and when I played in safe mode with all settings low (except for textures at ultra) the cpu temp even dipped below 60c sometimes. And my gpu temp was fine too, below 70c. The fan noise was a bit less too, but I am very nitpicky when it comes to noise. I mean, it doesn't sound like jet, but... I just dislike almost any external noise I can hear besides my game, lol.

 

Other games I play never freeze. Lately been playing Halo Reach on PC a lot too which fluctuates my cpu temp between 60-65c. No issues there whatsoever and no noise.

 

Now I am not the most smartest guy and especially not when it comes to complex PC stuff. I may have built my own pc, but I did it with tutorials a lot. It is most likely certain settings screwing with my game, but I could troubleshoot endlessly and never find the problem. I've read there are so many ways the game could potentially crash. 

 

I myself have a i7 7700K cpu and a geforce gtx 1080 gpu with 16gb of RAM. I slightly tested playing in Vulkan and the other one, DX12 or something? Vulkan gives me a better performance, but both have gotten me crashed.   

[Gforce]

Sit Rep .............

After struggling to get through the "Goats and Sheep" mission with crashing at various sections a whole 8 times, I decided to get serious with trying to find the reason why my game has progressively got worse with every attempt at playing, so ...............

I deleted the contents of the "C:\Users\*YourName*\Documents\Rockstar Games\Red Dead Redemption 2\Settings" folder

I deleted the contents of "C:\ProgramData\NVIDIA Corporation\NV_Cache" folder

Uninstalled the game via the R* launcher

ran CCleaner, rebooted

Waited an hour for the game to download and reinstall

Went back to playing RDR2 at butter smooth 60fps everywhere, able to go into the gfx settings menu and back to game without the game turning into a stutterfest before it's eventual crash, just about every issue I was having that I posted in my previous posts in this thread have now gone.

Some of the remaining issues I have are occasional flickering as the Chapter Transition cutscene went to Schitt Creek or W/E it's called, and I'm getting some frame hitching which I have been hypothesising over because they're repeatable, the hitches are mostly happening when the game appears to be setting a "Mid Mission Checkpoint,respawn, trigger point" either at the start of a mission or midway through, or when interacting with strangers with a greeting, or random stranger events like campsites with or without gangs or side missions, previously a lot of these hitching points would actually cause the game to crash.

the oddest thing has been the ability to just wander around the map exploring for secrets etc and being able to play for a couple of hours as long as there were no random events or encounters.

given that game can run so smoothly at times and at others on different days it would run like crap for absolutely no reason, also that R* did a pretty good job with how smoothly GTA V ran out of the box it seems odd that with RDR2 there's so many problems, until you take a look at the fact that GTA V was being played by the Jack Sparrows within hours of the game going on sale, this time we're almost 8 weeks into release and the game is still not being played by the Jack Sparrows of this world and the game is not using Denuvo which in recent times has gone south on day 1, but the game is running like absolute dogsh!t for some if not most players, this leads me to believe that it's possible that these "Mid Mission Checkpoint,respawn, trigger point" are potentially part of the DRM or maybe the triggers are also syncing to the cloud as well, I also noticed that I was getting a lot more crashes at what appear to be peak server times, I haven't been able to test any of the hypothesis for whether or not the online/server side of the game code is what's giving us problems as so far I haven't figured out how to tell the game to run in offline mode.

one last thing, I'm running the game from a Samsung 970 EVO Plus M.2/NVMe drive running at roughly 3500MB's, I don't think it's a file loading/streaming issue causing the hitches.

Seasons Greetings to one and all  ......................... except ........... no Seasonal Snow dlc update for your loyal PC Single player gamers, bah humbug

[Officer Friendly]

Its sad that they had an entire year to optimize and test only for it be a sh*t show at launch. Now you could partially blame Nvidia, but the crashing and CPU is issues are squarely on Rockstar.

 

The game is going backwards performance wise, and now with this new v-sync issue its unplayable.

 

I'd be curious to see a DRM free version tested, even with offline mode the DRM may still have an impact.

Edited December 24, 2019 by Officer Friendly

[Armerius]

for me the problems are conections issues..since the update those are far FAR worse then before.

[Candy_Licker]

Very nice....   Looks like there's a memory leak or sth. After a few minutes ingame I have tearing stutters.

 

And when I start the game, I have to hit Alt/ The WIndows button because the game is running only with sound in the background

[Armerius]

How do we clear local files? Anybody knows? Seems to fix some of the issues with the update

[gregorius11]

While the previous patches did not really affect my gameplay in a negative way, I have to say that his one brought some random stutters/fps drops I have never seen before.

[Nagru87]

wtf are they planning to release a new patch or what ;/ this one is a garbage ruined a gameplay experience with a lot of bugs stutterting etc..

i doubt they even test it properly.

Edited December 27, 2019 by Nagru87

[Officer Friendly]

17 minutes ago, Nagru87 said:

wtf are they planning to release a new patch or what ;/ this one is a garbage ruined a gameplay experience with a lot of bugs stutterting etc..

i doubt they even test it properly.

Don't think the developers are in the office next week, so probably the week of January 6th. Who knows. I stopped playing for a couple weeks now because of this.

[Slappy212]

On 12/24/2019 at 12:29 PM, Officer Friendly said:

Its sad that they had an entire year to optimize and test only for it be a sh*t show at launch. Now you could partially blame Nvidia, but the crashing and CPU is issues are squarely on Rockstar.

 

The game is going backwards performance wise, and now with this new v-sync issue its unplayable.

 

I'd be curious to see a DRM free version tested, even with offline mode the DRM may still have an impact.

Given the resources RS has...it's insane how bad this port is. There are indie dev who do a better job of it. 

[Candy_Licker]

On 12/28/2019 at 12:12 AM, Officer Friendly said:

Don't think the developers are in the office next week, so probably the week of January 6th. Who knows. I stopped playing for a couple weeks now because of this.

 

yeah me too

[Hanzema]

I have a question for you guys. Anybody of you having crashes when fire effect from molotov cocktails and/or fire ammo from shotguns have been used? I sometimes get the famous GFX error from it. 

[UpTheDowngrade]

1 hour ago, Hanzema said:

I have a question for you guys. Anybody of you having crashes when fire effect from molotov cocktails and/or fire ammo from shotguns have been used? I sometimes get the famous GFX error from it. 

Haven't gotten a crash from fires being on screen since like the first couple weeks of release, personally.

[gregorius11]

Wow, the game performs worst in the wilderness around Strawberry. It's a big stuttering mess out there.

[Hanzema]

22 minutes ago, UpTheDowngrade said:

Haven't gotten a crash from fires being on screen since like the first couple weeks of release, personally.

Weird. I never had any kind of crash since the moonshiners update dropped. 

[Dryspace]

20 hours ago, gregorius11 said:

Wow, the game performs worst in the wilderness around Strawberry. It's a big stuttering mess out there.

Is it basically a framerate issue, or is it hitching/stuttering in spite of a decent framerate?

[gregorius11]

44 minutes ago, Dryspace said:

Is it basically a framerate issue, or is it hitching/stuttering in spite of a decent framerate?

I'm not using any FPS measuring program, but it feels like 20 fps sometimes.

 

Also, I'm not sure if I'm getting paranoid or did they bring LOD problems along with this update. Despite having textures on Ultra and geometry level of detail maxed out, some textures in the distance look flat and boring. Take a look at the building above Arthur's head for example.

 

[zedshifter67]

After Patch 1.15 release my game became highly unstable, while before it was running perfectly.

Crashes occurred during loading and while playing the game.

Sometimes I got the ERR_GFX_STATE error message (which I had never seen before), an old friend (from the first days after game release), the EXITED UNEXPECTEDLY message reappeared and sometimes the game just crashed.

 

After trying lowering the graphics settings, which didn't work, I managed to get the game running again (no more crashes since almost 3 weeks) by doing the following:

 

I added the -ignorepipelinecache launch argument to the launcher.

On the compatibility tab of the Properties pop-up window of RDR2.exe I disabled Fullscreen Optimization and forced Administrator Privileges.

Graphics settings as before.

 

And yes, since patch 1.15 I'm experiencing the Vsync-stutter issue (reported by several players) too. Switched Vsync off - stutter disappeared.

 

In addition, since patch 1.15 Seamus' table (Fence location at Emerald Ranch) is missing. No invisible collision model either - can walk straight to Seamus. A lamp formerly standing on the table is now hovering in air.

 

System AW 17 R4 (laptop, Mar 2017), i7 7700HQ, GTX 1060 6GB

[mhenkel]

On 12/31/2019 at 10:07 PM, Hanzema said:

I have a question for you guys. Anybody of you having crashes when fire effect from molotov cocktails and/or fire ammo from shotguns have been used? I sometimes get the famous GFX error from it. 

I get GFX error if I run my graphic card overclocked. A member on this forum talked about that he underclocked his card and it solved some of the problems. So I tried it, underclocked my card very little, and the crashes reduced a lot. And as soon as I overclock it, no matter how much it start to crash very often. This happens in RD2 only, for me.

 

But the game crash anyway, but way less frequent when the card is underclocked. 

Edited January 4, 2020 by mhenkel

[Hanzema]

8 hours ago, mhenkel said:

I get GFX error if I run my graphic card overclocked. A member on this forum talked about that he underclocked his card and it solved some of the problems. So I tried it, underclocked my card very little, and the crashes reduced a lot. And as soon as I overclock it, no matter how much it start to crash very often. This happens in RD2 only, for me.

 

But the game crash anyway, but way less frequent when the card is underclocked. 

I didn't overclock nor underclock it. It's a base Asus Strix 1080ti. Didn't have those problem I mentioned or any kind of problem I'm having now before the moonshiners update. So I'm confident to say that the fault of any issues anybody is experiencing is on Rockstars part. 

[Gforce]

One of the main bugs I'm seeing a lot of, other that the obvious trigger hitches and crashes, is this immersion killing water bug.

[_CP_]

Is this occurs at the specific place or anywhere?

[Gforce]

38 minutes ago, _CP_ said:

Is this occurs at the specific place or anywhere?

It's pretty random in a multitude of locations, mostly ponds, lakes and shallow waters

there's also the storyline dialogue bugs in camp locations,

Spoiler

with dialogue from Mary Beth mentioning the condition of the next location, meanwhile in Shady belle they're discussing Jack being missing while he's long been back and then the usual Sheriffs badge bug

 

[gregorius11]

Never seen this water bug. Jesus, this game is like a Kinder Suprise Egg. You just don't know what to expect after you buy it.

[UpTheDowngrade]

Anyone else getting the bug where you can't do bounty missions? It shows there's 1 available in Rhodes, and 1 in Saint Denis, and once I get into said town/city, the icon disappears. I'm in chapter 4 and i've paid off the price on my head everywhere, and even tried doing multiple story missions first, and they never are actually available to me. Once I ride out of Rhodes or Saint Denis, they both reappear.

 

Could be something got messed up with my save file? I was using Scripthook when the bug started happening. I removed it, but the bug persists.

Edited January 5, 2020 by UpTheDowngrade

[Dryspace]

5 hours ago, gregorius11 said:

Never seen this water bug. Jesus, this game is like a Kinder Suprise Egg. You just don't know what to expect after you buy it.

Lol, that's a good analogy. But to be honest, after over a year of "development", and another couple months post-release of....whatever it is Rockstar is doing, I know exactly what to expect if I buy it: obvious, intrusive, and serious bugs (as opposed to minor/rare bugs that almost all games have).

 

If I buy a lottery ticket, am I guaranteed to lose? No, but I expect to. Which is why I have no plans to buy RDR2 any time soon.

[Hanzema]

This game is a freaking mess.