Game crashes while compiling shaders.

[cylinderofantigod]

Game crashes upon launch while compiling shaders with "LowLevelFatalError".

Looks like a LOT of people are having this issue on Intel 13th and 14th gen with NVIDIA cards. I'm on Linux, but it looks like a very common issue on Windows as well.

Trying to launch the game with "-dx11" causes "Fatal error!" after the video followng character creation (which is also exactly what happens to people on Windows who have this issue). Updating drivers didn't help.

Going to install if on my Ally and see if it works on that. If it doesn't and they don't issue a fix relatively quickly, I've got no choice but to refund the game.

[germy813]

It's a known bug. Digital foundry covered

[Cythal]

I have AMD GPU. It seems the settings in appdata/Local/Alabama is setting DLSS as default for any GPU. I disabled it, launched and was generating shaders fine with no immediate crash. Then I went to steam to create a post and share my findings and something happened and it crashed my whole system and had to reboot.

[brianmia]

I got it to work by clicking properties in the exe file and selecting “run as admin”, “run compability mode for windows 8” and “disable full screen optimisations”

[cylinderofantigod]

Interesting. I did read the Run as Admin/Windows 8 compatibility fix, but I'd have to do more tinkering that I'd like to figure out how to replicate that on Linux.

It's running just fine on my Ally (also Linux), so I'm going to enjoy the actual game for a little bit and then come back to it.

I might try disabling DLSS and seeing if that helps. DLSS makes everything look like garbage, anyway (I know they're fixing this, but it doesn't look like Avowed has DLSS4 support, anyway).

[cylinderofantigod]

I found a workaround. After launching the game on my Ally, I can now continue the game on my PC using the "-dx11" startup option. Awesome.

For some reason, the game experiences graphical issues that make it unplayably bad unless upscaling is set to DLSS3 on Performance (Quality has graphical errors, and any other upscaling option, including turning it off, results in a all or part of the screen being black).

[Kneehow]

That's strange. Does your Ally and PC share game files in some ways? I still get fatalerror when loading into the game past character creation.

[cylinderofantigod]

Yes? They share save files through the cloud?

For clarification, I launched the game on the Ally, played the first few minutes of the game, and then loaded that save file on my PC.

Whatever the problem is that causes it to crash seems to be related to the part after character creation specifically. If I try to create a new character, it still won't progress past the video after character creation on PC, but I can load any save file made after that (using DX11).

So if you have a computer with another setup, load the autosave made after character creation (your character should still be there), manually save, and then load that on whatever device you actually want to play on.

Also, if anyone cares, the game runs buttery smooth on Ally with some fiddling.

[Kneehow]

Hey wanted to thank you because I wouldn't have tried it otherwise and just to get it out there for others. But for me turning all my settings on low and switching to upscaling TSR got me in game. Then I messed with the settings so it wouldn't crash in dialogue and I found I needed to put postprocessing on low. Other settings didn't seem to matter and the game works fine now. I do see some weird graphical glitches like you mentioned but nothing crazy. Of course all of this while in DX11 and I unfortunately don't have another device except my windows PC so it worked without that trick.

[Shekels]

Don't worry. You paid to beta test their game. So don't go complaining about it.

[cylinderofantigod]

I mean, it sucks that it took three hours to get working, but I'm having fun now.

[TaliHazard]

-dx11 made the game actually launch on my steam deck when before I was just getting a black screen then the crash message you had.

[Dark Wombat]

I reinstalled, then downloaded latest AMD drivers, fixed it.

[Emi-Chan]

Obsidian have acted disgracefully, utterly disgraceful during this early access to owners of 13/14th Gen Intel processors which make up the vast majority of their player base hence the pointless and stupid graphics shading which has serious issues with these latest processors, but still the morons kept them knowing there would be serious problems.

I don't have the steam version of this game, I have the m$ version, because I got it half the price for the ultimate edition on a 3rd party site which I often use.

However somehow I managed to get into the game by doing something, and was able to create character -> get to the end of the starter island after which it crashed after trying to get onto the boat. I then tried compatibility mode with windows 7, it worked then crashed, then I tried it with windows 8 and it crashed, but when it initially loaded up I was on a dock, ran around for a minute or two, then it just ctd.

Since then I have tried everything, now it's trying to start in window mode, no idea why. Tried downloading a dozen times to no avail, nothing seems to work any more.
If I add -dx11 the game completely ignores the graphics caching at the beginning, it gets to the character creation, then loading into the game it crashes.

[Emi-Chan]

Originally posted by Shekels:

Don't worry. You paid to beta test their game. So don't go complaining about it.

no, we paid for early access...as obviously did you...and your damned straight we'll complain about it, when the game is so broken, that people can't even get passed pointless loading shader screen don't even get me started on the full early access price of this game, we still can't run, despite having high end gaming rigs!

[Sokar79]

i am getting this Fatal alabama UE5 error after longer period of time of playing this game, it looks like some kind of memory leak or something, any word on fix from devs pls? Thanks.