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

[LEXX141]

smoke was not returned from the train!

[mytu420]

sadly vsync problem is still there, i was hoping it will be fixed

Edited January 14, 2020 by mytu420

[Hanzema]

3 minutes ago, LEXX141 said:

smoke was not returned from the train!

Wtf? Really? 

Just now, mytu420 said:

sadly vsync problem is still there, i was hopping it will be fixed

That's unbeleavable

[trulex47]

nothing is fixed here, patch of 93mb cant do any thing. This is only online update about discounts and thats all.

[Spider-Vice]

This patch was simply a hotfix patch. Anything more significant will probably o ky be coming later. As I mentioned before they probably have barely had any time to work on PC/bug stuff after and before Xmas. 

[Gforce]

700mb later and not much change for me other than R* reset all my gfx settings yet again ............................ Motion Blur On ?!!! WHY ? if I want Vaseline smearing effects I'll fire up GTA IV on my XB360, not like that game's even playable on PC any more.

seems this was a small hotfix indeed, looks like they tried fixing the Vsync issues, my min fps have come right back up to close to where it should be and my max fps has come down, ultimately all 3 of these numbers should match with Vsync On, they're getting closer.



1440p/60fps/Vulkan 2x 980ti Multi GPU

Still crashes like a motherfecker, anytime I get near any NPC I get a sudden frame dip/hitch and I wait to see if it crashes or turns into a stutterfest, 7 times out of 10 I get a crash when I get a stutter/hitch.

[T-ru]

"General stability fixes and improvements"  - Bulls##t, a lie, instead of this now there is more freezes moments!!!

This game brings me back at 2009, GTA IV mess. R* NEVER care about their PC versions! 

[Hanzema]

59 minutes ago, T-ru said:

"General stability fixes and improvements"  - Bulls##t, a lie, instead of this now there is more freezes moments!!!

This game brings me back at 2009, GTA IV mess. R* NEVER care about their PC versions! 

I can confirm that this patch is a lie and hot garbage. Still freezes after I load in red dead online. 

[Dryspace]

On 1/10/2020 at 3:25 AM, MarshallRawR said:

Holidays is your answer to why there were no patches. Work started again and an update is on its way.

 

On 1/14/2020 at 1:35 PM, Spider-Vice said:

As I mentioned before they probably have barely had any time to work on PC/bug stuff after and before Xmas. 

I don't think that "Holidays" is a sufficient answer.

It's been 33 days--23 weekdays--since the last patch was released. Taking a day or three off? Sure. Considering Christmas and New Year's, taking a total of a whole week off? Okay, fine.

But that still leaves 25 days--16 weekdays (over 3 five-day workweeks)--since the last patch. And where I come from, if I have taken full payment from a customer, yet failed to deliver a working product, I'm going to be putting in Saturdays until my failure is rectified. As of right now, the fact that it has been 441 446 days since the game was originally released means that it doesn't make sense to hover with anticipation for the next patch with the assumption that it's going to amount to anything. It's not impossible--just improbable.

 

There are a plethora of problems that Rockstar clearly does not consider priority. That is undeniable. What is impossible is that an organization with Rockstar's resources could fail to produce a functional port with no serious, obvious problems by now if they were actually trying. To be more specific: If they were actually devoting the necessary amount of resources, the game would just work right now. Rockstar isn't attempting to colonize the moon here.

 

I am positive that if the source code and documentation were released today, the only question would be which fans are the first to deliver a working game in their spare time, and whether it would end up taking two weeks, or three. Instead Rockstar is attempting to minimize expense and maximize profit margins because they think--up 'til now apparently correctly--that the PC market will let them get away with it.

 

Having advertised and sold a broken product to a whole bunch of people means there's important work to be done. And when there's important work to be done, you show up to work and do it.

Edited January 15, 2020 by Dryspace
Mathematical error

[Orlansky]

Will the new patch get its own thread? Does its stature merit one? Was that out of line?

[kubon352]

So, my game started to give me that infamous err_gfx_state error.

Everything was fine since first patches that fixed stutterings.

Changing to DX12 solves the issue but on Vulkan I have better performance.

[Midokof2002]

52 minutes ago, Kubigz said:

So, my game started to give me that infamous err_gfx_state error.

Everything was fine since first patches that fixed stutterings.

Changing to DX12 solves the issue but on Vulkan I have better performance.

I had the same problem with the new patch but i fixed it by deleting the 3 sga_ files located at Documents\Rockstar Games\Red Dead Redemption 2\Settings , the game is working fine right now on Vulkan.

Edited January 16, 2020 by Midokof2002

[kubon352]

This did not help me.

[UpTheDowngrade]

36 minutes ago, Kubigz said:

This did not help me.

Did you try deleting the cache, then launching the game, getting the error, then relaunching without deleting cache? That always worked for me. I havent gotten the err_gfx_state since the newest patch. I was getting it every single time, prior.

Edited January 16, 2020 by UpTheDowngrade

[kubon352]

It came back to normal after hour of playing on DX12 and then deleting cache files. Strange.

[Koltos]

Did someone download new nvidia drivers with support of Vulkan 1.2?

 

How it goes with rdr 2?

