Game In a Continuous State of Slow-Motion, HELP!

[Orotomo]

I'm having an issue while playing New Vegas. My game is in a continuous Slow Motion-like state. I have no idea what mod is doing it. It happens as soon as the game starts, and it's like the entirety of the game's physics was converted into molasses; it's unplayable. My game was just fine 3 days ago, I didn't notice any problem. But when I got back into it today, it was like this. I have no idea what changed.

 

Here's my load order:

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenal.esm

CaravanPack.esm

ClassicPack.esm

MercenaryPack.esm

TribalPack.esm

Project Nevada - Core.esm

Project Nevada - Extra Options.esm

Project Nevada - Cyberware.esp

Project Nevada - Equipment.esm

Project Nevada - Rebalance.esp

Fallout3.esm

Anchorage.esm

BrokenSteel.esm

PointLookout.esm

ThePitt.esm

Zeta.esm

TaleOfTwoWastelands.esm

Rivet City Realignment.esm

Kentbury Way.esm

TTWFixes.esm

AWorldOfPain(Preview).esm

AWorldOfPainFO3.esm

More Perks.esm

Bashed Patch, 0.esp

Flora Overhaul.esp

Vurt's WFO.esp

Strip Wall Billboards.esp

Ragdolls.esp

NukaCola-Ojo.esp

NukaCola-Ojo-TTW.esp

No more giant manhole covers.esp

EVE FNV - ALL DLC.esp

More Perks - EVE compatibility patch.esp

More Perks Patch.esp

More Perks 2.94b patch.esp

MetroCars.esp

JIP Improved Recipe Menu.esp

LootMenu.esp

Project Nevada - Rebalance Complete.esp

Project Nevada - Cyberware Additions.esp

Project Nevada - All DLC.esp

Project Nevada - TTW.esp

Project Nevada - EVE All DLC.esp

TTW_OutcastTrading.esp

TTW_SpeechChecks.esp

ttw_wildwasteland.esp

TTWOptions.esp

The Mod Configuration Menu.esp

AutoGates.esp

TTWStashPackDistribution.esp

unique_incinerators.esp

NPCOverhaulTTW.esp

AWOP FO3 - AWOP NV - EVE.esp

MergeyMerge.esp

Any help would be appreciated.

[dubiousintent]

If you really didn't make ANY changes to the game, then the cause is likely due to something external to the game.

 

First, try a "cold reboot" (power off, wait at least 15-30 seconds, and then power on again). Be sure you are not using "hibernation" when you power down. (This is a setting in your "power profile". Google it if this is a new term to you.) This will "flush out" anything in memory that may have "glitched".

 

Now, please see the 'Checklist' and 'Solutions to Performance problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. The 'Checklist' runs through things outside of the game that often affect it when they get updated automatically. The "Performance" section is unlikely to affect anything that didn't exist more than three days ago, but can't hurt either.

On a side note: you have a "Bashed Patch" (BP), but it is in the wrong position in your "load order". It belongs at the very end.

* If "MergeyMerge.esp" is a "final merged patch" produced with Mator's "Merged Plugin Standalone" (MPS) tool, you should not use both it and the BP together.

* If OTOH it is an "override" patch to the "Bashed Patch", then it needs to be placed after the BP at the bottom.

* If it is an '''xEdit'' merge patch, note: LOOT will recognize the name "TES5Merged.esp" and place it just above the Wrye "Bashed Patch" file if present.

 

I haven't played TTW as yet, but that "load order" looks suspiciously alphabetical to be sorted properly. Suggest you run LOOT first, then adjust the result as advised on the TTW site: FAQ and Support Forum.

 

-Dubious-

Edited April 29, 2017 by dubiousintent

[Orotomo]

Thanks man, in the process of trying these suggestions. I'm also reading the guide to using both a Merged Patch and a Bashed Patch at the same time. I'll post an update if anything fixes it.

 

EDIT: So, I deactivated every mod and tried out my game (I first just deactivated a few mods at a time, but then went all in) and my game is STILL doing this slow-motion thing. I'm going to reinstall it and try again.

Edited April 30, 2017 by Orotomo

[dubiousintent]

Consider if this problem is specific to the game, or if you are experiencing a "slow down" in general in other programs as well.

 

If the latter, two causes come to mind: "thrashing" and "malware".

 

"Thrashing" can come about because the disk is having to move the drive head back and forth across the disk a lot due to "file fragmentation". Try "defragmentation" of your hard drives if it's been awhile. It's built into Windows. (System updates can fragment and fill up a drive behind your back quite easily.) Don't forget to "empty the trash" first.

 

"Malware" is everything from "viruses" to "root kits". When you suspect you may be infected, use more than one tool (but each separately) to scan your system. Any one vendor may miss detecting a recently released piece of malware, but a broad range of tools are more likely to pick up any given infection. Most of the vendors have "online" web based scanners. Best is to boot from a "clean" floppy, CD, or flash drive to run the scan.

 

The last consideration is "failing hardware". No one wants to hear that, but it does happen. I regard it it as a last resort possibility.

 

-Dubious-

[Orotomo]

I've discovered that this issue is only with Fallout New Vegas. I can run Skyrim (and the SKSE), For Honor, Salt and Sanctuary, etc. Every other game does not have this problem. I've also learned that:

• Running the game through the default shortcut and .exe file does not give me this problem.
• Running the game through the nvse_loader.exe does not give me the problem either.
• I can run the game through Mod Organizer using the default New Vegas .exe file without this issue
• Running the game through Mod Organizer using the NVSE .exe file gives me this issue

This all holds true with all mods enabled, disabled, and with only some enabled. (Granted, running the game without Mod Organizer doesn't give me any mods to enable). Is it a common problem for NVSE and MO to have issues?

[dubiousintent]

There is apparently a history of issues with running NVSE through MO. The most common suggestion found when searching on those keywords is to be sure all the FNV and NVSE launch executables are configured to "Run as Administrator" in their file properties. But that will only get the game to start. Didn't find anything about "performance issues" once started.

 

I don't use MO, and you have narrowed it down to running NVSE under MO: so my recommendation would be to take this issue to their support forum. Most likely is that you missed something when configuring NVSE in the "Gears" menu.

 

Let me know what you find out and I'll add it to the "Troubleshooting" guide.

 

-Dubious-

Edited May 1, 2017 by dubiousintent

[Orotomo]

All right, I'll do that. Thanks, Dubious.

[Orotomo]

UPDATE: I fixed my problem. All I had to do was put all of my mods into Fallout Mod Manager instead of Mod Organizer. Other than that there was absolutely no problem.