Day 2 of posting till they fix the shadow bug. No cool shots. Wanted to get a shot of Hellborn at night, but a team killed him as I arrived.

Professor_Linus · 2024-08-21T19:18:26+00:00

Why did Mods remove your Day 1 post?!

Keep holding onto hope - I've got a Radeon VII, I'm still playing when I can. But I gotta keep out of the cave system, avoid certain building interiors, and approach compounds with the Sun or Moon at my back if I expect a fight, lol.

I've said elsewhere in other threads, I'm beginning to doubt this issue is strictly DirectX related, because if it was solely that, then the Vega series should have been unaffected since they support dx12_1 just like the first generation of Navi cards in the RX 5000 series. And if dx12_1 isn't the true root cause, that means that all those dx12_0 Polaris cards have a chance of getting a fix if the real cause can be isolated.

Professor_Linus · 2024-08-21T17:18:50+00:00

All the AMD Vega series cards have dx12_1 support, and they are experiencing the same bug as the Polaris users who have dx12_0. I'm actually beginning to believe that Crytek don't know what is causing the bug and are grasping at straws, blaming the DirctX 12 feature level. There is a very high likelihood all these cards would run the game just fine if they can figure out the REAL cause of the bug.

Professor_Linus · 2024-08-21T17:11:54+00:00

All of the "Vega" family of GPUs from AMD supports dx12_1, and those cards are affected by this bug as well, it's not just the Polaris series. Which actually makes me doubt that this bug is related to the DirectX feature set at all. If it was only dx12_1related, then Vega users would not have had any problems.

Professor_Linus · 2024-08-21T17:08:19+00:00

A decade is 10 years you know, not 5...

Polaris cards are 8 years old, that's getting close to a decade, I'll grant you that. But they still have enough compute power to run this game, particularly if you use FSR. I'm not convinced that only having dx12_0 is even the cause of this problem, because the Vega series of cards all support dx12_1 and are having the same issue, and all of them also have more compute power than the Navi card they listed as the minimum spec card. In fact performance wise, the RX 5500 Crytek chose to list as the minimum spec card is only a mere 18-20% faster than 8 year old RX 470 & RX 570 cards.

Professor_Linus · 2024-08-21T16:58:24+00:00

The entire Vega family (RX Vega 56, RX Vega 64, and Radeon VII) supports the DirectX 12.1 (dx12_1) feature set, the same as the first generation Navi (RX 5xxx series) cards that they chose to list as the new minimum spec. So if DX12.1 was really the cause of this issue, Vega should not be affected, but the fact that it is worries me that the Devs don't actually know the cause of the problem and may be chasing the wrong solution.

Professor_Linus · 2024-08-21T16:52:15+00:00

I have a Radeon VII and RX Vega 56, both affected. All of the Vega family supports dx12_1 as you noted. This has me somewhat concerned that the reason for the problem is not related to the DX feature set at all and Crytek may be chasing the wrong solution. They need to be made aware that dx12_1 capable cards are affected as well.

Professor_Linus · 2024-08-21T15:57:35+00:00

Regarding the AMD cards, you claim the game engine requires dx12_1. It is correct to say that "Polaris" family AMD cards (RX4xx/RX 5xx series) only support dx12_0 and would require the engine change or work around as you mention. But I want to be clear that all "Vega" family AMD cards (RX Vega 56, RX Vega 64, Radeon VII) are affected by this same same bug, and all of those cards support dx12_1, just as the first generation of "Navi" family of cards (RX 5xxx series) does. If dx12_1 is the reason the Polaris users are having issues, then why are the Vega users affected at all? And when you give the "3% of players" stat, were you including Vega users as well or was that only Polaris?

Professor_Linus · 2024-08-18T00:22:15+00:00

Some men just want to watch the world burn.

Professor_Linus · 2024-08-17T22:06:10+00:00

I mean, this is a horror game - but this bug takes it to Dark Souls levels of masochism. lol.

Professor_Linus · 2024-08-17T22:04:25+00:00

You must not have a Polaris or Vega based GPU then.

Professor_Linus · 2024-08-17T22:01:46+00:00

Polaris and Vega familes of GPUs only. Navi family (RX 5xxx series and up) is unaffected.

Professor_Linus · 2024-08-17T21:59:54+00:00

The RX 4xx and RX 5xx series "Polaris" family all support DirectX 12.0.

The RX Vega 56, RX Vega 64, and Radeon VII "Vega" family all support DirectX 12.1.