[Gforce]

I gave up with the 441.87 drivers and went back to 441.66, the misery is very real with 441.87, and Nvidia knows about it.



Ngreedia driver release notes direct link to the problem section

https://uk.download.nvidia.com/Windows/441.87/441.87-win10-win8-win7-release-notes.pdf#G7.831996

[LEXX141]

10 hours ago, Koltos said:

Кто-то скачивал новые драйвера nvidia с поддержкой Vulkan 1.2?

 

Как это происходит с RDR 2?

I got worse on the 441.99 fps driver.

[sorder]

13 hours ago, Koltos said:

Did someone download new nvidia drivers with support of Vulkan 1.2?

 

How it goes with rdr 2?

Didn't notice any fps changes 

[trulex47]

2 hours ago, sorder said:

Didn't notice any fps changes 

There is one video on youtube with 441.99 test on rdr2, guy told there is 1-5fps boost.

[PolishRye]

25 minutes ago, trulex47 said:

There is one video on youtube with 441.99 test on rdr2, guy told there is 1-5fps boost.

it just depends on hardware, someone might get this 5fps boost, someone else can get no boost at all

[LEXX141]

55 minutes ago, trulex47 said:

На youtube есть одно видео с тестом 441.99 на rdr2, парень сказал, что это повышение на 1-5fps.

In the benchmark of the game on gtx 1080ti, I got one frame less than on the old drivers.

[trulex47]

1 hour ago, LEXX141 said:

In the benchmark of the game on gtx 1080ti, I got one frame less than on the old drivers.

lol, I paused download of new driver

[MarshallRawR]

A bit off-topic but to whoever wants to know, I've figured out the reason of the heavy stuttering I was experiencing that I reported here a little while ago.

Spoiler

 

Well the answer was pretty simple, RAM.  I knew I was maxing out RAM but didn't expect it alone to be the cause.

Turns out my theory after doing some testing is simply the game using the pagefile and thus hitting a wall in terms of performance.

Nothing new really, but I added an old 2x2 kit I had of not even technically compatible RAM (Old Kingston Fury Blu with the FuryX) just for testing and well, it works.

 

Spoiler

 

Definitely not a long term solution, so if anyone is reading this and considering mixing RAM kits, DON'T do it please.

Edited January 17, 2020 by MarshallRawR

[Dryspace]

10 hours ago, MarshallRawR said:

...I knew I was maxing out RAM...

...the game using the pagefile and thus hitting a wall in terms of performance.

Nothing new really, but I added an old 2x2 kit I had of not even technically compatible RAM...and well, it works.

How much RAM did you have originally? 8GB?

[seldo]

Just arrived in new Austin... I have many pop up issues from the Great plains to the overlook to Armadillo!

 

I guess that's the first time the drawing distance is so long with many details on the way (no foreground to hide the rest).

 

That's said, even on a low/medium setting, NA looks fantastic! Just issues with textures that are not all of the same quality, but I guess that's the game (I am using ultra textures).

Even when building the house, tiles next to each other had different texture level...

 

Edited January 18, 2020 by seldo

[Dryspace]

9 minutes ago, seldo said:

Even when building the house, tiles next to each other had different texture level...textures that are not all of the same quality, but I guess that's the game (I am using ultra textures).

If you can distinguish different mip-map levels simultaneously, that would have to be a bug, as I can't imagine a developer would intend that behavior.

 

You say that except for Textures, you are using Low and Medium settings--are there any settings that can be increased to address the pop-in and LOD problems?

[PolishRye]

34 minutes ago, Dryspace said:

If you can distinguish different mip-map levels simultaneously, that would have to be a bug, as I can't imagine a developer would intend that behavior.

 

You say that except for Textures, you are using Low and Medium settings--are there any settings that can be increased to address the pop-in and LOD problems?

geometry level of detail if i remember correctly

[MarshallRawR]

3 hours ago, Dryspace said:

How much RAM did you have originally? 8GB?

 

Yes a kit of 2x4 so 8GB total. The game barely uses about 1GB more than before but it makes all the difference.

[Gforce]

I was unaware of the 441.99 beta drivers when i made my last posts here, and since updating to these beta drivers I have had pretty much zero crashes,

I have gone from the game running butter smooth 60fps everywhere but random crashing litterally every 10-15mins whenever coming across random NPC interactions with the 441.87 drivers, to absolutely none during a 10hr play session that saw me leaving the game on pause for an hour at a time several times, even during a random stranger mission, the game has gone from being virtually unplayable to rock solid in the matter of one driver installation, I'm blown away by the improvements.

also looks like I have to retract almost everything negative I said about R*, but I do still have some flickering during cutscene transitions and occasionally going from a darker interior/building into bright daylight.

given the sheer frustration I have had from this game running so badly I have probably gained an extra 5fps simply from going through all of my OS settings fine tuning and optimising everything I possibly could to eliminate any possible issues, and my OS is already on a savage resource diet at the best of times.

Edit: Just ran another benchmark and the framerate is now pretty consistent with Vsync on with Vulkan


Congrats to , the game finally runs without crashing constantly, only taken 10 weeks time to start modding it 

Edited January 19, 2020 by Gforce