absolute garbage

[kcornia]

I've done all the things on their support site, updated the bios, checked integrity of the game, etc. and still crashes at generating shaders 80% of the time, weeks after launch.

What happened to you Obsidian, you used to be cool.

[Xeirus]

Don’t know why bios would matter, but I’ve never had issues with the shaders once. Had a few crashes after the most recent patch though.

Did you uninstall the game completely and delete the shaders?

If so I think you need to OS restore and let us know if that did it.

[catch22atplay]

If the OP is using 13th or 14th gen cpu and updated the bios. Then you need to select Intel Defaults or whatever your motherboard manufacturer said to do. If it still doesn't work i'd look into potentially replacing the cpu.

UE uses Oodle decompression and this is what causes the errors with unstable cpus. Note that any cpu can cause errors if it's unstable. So 13th/14th gen or not it's on YOU to fix your unstable machine. Devs can't fix an unstable system.

I'd try OCCT using AVX2 or AVX512 extreme/steady/fixed/all threads selected for cpu stability testing.

Ah and according to another post you made you have a 13th gen cpu. Well to me that pretty much confirms the cpu issue. Update your bios dude and pray it works.

[Draxuss]

Originally posted by catch22atplay:

If the OP is using 13th or 14th gen cpu and updated the bios. Then you need to select Intel Defaults or whatever your motherboard manufacturer said to do. If it still doesn't work i'd look into potentially replacing the cpu.

UE uses Oodle decompression and this is what causes the errors with unstable cpus. Note that any cpu can cause errors if it's unstable. So 13th/14th gen or not it's on YOU to fix your unstable machine. Devs can't fix an unstable system.

I'd try OCCT using AVX2 or AVX512 extreme/steady/fixed/all threads selected for cpu stability testing.

Ah and according to another post you made you have a 13th gen cpu. Well to me that pretty much confirms the cpu issue. Update your bios dude and pray it works.

I 100% agree. I had to lower my OC on my CPU to get past the shader loading. High CPU temps will also cause this to happen. 14700K

[DeadJericho]

y cruncher or core cycler are also good things to test stability.

[kcornia]

Guys I play TONS of games, including multiple UE games. This computer is less than 2 years old and is rocking a 4090, a nice Asus mobo, and gobs of RAM with a i7-13700 CPU. NO other games have had issues at all. So forgive me for being skeptical of needing to replace my CPU, reinstall my OS, over/underclock, etc.

I've been playing games since my Commodore 64, used to set my own pins, you name it. We just shouldn't be in a place where one game comes out like this and can't handle a broad spectrum of hardware.

I'm not going to let them make their problem my problem. It was fun to play until it started blowing up, now I'll move on to one of dozens of other games I have to pass the time. I'll check back periodically to see if they've fixed it and if so I'll be happy to finish.

Now if Solasta 2 has these issues, I will move heaven and earth lol...

[DeadJericho]

last thing you could try it clearing the nvidia shader cache

not sure where its located. but google will help i expect

its quite telling that it only crashes at compiling shaders. once theyve been compiled they really dont get compiled again until a driver or game update.
so its crashing whilst loading them rather than compiling

[catch22atplay]

Originally posted by kcornia:

Guys I play TONS of games, including multiple UE games. This computer is less than 2 years old and is rocking a 4090, a nice Asus mobo, and gobs of RAM with a i7-13700 CPU. NO other games have had issues at all. So forgive me for being skeptical of needing to replace my CPU, reinstall my OS, over/underclock, etc.

I've been playing games since my Commodore 64, used to set my own pins, you name it. We just shouldn't be in a place where one game comes out like this and can't handle a broad spectrum of hardware.

I'm not going to let them make their problem my problem. It was fun to play until it started blowing up, now I'll move on to one of dozens of other games I have to pass the time. I'll check back periodically to see if they've fixed it and if so I'll be happy to finish.

Now if Solasta 2 has these issues, I will move heaven and earth lol...

Been playing games since the Atari 2600. Bought a C64 when it first came out. Think i was 20 or so. Been building computers for myself and others for a long time now.