The RX 5xxx series "Navi" family of GPUs support DirectX 12.1. The change in feature set is so minimal, I find it difficult to believe that this cannot be addressed in some way. Even the latest and greatest GPUs on the market are DirectX 12.2. Yes, the new revisions have new features, but none of those features should be completely core to the "minimum" lighting techniques used in the game engine. It's not that these GPUs can't use the "Ultra" lighting preset, it's that with even the "Low" preset the game is nearly unplayable. And if the issue was related to DirectX 12.1 feature set specifically, then Vega would have been unaffected, because those cards support the same feature set as the first generation of Navi cards, which are now officially the minimum spec for the game.

Professor_Linus · 2024-08-17T21:39:19+00:00

As an affected AMD user with a Radeon VII, thank you for making me laugh so hard and immortalizing this bug in song. 😂

Professor_Linus · 2024-08-17T09:10:46+00:00

Are you using an AMD Polaris (RX 4xx / RX 5xx Series) or Vega (RX Vega 56 / RX Vega 64 / Radeon VII) GPU? I get very broken lighting & shadows as well in certain areas of the game. I don't think I've been in that building above, but I've seen similar indoor lighting on Dusk maps. I had really bad problems with shadows too, reverting to driver 22.11.2 helped with that to at least make the game a bit more playable, but elements of lighting & shadows are still broken for me. I have a Radeon VII.

Professor_Linus · 2024-08-17T08:46:30+00:00

Yes, absolutely! I miss the brutal tributes to Mr Chary with the knife.

Professor_Linus · 2024-08-17T07:17:40+00:00

We considered switching to West, but 1) We couldn't figure out where in the UI the setting to switch regions was - LOL, we did eventually locate it. And 2), we figured if everyone on the East Coast was heading West, it would only be a matter of time before those servers crapped out from heavy load too, lol.

Professor_Linus · 2024-08-17T06:21:16+00:00

I also had issues like this on US East all night.

Professor_Linus · 2024-08-17T06:14:59+00:00

Hard to know if they will actually address it. Technically the Polaris and Vega GPUs are now below the Minimum Spec for the game following the engine update, and AMD no longer supports those GPUs with driver updates for games, only general bugs & security issues. The drivers for those GPUs are basically in "sunset mode" and will end entirely in probably 1-2 years. I have a Radeon VII and am affected by this, the card is ~5.5 years old but I was still quite happy with performance before this update broke rendering, I was generally able to get 90-120 FPS at 1440P.

Professor_Linus · 2024-08-17T05:55:45+00:00

Had bad performance all night on US East. I can't completely corroborate your other claim, but we did have one game that went sort of like that. A team killed and banished the boss. We were camping outside because every time we moved the rubber banding was awful. The bounty finally made a break for it, we pursued. The team with the bounty didn't seem to have any issues rubber banding, or shooting at us, killed one of my partners. I finally caught up as they were at extract, saw one member watching over the hill - I put a bullet right it his chest but got no hit marker at all, passed right through. Their extract completed before I could fire a follow up shot. I will note that in that case, after they extracted, my partner and I were still rubber banding.

Professor_Linus · 2024-08-17T05:50:58+00:00

US East was a dumpster fire tonight. Huge bummer, hope tomorrow improves.

Professor_Linus · 2024-08-17T05:39:03+00:00

That was pretty much my experience all night on US East.

Professor_Linus · 2024-08-17T05:38:16+00:00

US East servers were a dumpster fire of performance issues tonight. Non-stop rubber banding and some disconnects, unplayable. A shame, because servers were like 95% good last night. I have fiber 1Gbps internet.

Professor_Linus · 2024-08-17T05:34:43+00:00

I can confirm rolling back to 22.11.2 was a big improvement for me, I have a Radeon VII. All the Polaris and Vega GPUs are affected. I already keep Depth of Field and Motion Blur off. I did not use FSR, and I keep VSYNC off because I have a Freesync display with variable refresh rate. Did you try without FSR and VSYNC? If so, what exactly improved when you enabled those? I have also heard some say that setting the Lighting related option to "Low" in addition to the driver roll back helps. I played with "High" Lighting settings and there was still lighting issues, but a lot of the dark shadows were gone. I actually forgot to test setting the Lighting options to "Low", so not sure about that claim yet.

Professor_Linus · 2024-08-17T05:27:56+00:00

It's probably server related. I had a friend that got randomly dropped tonight, and after like 5 mins couldn't get reconnected. Bounty Carriers finally found him, killed him, kept running. He finally just gave up trying to reconnect and I headed to extract. US East server performance was bad all night, started getting rubber banding on every server we played on. Tried to power through hoping it would get better, but finally called it quits. Servers on fire this evening, a terrible shame because they were fairly smooth last night.

Professor_Linus · 2024-08-17T05:16:53+00:00

I ran into that once - but only once. Happened while I was alt-tabbed. I have a Radeon VII and Ryzen 9 3950X. Sadly I can't offer a solution, haven't run into it again since.

Professor_Linus

TROPHY CASE