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

[pbmeloche]

Hello Nexus Forum 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

 

 

[pbmeloche]

Hello Everyone,

 

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 anyone else with this horrible, horrible bug.

 

PM