There are a few things it can be. Bad cpu, corrupted gpu driver, VS C++ corrupted. Corrupted windows and by these corruptions it can be just 1 file. It's rare but nvme's have issues as well. All of these just for compiling shaders. I'm sure i left something out like mobo, memory, psu, etc. The greater majority of the time it's the cpu. The chance it's the actual game is like 0.01%. So go in your bios and change some settings around. Check PL0 and PL1 and set them correctly. And total amps as well. Or just try the Intel defaults. Download and run XTU from Intel and try downclocking and or disable e-cores and lower p cores just as a test and see what happens. Or download process lasso and set it up for this game and set it to run on say just 4 P-cores and see what happens.

[xEZ TECx]

I honestly think this game is a rip off. It takes place in the pillars of Eternity universe. And is in the living lands, Again, another spot in pillars of eternity. You have all the same followers too. it's hilarious.

Vault
OS: win 11
CPU: Ryzen 7 5700x3d
ram: 32gb ddr4 @ 3200 MHz
mobo: Asus Tuf X570 + WiFi
Gpu: Msi Rx 7900xt gaming trio
monitor: Asus Tuf 34" display @ 3440x1440 12 bit display & 120 Hz refresh rate

And i've played this game with ray tracing on/off. not that much of a diff. And the only oc i do is windows power settings to ultimate performance. If you guys have way better then what i have and i can run it without issues at all. then it's user error not the games fault.

[Krayor Krelion]

Originally posted by catch22atplay:

Been playing games since the Atari 2600. Bought a C64 when it first came out. Think i was 20 or so. Been building computers for myself and others for a long time now.

There are a few things it can be. Bad cpu, corrupted gpu driver, VS C++ corrupted. Corrupted windows and by these corruptions it can be just 1 file. It's rare but nvme's have issues as well. All of these just for compiling shaders. I'm sure i left something out like mobo, memory, psu, etc. The greater majority of the time it's the cpu. The chance it's the actual game is like 0.01%. So go in your bios and change some settings around. Check PL0 and PL1 and set them correctly. And total amps as well. Or just try the Intel defaults. Download and run XTU from Intel and try downclocking and or disable e-cores and lower p cores just as a test and see what happens. Or download process lasso and set it up for this game and set it to run on say just 4 P-cores and see what happens.

I invented computers (totally, true story). And I say that sometimes a problem with a game is just the game. When you have wide spread reports of the issue from people with various configurations, it's probably the game.

For those experiencing crashes, send a report to Obsidian: https://avowed.obsidian.net/issue-tracker#07NXlUjl-how-to-report-a-bug

Note: Use MSInfo to send your system info:

HOW TO GENERATE AN MSINFO

1. Open a Run command box. To do so, press the Windows key and R key at the same
   time.
   1b. Alternatively, search for "Run" in your Start menu's search bar.
   
2. In the Run window's dialog box, type msinfo32 and click OK.
   
3. When the System Information window opens, allow it to pull information from your
   system. You’ll know it’s done when you click through the menus on the left and see
   information for each of them.
   
4. Keep "System Summary" highlighted.
   
5. Click File, then Export...
   1. Do not choose File, then Save as. This will create a very large file you may not
   want on your system, and Obsidian's system has a file size limit that might reject it.
   2. Name your file something simple, like "mymsinfo", and make sure it’s saved as a
   text (.txt) file.
   3. Save the exported file on your Desktop or your My Documents folder.
   4. The file can take a minute or two to export and save.

[catch22atplay]

OK Charles i guess you're a ghost. You died in 1871.

[Draxuss]

I'll almost bet OP's CPU is either overheating or unstable during shader compile and it's easy enough to figure out if this is the case.

[kcornia]

Originally posted by catch22atplay:

Originally posted by kcornia:

Guys I play TONS of games, including multiple UE games. This computer is less than 2 years old and is rocking a 4090, a nice Asus mobo, and gobs of RAM with a i7-13700 CPU. NO other games have had issues at all. So forgive me for being skeptical of needing to replace my CPU, reinstall my OS, over/underclock, etc.

I've been playing games since my Commodore 64, used to set my own pins, you name it. We just shouldn't be in a place where one game comes out like this and can't handle a broad spectrum of hardware.

I'm not going to let them make their problem my problem. It was fun to play until it started blowing up, now I'll move on to one of dozens of other games I have to pass the time. I'll check back periodically to see if they've fixed it and if so I'll be happy to finish.

Now if Solasta 2 has these issues, I will move heaven and earth lol...

