Fallout New Vegas Weird Sprinting Glitch

[RobinHood2005]

Hey, I have a small issue.

 

In my Fallout New Vegas game, I sometimes get this glitch while sprinting which causes my character to sprint infinitely without stopping no matter what, or consuming AP. When I get this glitch, I often cannot do anything to stop my character from sprinting and am unable to view my Pip Boy or access the menu by pressing Escape. The glitch usually stops after about 15-20 seconds, however, but is very annoying.

 

I use the following mods:

 

0 0 FalloutNV.esm

1 1 DeadMoney.esm

2 2 HonestHearts.esm

3 3 OldWorldBlues.esm

4 4 LonesomeRoad.esm

5 5 GunRunnersArsenal.esm

6 6 ClassicPack.esm

7 7 MercenaryPack.esm

8 8 TribalPack.esm

9 9 CaravanPack.esm

10 a YUP - Base Game + All DLC.esm

11 b Interior Lighting Overhaul - Core.esm

12 c ELECTRO-CITY - CompletedWorkorders.esm

13 d AWorldOfPain(Preview).esm

14 e ELECTRO-CITY - Highways and Byways.esm

15 f NVStripOpen.esm

16 10 AWOPDeadMoney.esm

17 11 Interior Lighting Overhaul - L38PS.esm

18 12 Project Nevada - Core.esm

19 13 Project Nevada - Equipment.esm

20 14 More Perks.esm

21 15 Project Nevada - Rebalance.esp

22 16 Project Nevada - Cyberware.esp

23 17 NevadaSkies.esm

24 18 SolidProject.esm

25 19 Weapons.of.the.New.Millenia.esm

26 1a SomeguySeries.esm

27 1b YUP - NPC Fixes (Base Game + All DLC).esp

28 1c Real Recoil.esp

29 1d Sit Anywhere.esp

30 1e The Mod Configuration Menu.esp

31 1f The Weapon Mod Menu.esp

32 20 Vurt's WFO.esp

33 21 EVE FNV - ALL DLC.esp

34 22 WeaponModsExpanded.esp

35 23 IMPACT.esp

36 24 Project Nevada - IMPACT.esp

37 25 dD - Enhanced Blood Main NV.esp

38 26 WMX-ArenovalisTextures.esp

39 27 More Perks Update.esp

40 28 WMX-DLCMerged.esp

41 29 CNR_Beta.esp

42 2a StripOpenMain.esp

43 2b FNV Realistic Wasteland Lighting - All DLC.esp

44 2c AWOPDeadMoneyVendorPatch.esp

45 2d ADAM Complete.esp

46 2e ADAM - MERGE.esp

47 2f MojaveSandyDesert.esp

48 30 NewVegasBounties.esp

49 31 NewVegasBountiesII.esp

50 32 1nivVSLArmors.esp

51 33 1nivPNSLPatch.esp

52 34 ADAM - Trooper Gloves.esp

53 35 AWOP Interim Fixes.esp

54 36 WMX-EVE-AllDLCMerged.esp

55 37 AWOP-WMX-EVE AllDLCMerged.esp

56 38 WMX-ModernWeapons.esp

57 39 B42Inertia.esp

58 3a Boacombat2glove.esp

59 3b NukaCola-Ojo.esp

60 3c CAGE 1.9.3.2.esp

61 3d DK Caucasians.esp

62 3e FOVSlider.esp

63 3f boa ncrpahelmet.esp

64 40 ILO - Nevada Skies Patch.esp

65 41 Readius_NV.esp

66 42 NoBackpack_CyberDog.esp

67 43 Interior Lighting Overhaul - Ultimate Edition.esp

68 44 ILO - A World of Pain.esp

69 45 NevadaSkies - Ultimate DLC Edition.esp

[dubiousintent]

That's a twist. Usually people complain about not getting to sprint at all.

Either way, this is usually a "key binding" problem. From Gribbleshnitbit8, one of the PN and NVSE authors:

Two things can happen. Sometimes the sprint scripts crash. The solution is to turn the feature off, save and exit the game, then reload and restart it. This clears all instances out of memory, and then restarts the managing quest, usually fixing the problem.

The other issue is that sometimes it remaps or even completely unbinds the walk/run key. So check in your control settings to make sure that walk/run is bound to whatever key you had it set to. It's a rare bug, but does happen. If you're wondering why in the world it unbinds it, it's due to the way the sprint feature works, otherwise you'd actually wind up just walking.

Please see the 'Issue: How to determine what keystrokes are being passed' entry under the 'Solutions to Control problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" article. That will let you know if you are actually sending the "left" <Shift> key as intended. (Yes, the left and right <Shift> keys send different scan codes and can be distinguished between. I don't recall which PN is expecting, but that is a possibility.)

That same "Solutions to Control problems" section has some other things you should check.

Please see the wiki "HUD-UI-Menu issues" article. The "install order" of your HUD-UI-Menu" mods can make a difference. In particular you need to account for the older version of MCM included with PN, and the separate, later version you have installed.

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

If all else fails, I have seen some reports of other issues between PN and "Solid Project". You might check SP's comments to see if anyone else has reported any issue with "sprinting".

-Dubious-

[RobinHood2005]

That's a twist. Usually people complain about not getting to sprint at all.

 

Either way, this is usually a "key binding" problem. From Gribbleshnitbit8, one of the PN and NVSE authors:

 

Two things can happen. Sometimes the sprint scripts crash. The solution is to turn the feature off, save and exit the game, then reload and restart it. This clears all instances out of memory, and then restarts the managing quest, usually fixing the problem.

 

The other issue is that sometimes it remaps or even completely unbinds the walk/run key. So check in your control settings to make sure that walk/run is bound to whatever key you had it set to. It's a rare bug, but does happen. If you're wondering why in the world it unbinds it, it's due to the way the sprint feature works, otherwise you'd actually wind up just walking.

Please see the 'Issue: How to determine what keystrokes are being passed' entry under the 'Solutions to Control problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" article. That will let you know if you are actually sending the "left" <Shift> key as intended. (Yes, the left and right <Shift> keys send different scan codes and can be distinguished between. I don't recall which PN is expecting, but that is a possibility.)

 

That same "Solutions to Control problems" section has some other things you should check.

 

Please see the wiki "HUD-UI-Menu issues" article. The "install order" of your HUD-UI-Menu" mods can make a difference. In particular you need to account for the older version of MCM included with PN, and the separate, later version you have installed.

 

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

 

If all else fails, I have seen some reports of other issues between PN and "Solid Project". You might check SP's comments to see if anyone else has reported any issue with "sprinting".

 

-Dubious-

Thank you for your reply. I haven't experience this glitch since writing this post. If anything else happens, I'll mess around with the sprint mods/features that I have installed.