Waiting button won't work?

[TheGlock]

Hello,

 

I'm playing Fallout: New Vegas for the first time with the Project Nevada mod as the main core. The problem is, when I hit the Waiting Button (T) in game, it doesn't do anything. Changing the keybind doesn't do anything either.

Now I can only sleep to speed up time, and it's getting really annoying that I have find a bed in the middle of a radiation storm. Does anyone know if the mods I'm using are causing this or conflicting?

 

Here's my FOMM load order:

• FalloutNV.esm
• TribalPack.esm
• MercenaryPack.esm
• ClassicPack.esm
• CaravanPack.esm
• DeadMoney.esm
• HonestHearts.esm
• OldWorldBlues.esm
• LonesomeRoad.esm
• GunRunnersArsenal.esm
• Project Nevada - Extra Options.esm
• NevadaSkies.esm
• YUP - Base Game + All DLC.esm
• Project Nevada - Core.esm
• Project Nevada - Cyberware.esp
• Project Nevada - Equipment.esm
• Project Nevada - Rebalance.esp
• WMR.esm
• Better Game Performance.esp
• EVE FNV - ALL DLC.esp
• YUP - NPC Fixes (Base Game + All DLC).esp
• Project Nevada - Rebalance Complete.esp
• Project Nevada - Cyberware Additions.esp
• Project Nevada - EVE All DLC.esp
• populatedcasino.esp
• ToggleAim.esp
• LFox Bottle That Water.esp
• DarNifiedUINV.esp
• WeaponModsExpanded.esp
• WMX-DLCMerged.esp
• WMX-POPMerged.esp
• WMX-EVE-AllDLCMerged.esp
• Project Nevada - WMX.esp
• WMR - WMX Edition.esp
• NevadaSkies - Ultimate DLC Edition.esp
• NevadaSkies - Brighter Nights.esp

 

[dubiousintent]

Just guessing, but as the "Wait" button is part of the UI and I see you have DarnifiedUI as well as Project Nevada installed, this may be the result of the Install Order. See this post.

 

-Dubious-

[TheGlock]

I tired uninstalling and reinstalling PN and DarnUI in different orders, but that didn't fix it.

 

The problem is that I don't know what the ideal load order for these mods are and I don't want to spend a lot of time randomly uninstalling and reinstalling everything to get the right configuration. Is there a guide that tells you how mods should be installed first to last?

Edited April 26, 2016 by The Glock

[dubiousintent]

Aren't you using MCM and UIO? You should. MCM is needed to change the hotkey bindings for PN and other mods to avoid conflicts. UIO is needed to get different mod menus to work together.

 

With Darn and MCM there is an XML conflict, which I addressed here.

 

As an install guide I recommend either the "Fear and Loathing" STEP Guide for FNV or "TESCOSI" (which is written for Oblivion but covers the basics behind all Bethesda games install and load orders in depth). The STEP Guide is focused on using the Mod Organizer management tool but that is not required.

 

The point of install order is less about specific mods and more about which sorts of mods go in which order because they may overwrite each other. For that I have found TESCOSI to give a better understanding.

 

-Dubious-

[TheGlock]

So I tried all the suggestions you brought up dubiousintent, and so far nothing has brought back the ability to wait. I've even uninstalled and reinstalled all the mods to the best order that I can figure out, but no luck so far.

 

I problem is that I don't know what's causing the conflict and when it's happening. Is there a log I can check during gameplay that tells me if there are errors?

[dubiousintent]

No such general error log that I am aware of. NVSE does have a log in the game folder (..\common\Fallout New Vegas"), as do MCM and other specific mods. Search on the ".log" extension.

 

I'm afraid you are down to having to isolate which mod is causing the conflict. I suggest you start by uninstalling (not just disabling) "Nevada Skies", simply because it has been the source of other problems in the past.

 

If that isn't the solution, you are at the point of "time versus effort" return on investment. I would uninstall everything, rename/delete the INI files in "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder, "verify game files", use the vanilla game launcher and test basic functionality (including "wait") is there, then start installing again and test each mod as you go. Tedious, but the only sure-fire way.

 

One more thing. If you installed to the default Steam location of "C:\Program Files" I suggest you read the "Installing Games on Windows Vista+" article in my sig and move FNV elsewhere. That clears up many mystery problems.

 

-Dubious-

Edited April 29, 2016 by dubiousintent