Been playing games since the Atari 2600. Bought a C64 when it first came out. Think i was 20 or so. Been building computers for myself and others for a long time now.

There are a few things it can be. Bad cpu, corrupted gpu driver, VS C++ corrupted. Corrupted windows and by these corruptions it can be just 1 file. It's rare but nvme's have issues as well. All of these just for compiling shaders. I'm sure i left something out like mobo, memory, psu, etc. The greater majority of the time it's the cpu. The chance it's the actual game is like 0.01%. So go in your bios and change some settings around. Check PL0 and PL1 and set them correctly. And total amps as well. Or just try the Intel defaults. Download and run XTU from Intel and try downclocking and or disable e-cores and lower p cores just as a test and see what happens. Or download process lasso and set it up for this game and set it to run on say just 4 P-cores and see what happens.

You're like a broken record. If I was the only one having this problem I'd assume it was me. But here's the thing. It's NOT just me, it's thousands of people. On top of that, right now I'm regularly playing Diablo 4, Cyberpunk 2077, Civ 7, Cities Skylines 2, Solasta 1, Solasta 2 demo, Stalker 2, BG3, Test Drive Unlimited 2, POE2 (not anymore really), Kingdom Come 2, etc. (Yes I'm easily distracted, no I haven't finished any of them). All at ultra settings.

NONE of those games have this issue. So you're wanting me to believe that it's my PC despite all those mostly AAA games running perfectly, and tons of other people with different PC setups complaining about the same issue? Sorry but no.

And I also had the Atari (and Intellivision, and Colecovision), but when I got my C64 I was 8 so you're an old man :P

[catch22atplay]

And none of the games you mentioned are using Oodle for decompression. And that's what shows the issues with 13th/14th gen Intel cpus. All i'm saying is at least do 1 or 2 fairly easy tests i suggested. But no it can't be your system right. I'm not responding any more to the broken record of people saying "all my other games work fine except this one so it must be the game" when sure it sometimes is the game. But if using Intel 13th/14th gen cpu and the game is using Oodle decompression you MUST eliminate the KNOWN cpu issue as being the cause. After eliminating the cpu as being the fault then blame the game. I've done enough Tech support over the years to at least be logical.

[Draxuss]

Originally posted by kcornia:

Originally posted by catch22atplay:

Been playing games since the Atari 2600. Bought a C64 when it first came out. Think i was 20 or so. Been building computers for myself and others for a long time now.

There are a few things it can be. Bad cpu, corrupted gpu driver, VS C++ corrupted. Corrupted windows and by these corruptions it can be just 1 file. It's rare but nvme's have issues as well. All of these just for compiling shaders. I'm sure i left something out like mobo, memory, psu, etc. The greater majority of the time it's the cpu. The chance it's the actual game is like 0.01%. So go in your bios and change some settings around. Check PL0 and PL1 and set them correctly. And total amps as well. Or just try the Intel defaults. Download and run XTU from Intel and try downclocking and or disable e-cores and lower p cores just as a test and see what happens. Or download process lasso and set it up for this game and set it to run on say just 4 P-cores and see what happens.

You're like a broken record. If I was the only one having this problem I'd assume it was me. But here's the thing. It's NOT just me, it's thousands of people. On top of that, right now I'm regularly playing Diablo 4, Cyberpunk 2077, Civ 7, Cities Skylines 2, Solasta 1, Solasta 2 demo, Stalker 2, BG3, Test Drive Unlimited 2, POE2 (not anymore really), Kingdom Come 2, etc. (Yes I'm easily distracted, no I haven't finished any of them). All at ultra settings.

NONE of those games have this issue. So you're wanting me to believe that it's my PC despite all those mostly AAA games running perfectly, and tons of other people with different PC setups complaining about the same issue? Sorry but no.

And I also had the Atari (and Intellivision, and Colecovision), but when I got my C64 I was 8 so you're an old man :P

Have you even tried to eliminate the possibility of your CPU being the issue? This isn't the only game that gave me issues until I addressed any potential problems with my CPU (14700K). Usually on fresh load of shaders if it crashes @ 80% and then retry it will work. Also Iv'e been building gaming machines for years so I know a little bit. And wtf does age have to do with anything here besides experience?

[Draxuss]

After all this and the the clown awards from OP it's easy to see that this person did not come here for help, just wanted some attention.