Jump to content


Photo

MO 2.0.7 + F4SE (0.6.0) Crash at launch for Fallout 1.0.26.0

f4se fallout 4 mod organizer

  • Please log in to reply
4 replies to this topic

#1 Christopher_C

Christopher_C

    Prisoner

  • Members
  • 9 posts

Posted 28 October 2017 - 02:51 PM

Hello,

 

I have been doing my due diligence in searching Google for a RCA for this issue. I can launch F4SE_Launcher.exe and Fallout 4 comes up without an issue. It's just that I am a LONG time gamer with mods and MO 2.0.7 is my tool of choice. After the last update when I launch it from within MO right after is loads up the "Preparing VFS" the f4se_loader.exe cmd screen pops up with an error;

 

(hover mouse to view error)

Attached File  F4SE error.png   19.84KB   0 downloads

 

I have ensured that all of my mods that utilize F4SE are up to date. It has been a month since the CC patching and still not finding a resolution. I am tech guy that has been modding games going back to NWN and I have dug my way out of most of my issues. This one is slamming the door in my face before I even get into the game. It works outside of Mod Organizer and no launching within MO?!? Even if I strip out all the Mods and just try to launch a base game from MO with no mods in place. I have removed all prior installs of F4SE and done the verify cache with Steam... No good. I was trying to recover the older Fallout4.exe through the Steam console process without success  :crying:

 

Any bones you can throw my way? This error has come up in the past for others so thinking it might just be simple I overlooked something. Don't bother posting crap like rebuild my Windows 10 and install every damn file over again. I have been building my own machines and working real IT helpdesks back when Daggerfall  was cutting edge.  :cool:

 

Something with Mod Organizer is not playing nice with F4SE on my machine and it was looking fine even after the 1st CC patch came out.

 

Thank you for you time.  ::):

AF1QipPGSvkwxOBu8ovE_sK6N1nlvkMfQS_bdWhx

AF1QipPGSvkwxOBu8ovE_sK6N1nlvkMfQS_bdWhx


  • 0

#2 Christopher_C

Christopher_C

    Prisoner

  • Members
  • 9 posts

Posted 28 October 2017 - 03:24 PM

Hmmm this looks to have been a better fit in the Mod Organizer 2 forum.  :unsure:  my bad.


  • 0

#3 Greg

Greg

    High King

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,496 posts

Posted 28 October 2017 - 09:22 PM

Topic moved to Mod Organizer 2 support.



#4 Christopher_C

Christopher_C

    Prisoner

  • Members
  • 9 posts

Posted 30 October 2017 - 02:39 PM

I am still digging on this... Interesting I also get an error in FO4Edit when launched in MO2 with "could not find ini". Then in the msg "Fatal: Could not determine my documents folder."

 

Again both F4SE and FO4Edit launch outside of MO 2.0.7


  • 0

#5 Christopher_C

Christopher_C

    Prisoner

  • Members
  • 9 posts

Posted 30 October 2017 - 04:17 PM

[Fixed] I did not find my answer on any forum. I found that a fresh MO 2.0.7 profile was able to launch with F4SE 6.0 + no issues with F4Edit as it found whatever ini files it needed.

  1. Create new profile (do not copy the corrupted one)
  2. Copy over from the old profile your load order and plugin files; lockedorder.txt, modlist.txt, hide_plugins.txt, loadorder.txt, plugins.txt
  3. Depending on where you place your saves local or in the profile you will need to move them.

End game is I am up and running again without having to do much work. This one really sucked for lack of info on the web. Which is why I post how it got fixed. Don't be that guy that say "got it" and never spills the beans on his fix.

 

Hope his helps some other Mod Organizer user until Vortex get done. :clap:


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users