Out of Video memory

[Sandman]

When I open the game it does it's Shader Pre-cache countdown then i get a low video memory error. I have an I9 14900K, 64Gb of 6400MHz ram and a 4080 super. Plenty of power to run this game. Any ideas? Other games run just fine.

[Rune]

It's because of Oodle decompression crashing due to unstable out-of-range core enhancements with no power limits set by your motherboard. Intel is aware of this, and some motherboard vendors are releasing BIOS updates to default back to Intel's factory settings without auto OCs. You can read about it here, aswell as solutions: https://www.radgametools.com/oodleintel.htm

You can change these settings manually without a BIOS update, but they make it easier with a simple button change.

[ko]

Yeah, 14900K is crash city in Unreal engine if you don't set your BIOS correctly (bad defaults). It's not just Oodle, it is a general issue when you put a lot of load of the CPU. It will throw out a video memory error. Other Intel CPUs from the 13XXX/14XXX series have this issue to varying degrees.

[NijimaXL]

follow that Oodle troubleshooting above.

[VKvampire]

I solved this problem by increasing the swap file to 45 GB
I know that video memory does not interact with the swap file, but this helped me. The game loads and does not crash during the gameplay

[Jurassic Fart 1]

Any time I'd encountered that message I'd found it to be complete bullcrap. My rig is WAY OP with respect to specs; I have FAR more memory resources and speeds than the game requires. It's an idiot developer code-writing fault. I don't sweat it. At the worst, I just close the game and relaunch, scrubbing all the crap clogging volatile memory.

[Lightor]

I had the same issue, is actually an Intel issue. I updated my BIOS and have never seen it again.

[=XFG=Hubert von Hans]

If you have seen this issue, your CPU is already damaged.

[Lightor]

Originally posted by =XFG=Hubert von Hans:

If you have seen this issue, your CPU is already damaged.

False.

I had this issue and updated my bios months ago. I have had no issues or impact to my CPU. Please don't spread misinformation.

[Lithurge]

Originally posted by Lightor:

Originally posted by =XFG=Hubert von Hans:

If you have seen this issue, your CPU is already damaged.

False.

I had this issue and updated my bios months ago. I have had no issues or impact to my CPU. Please don't spread misinformation.

It's not false, your CPU has been damaged, it's just the degree of damage is not enough to cause you problems but the overall lifespan will have been shortened. As most people don't keep their rigs to point of failure it's not likely to be an issue.

[Lightor]

Originally posted by Lithurge:

Originally posted by Lightor:

False.

I had this issue and updated my bios months ago. I have had no issues or impact to my CPU. Please don't spread misinformation.

It's not false, your CPU has been damaged, it's just the degree of damage is not enough to cause you problems but the overall lifespan will have been shortened. As most people don't keep their rigs to point of failure it's not likely to be an issue.

Ok so there's a small amount of damage that no one can see but it's there. From what I read it was a BIOS issue. Do you have any proof to backup what you're saying since most people will never know about this mysterious level of "damage."

[Jurassic Fart 1]

Originally posted by =XFG=Hubert von Hans:

If you have seen this issue, your CPU is already damaged.

Who the Hell taught you that? That is complete garbage. There is absolutely nothing deleteriously affecting the performance of my i9-10900F CPU. I've been working with computers since 1984, and I have never heard anything so completely absurd.

It is not a message alerting you to CPU damage. The message may be triggered by a number of events, most merely annoying, and if your CPU has been damaged, then you were doing something else that caused the damage...like overclocking and failing to monitor temperatures and set alarms.

"Already damaged." Jesus.

Tapping out; won't respond further. There's been good advice that is being ignored. Trying to do more is casting pearls before swine.

[dethtrain]

Any workarounds to be able to actually play the game? Looks like I might have to refund this :(
edit: went into power settings and capped maximum processor performance to 15% and it was able to finish compiling shaders. Closed the game, reverted back the cap and when I ran the game again, it was able to compile the shaders without crashing.

I assume this happens every time I start the software. It's usually a 1 time thing unless there is an update to the game.

[Lithurge]

Originally posted by Lightor:

Originally posted by Lithurge:

It's not false, your CPU has been damaged, it's just the degree of damage is not enough to cause you problems but the overall lifespan will have been shortened. As most people don't keep their rigs to point of failure it's not likely to be an issue.

Ok so there's a small amount of damage that no one can see but it's there. From what I read it was a BIOS issue. Do you have any proof to backup what you're saying since most people will never know about this mysterious level of "damage."

Your individual CPU? Of course not, but you want to ignore Intel admitting there is an issue and releasing multiple patches to fix it as evidence then that's up to you.

https://www.zdnet.com/article/intel-chip-bug-faq-which-pcs-are-affected-how-to-get-the-patch-and-everything-else-you-need-to-know/

[Lightor]

Originally posted by Lithurge:

Originally posted by Lightor:

Ok so there's a small amount of damage that no one can see but it's there. From what I read it was a BIOS issue. Do you have any proof to backup what you're saying since most people will never know about this mysterious level of "damage."

Your individual CPU? Of course not, but you want to ignore Intel admitting there is an issue and releasing multiple patches to fix it as evidence then that's up to you.

https://www.zdnet.com/article/intel-chip-bug-faq-which-pcs-are-affected-how-to-get-the-patch-and-everything-else-you-need-to-know/

How are you connecting this to the same issue? I'm not finding anything in there calling out the out of video memory issue. This seems like two separate issues unless there's something here I'm missing.

They even called out this issues as "Intel describes them as instability issues commonly experienced as consistent application crashes and repeated hangs." I never got hangs and only a few crashes when I played games. Never had consistent application crashes or hangs at all, just the one message when loading some games. Everyone here seems to be seeing that as well. Again, this doesn't feel like the same issue unless you can find something saying so.

You saying they had a problem and this is also a problem, so they are all the same seems like a very inaccurate way to determine the truth. And there wasn't multiple patches, it calls out one specific patch, the "microcode 0x129 update." So I'm not sure what you're talking about there either. Was there one patch for one thing and then another patch for another. Or are you saying there were multiple patches for the same issue?

[Fr0gg0]

I just bought a new pc, RTX 5080 and Ryzen 7 9800x3d, and I got this out of memory crap trying to play this game. Never get it before with 3060 ti and i7 6700k.. ugh