New Vegas crashes when starting with MO

[Thiero]

I am running a completely vanilla game, and whenever I try to start new vegas using MO it crashes after the first logo screen. The game does not crash when running from steam, and I can bring up the launcher using MO and change options but once I click play I go through the same issue.

[Thiero]

Reinstalled MO, and it seems to work again... hopefully will continue to do so.

[Questdog]

I am having the same problem.  If I try to launch with the FNV4GB or NVSE the game hangs at the Bethesda logo.  If I try to launch with falloutnv.exe it crashes.  It does not matter whether I have any mods enabled or not.

 

I played earlier in the day with no issues and now I can't play.

 

I tried the blacklist.txt file and no change in behavior.  I am running win7 ultimate 64-bit.

 

I can launch the game from steam and I can launch Skyrim and Fallout 3 with no problems from MO, but not New Vegas.

P.S. I haven't played Skyrim for a while and the MO version for it is still 1.2.14.  Fallout 3 uses 1.2.18, though it is not a steam game on my system.

 

Verified game cache, etc., etc....

Edited February 27, 2015 by Questdog

[GrantSP]

Both of you will need to provide some more details, but going from you have said, something must have updated on your systems and perhaps a fresh reboot might install those updates and fix these issues.

 

I can't believe that I am the only lucky user that just never sees these problems that are mentioned.

Check your settings for MO and FNV.

[Questdog]

Both of you will need to provide some more details, but going from you have said, something must have updated on your systems and perhaps a fresh reboot might install those updates and fix these issues.

 

I can't believe that I am the only lucky user that just never sees these problems that are mentioned.

Check your settings for MO and FNV.

What details do you want?

 

The only change was that I installed the new Nvidia driver and I already uninstalled that to see if it was the problem, but no dice.

 

P.S.  1.3 beta seems to work with the NVSE launcher, though it crashes when trying to launch with fnv4gb.exe

Edited February 27, 2015 by Questdog

[Thiero]

Both of you will need to provide some more details, but going from you have said, something must have updated on your systems and perhaps a fresh reboot might install those updates and fix these issues.

 

I can't believe that I am the only lucky user that just never sees these problems that are mentioned.

Check your settings for MO and FNV.

I'm honestly at a loss as to what other details I can provide. I know that steam recently updated, but I'm not sure that would be an issue.

[GrantSP]

@Thiero

Try that blacklist fix.

@Questdog

Since nothing inside you modded game or MO has changed I'm not sure how MO is the problem.

 

My setup has 1.2.18 for all games and after reading your initial posts, I played FNV for 15min with no issues.

Steam is updated and I usually play offline so you could try that.

Edited February 27, 2015 by GrantSP

[Questdog]

I tried offline.

 

I'm not saying it is MO's fault, but I'm saying it only happens in MO.  I can play from steam launch and 1.3beta (w/o fnv4GB.exe).

[Thiero]

@Thiero

Try that blacklist fix.

@Questdog

Since nothing inside you modded game or MO has changed I'm not sure how MO is the problem.

 

My setup has 1.2.18 for all games and after reading your initial posts, I played FNV for 15min with no issues.

Steam is updated and I usually play offline so you could try that.

What do you mean by blacklist fix?

[Questdog]

I re-installed MO 1.2.18 over my current installation and there was no change; still could not play.

 

I made a completely new MO 1.2.18 installation and copied my mod folder/profiles/etc. from the old installation and still could not play with mods activated or not.

 

I made a completely new 1.2.18 installation and tried to play with no mods installed yet and it worked.  Downloaded a mod and activated it and it still worked, so now I am re-downloading all 8,237 mods I have acquired over the years.  What fun!

 

P.S. The mod total reported may be a slight exaggeration.

Edited February 27, 2015 by Questdog

[GrantSP]

If you still have that old non-working installation, can you zip up all the ini files that are in it and post them here? I'd like to see what is in them as it is very strange to have the issue you describe continue with a new install over them.

 

So I would like all the files from the current profile that you were trying and the logs folder and your ModOrganizer.ini if that's not too much hassle.

 

With your downloaded mods. Did you copy over the *.meta files into your new installation or just the actual archives? Any issue with those mods could be related to some incorrect setting in those *.meta files that MO generates for each file. Not saying that is the case but copying just the archives into your downloads folder is exactly the same as downloading them from the net, except it is less time-consuming.

[Questdog]

 I will do as you have asked when I get some time.

 

I don't save the archived files because of disk space, so all I have is the mod folder with the meta files.  But the issue happened even if I de-activated every mod.

Edited February 28, 2015 by Questdog