Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For Online are you using the startup.meta file trick to get your own solo session? If not then it's griefers with cheat mod menus crashing your game as soon as you join a session.
I'm still experiencing the issue. I did a clean install and everything too...also with no joy.
Yes, single player works fine and loads without fail every time. I am unfamiliar with the "startup.meta file trick." So you're saying that it could be griefers consciously crashing my game before loading into 'free roam' completes? Dammit, I hope not. What a bummer.
I do not say it is your problem, but this is definitely something you should try.
After changing many things, and reading many (too many...) "solutions", I solved my problem by simply changing 1 thing in the settings: Change from VULKAN to DIRECTX ... (or the opposite)
> RDR2, SETTINGS
> Graphics
> scroll down to Advanced Graphics
> Advanced Settings: Unlocked
> Graphics API : DirectX 12 And if it is already DitrectX 12, change to Vulkan...
Almost 100h later, zero issue, all settings at ultra, FSR 2.0
Don't forget to exit the game and reboot the computer as the video API should be refreshed.
It's very easy to use any search engine to find out how to do the startup.meta file trick to get your own solo session, just search "red dead online startup meta" and yeah, griefer cheaters have pretty much taken over public RDO... R* doesn't care.
True that globally, Vulkan tends to be more stable. But not always.
Changing from the default Vulkan to DirectX 12 did solve the issue on my system, full AMD.
And the culprit was Vulkan, wrongly used by Steam on some specific configurations, especially high-end PCs using AMD SmartAccess Memory unlocking the dGPU memory.
The precompiling of shaders was not properly done and it had to be disabled within Steam. Vulkan was not receiving in times the necessary data for feeding at 5K 32:9 120 fps, hence aborting.
It is system dependent. Vulkan is only better if your configuration makes it shine as it is, which should be the case for most/many.
But if you have a problem, you should not rule out potential solutions...
I will certainly try switching to Vulkan (it is currently on DX12 after all), and I'll report any changes I experience.
I'll also check that solo-session trick out when I get home. While I can generally peruse Steam forums at work with no issues, I have to be very careful what I search for with search engines, particularly for games if it may be a mod obtained from Nexus Mods with all its sometimes-NSFW content.
Hopefully, a solution is in sight with one or both of those suggestions. Sincere thanks for taking the time to try to help.
With CPU : AMD Threadripper PRO 7000 WX, GPU : AMD Radeo PRO W7900, 128 Mb RAM, on a Samsung Odyssey G9. I can assure you it is way more than your regular PC. And it helps a lot for mathematical modeling . And obviously gaming also of course...
It is not a gamer PC, it is a workstation. :)
But what is ONLY important, is to see the OP solving his/her problem. Not arguing about this is best, no this is better.
The issue I talk about was reviewed by Steam Support, and it is them who gave the answer. Steam simply does not built always a flawless interface between its internal process (of Vulkan), and the specific use made by semi-external games like RDR2. Actually, it is best using/playing RDR2 without Steam...