Weapon switching issue, glitched weapon equips, and re-holstering bug

[pmeloche]

Hello Loverslab folks,

 

So I get this extremely frustrating bug as soon as I leave the Vault 111 and Sanctuary areas on a new game playthrough. Basically the guns and security baton, switchblade, all weapons malfunction when I enter a new area (new game cell?) beyond the immediate Vault 111 and Sanctuary areas. Weapons get stuck (for example stuck on 10mm pistol and won't unequip or switch properly to another weapon), glitch out, refuse to equip, and weapon models get frozen in 10 mm gun mode - see screenshots, for e.g. security baton equips like a pistol!! Bare hands are frozen in invisible pistol death grip. Weird. Game will then obsess over this, CPU maxes out, locked in an endless trying to remedy or load loop, and can't save, can't quit properly, have to CTRL-ALT-DEL to get out of game. 

 

Only happening now with the new version of the Fallout4.exe (1.10.82 +).

 

Happens with or without using F4SE (F4SE loader or regular F4 launcher). Only triggers in areas beyond Sanctuary (so in Concord near Museum of History also noticed it around the Concord water tower area).

 

I get it with lots of mods or minimal mods or no mods at all.

 

Best I can guess is it's some delay glitch or failure to load textures whilst loading new world area textures and the response time times out.

 

Also note this did NOT happen when I was playing game middle of last year (mid 2017) all the way up till about a month or two ago. So maybe newest game updates to blame? Perhaps rolling back to an older Fallout4.exe is the fix?

 

Eager to hear if anyone having this same game breaking persistent issue, what your fixes might be, and your general accumulated wisdoms!!

 

P.S. - Please check out my screenshots for the glitched out weapon equips.

 

Cheers,

 

P

[AWP3RATOR]

That knife coming out the hand reminds me of Wolverine....

 

Since you observe this during a test with no mods installed - it sounds like something in your game files is corrupt.  Have you run the Steam verify integrity of game cache?  You may try that, either directly with game files installed, or move/rename the game's folder and run it (this will download a new copy of Fallout 4) then test again.

 

Do you happen to be using Mod Organizer?  This would help with reinstalling your mods and/or testing without any mods in stalled, save for F4SE, which can be disabled simply by running the game with the regular .exe

 

Are you running an ENB?  Change your DX or video graphics drivers?  Anything change since you last played when this didn't happen?

[pmeloche]

Hi,

 

Yes I have tried verifying game cache, reinstalled,  etc, ran with and without ENB, nVIdia drivers are up to date and fine. The game runs perfectly except  for the fact that as soon as I leave the Sanctuary game cell to say Concord or towards Abernathy Farm etc get this game breaking weapon glitch.

 

Only thing haven't tried is using Mod Organizer for Fallout 4 (although I use it for Skyrim). Most people say NMM better for Fallout 4 anyway which is what I use. I don;t think this will make a difference - been using NMM for over a year and worked fine (unless latest version is the problem? But doubt that too). No I'm sure it's some stupid, hard to fathom thing, some setting not set or some irritating bug that either a patch or an update to Unofficial patch or maybe Fallout4.exe or maybe F4SE implementation. Or an animation issue - weapon lag used to be a problem for this game - it's probably Bethesda's fault.

 

Cheers.

[AWP3RATOR]

Well, considering you are experiencing this on a fresh install without any mods installed, on the latest game version - and on one else that I can find has reported this (I cannot recreated it) - it points to something with your system.  You're right, it's probably some silly setting.

 

When you re-ran the game cache verification and reinstalled - did you also happen to clean the files from you My Documents folder?  There are sever ini files there which do not get reinitialized, unless missing, when game cache is verified through Steam. (at least that's my experience).  This would be the only thing I can think of that would be the same, unless you manually removed them, across reinstalls.

[pmeloche]

Hello Everyone,

 

Sorry turns out I told a lie - did have one very crucial mod still installed lurking in the background that was the cause. As I say later was late at night, and got sloppy.

 

Figured it out/Fixed it myself. Feel like such an idiot for not figuring this out earlier given my long experience troubleshooting Bethesda games and mods etc.

 

It was the PipPAD mod which was the culprit and still installed I'm afraid, and I neglected to realise (sorry was late at night writing my OP). The really good news is that PipPAD can still be used bug free by going to the MCM Configuration settings and changing it's default item slot from #61 (fx) which is the default to something else for e.g. I change it to #51 (ring slot). Not sure about #41 - #49 haven't tested yet but likely they will do the trick too.

 

Hope this helps, spread the message around for anyone else experiencing this horrible, horrible, game breaking  bug.

 

PM