gun problem

[artsid1]

There was a problem with choosing a pistol and a composite bow, while they were lying in a backpack, it's okay as soon as you pick up the game falls
Is it just me? Could not understand what the problem is
gun problem

[FT]

I am having a similar problem after the A17 update. Weirdly, the game worked fine for the first hour or so of playing, including guns, but now it'll crash within minutes or sometimes immediately even with settings the same or lowered to make sure I'm far from running low on RAM.
One of the things that will immediately crash 7D2D for me now is picking up a pistol. Even if I turn on cheats and grab a pistol from the extended menu, instant crash.
The crashing usually needs a TaskManager shutdown to kill the game, and it almost always means the save file will instantly crash upon re-entry. So a crash usually means that whole game is toast.

I'm on a fresh install after making sure Windows and hardware drivers are up to date, clearing previous saves, uninstalling, deleting registry files from the uninstalled game, re-downloading, verifying file integrity without issue and repairing the SteamLibrary. I've doublechecked the RAM and HD for errors which came up fine, and I don't have any GFX issues either. This whole system works flawlessly on everything else, including A16 and previous, so I'm super confused.

[FT]

So far I've noticed that holding a pistol in hand will crash, holding rocketlauncher, holding assault rifle, and firing/loading the compound bow will also cause a crash. Holding the compound bow is fine, and the wooden bow and crossbow are completely fine. The rest of the guns and the nailgun seem to work alright as well aside from wonky reloading glitches. I haven't tried any of the guns with mods/scopes though.

Is anyone else having weirdly specific problems like this?
I'm eperiencing other crashes and quirks too, but these gun crashes just seem extra strange and they've been pretty consistent.

[artsid1]

AK47 problems too
Work only shothgun and hunting rifle

[artsid1]

I give up. at least five times demolished the game to zero. checked for integrity. but the problem remained. Wood bow apparently everything that I deserve ...

[FT]

I spent a long time with cheats on and several game crash/reboot cycles trying to find which things were safe to pick up and which things would cause a crash that blackholes the save. After some luck there, I've started getting more random crashes now that I can play for a bit.
My computer is a pretty old potato that could never run the game well at high settings, but the game has been doing this random crashing even on low settings with lowered resolution where it runs decently smooth and isn't 100%ing anything.

If it makes you feel any better you may bask in this 2011-2012 glory.
CPU: AMD fx4100 not OC'd
RAM: 8gb, 2x4gb ddr3 at stock/1333
GFX: AMD/ATI hd6770 1gbVRAM
HDD: 5400rpm with plenty of space
PSU: 500watt fire-hazard that's been nicely behaved
Windows7Ultimate because 8/10 seems to fight more than it helps

What are you running 7days on?

I'm not sure what else to do about it. I hope the devs can get all these different crashes fixed quickly once they're back from their break.

[FT]

I completely rolled back my graphics drivers from DeviceManager and then dug around to find the old ATI CCC setup.exe from 2011 which let me uninstall all of the new CCC except the HDMI option. Then I installed the original 2011 CCC from the same ATI CCC setup.exe.
Next, instead of updating directly by using either of the newer CCC or Driver downloaded files that are still sitting here after grabbing them from AMD's site, I went back into DeviceManager and told it to try updating. This time it worked.
With the updated CCC and drivers I also decided to try the builtin OverDrive OCing tab that I've previously ignored. Everything there seems to work alright, though the board and powersupply get pretty warm.

Started 7Days and realized it's running smoother and using a lot less CPU than it was even at really low graphic settings. Turning all the OC business back off doesn't seem to make a huge difference either. CPU usage went up a bit, maybe because it cooled off a little, and framerates are about DOUBLE of what they have been. They're a lot more stable too.

So I tried flying around and collecting zombies by harrassing POIs and sending them tumbling, but it still runs well. Final test, grab an unloved safefile and see if holding a pistol crashes it. Nope, it's still running fine.
I'm guessing this second time with the drivers just worked much better. The previous time added different things which seemed to conflict, but letting the DeviceManager pick and choose whatever it wanted seems to have left an overall superior driver+CCC.
I also like to think that maybe the OCing knocked off some imaginary cobwebs, but I'm pretty sure it was just the driver update improvement.

[FT]

It still instantly crashes when holding a pistol, etc. IF the setting for DepthOfField is turned OFF. If I leave DOF turned on, so far everything is fine. If I turn DOF back on in pre-game settings before loading the crashed file, it'll load just fine too. I'm guessing they were instant crashing upon reload because the game saved with the last held item.

I wonder why it wants DOF turned on so badly.

[artsid1]

I also have an old computer. I did not find the old drivers for the video card.
Intel i5-3470
AMD Radeon HD6770
RAM 8Gb
Win 10-64
beginning to fall, even with a wooden bow, if an ally is near