[BUG:RESOLVED] Crash Accessing Private Storage :: S.T.A.L.K.E.R. 2: Heart of Chornobyl General Discussions

S.T.A.L.K.E.R. 2: Heart of Chornobyl

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

S.T.A.L.K.E.R. 2: Heart of Chornobyl > General Discussions > Topic Details

Large Tomatoes Dec 7, 2024 @ 9:47pm

[BUG:RESOLVED] Crash Accessing Private Storage

A new repeatable issue has occurred for me since installing 1.0.3. I wanted to check if anybody else had this before writing a bug report.

My private storage contains lots of ammo (multiple stacks for each type), roughly 10 weapons, hundreds of healing items/anti-rad/food/drink. Whenever I access the storage it allows me to put/take stuff from the storage, however, after roughly 5-10s the game hangs and I have to sign-out to recover

I'm not sure if it's the number of items in the storage that is causing the issue or if it's the latest patch. I have been getting lots of crashes with this latest patch but they have been random.

System

Specs: Windows 11, 32 GB, 4090, 12900K, Running from SSD.
NVIDIA Driver Version: 566.36
Windows Version: 23H2
Game Version: 1.0.3

Fixed - Worked Around

I downgraded my install to the previous release and loaded an older save, this seems to have stabilised the storage container issue, time will tell if the other crashing issues have gone. I'm unsure if loading an older save was necessary, but it's working now and it's taken me an hour to get here so I ain't touching it. I've looked in all the usual places for logs but I can't see anything of value, if there is a specific dump dir that I can inspect I would be happy to send them to the devs should you want.

For now, I won't be installing 1.0.3, I will wait for the next release and see what comes of that.

Last edited by Large Tomatoes; Dec 7, 2024 @ 11:24pm

< >

Showing 1-4 of 4 comments

Large Tomatoes Dec 7, 2024 @ 11:20pm

Originally posted by Donaldo Trumpado:
And what do you have running in the background

Coincidentally I was just typing in another thread that I should update this as I "fixed" the issue. But to answer your question, not much, it is on my dedicated gaming rig so only the absolute minimum is set to auto-start at boot.

See update in top level post if interested.