endomiel Posted April 17, 2020 Posted April 17, 2020 Hey all, I looked at the MO forum, but that place seems pretty quiet. I had a fresh Steam FO: NV install. That worked. Then I added NVSE, which worked as well. However, whenever I wanted to run either NVSE or regular NV through MO2, it crashed. I got the screen with all the info about the licenses (Havok, Bethesda, etc...) then it crashes to desktop. Running it outside of MO2 works fine. Is there a way around this? I really hope that I don't have to resort to Vortex to manage my mods... Thanks in advance!
dborg2 Posted April 17, 2020 Posted April 17, 2020 do you have any mods running? Did you patch the falloutNV.exe to 4GB?
endomiel Posted April 18, 2020 Author Posted April 18, 2020 I had no other mods running. None were installed. It was patched to 4 GB. It runs perfectly well OUTSIDE of MO2, but once I start it via MO2, it crashes.
dongding Posted April 18, 2020 Posted April 18, 2020 How does your load order in MO2 look like? I suspect that your MO2 load order is causing the problem.
endomiel Posted April 18, 2020 Author Posted April 18, 2020 There is none. There are no other mods. It's just the base game and the DLCs.
endomiel Posted April 18, 2020 Author Posted April 18, 2020 What would the correct order to sort them be? I haven't looked at it, tbh.
dongding Posted April 18, 2020 Posted April 18, 2020 FalloutNV DeadMoney HonestHearts OldWorldBlues LonesomeRoad GunRunnersArsenal
endomiel Posted April 18, 2020 Author Posted April 18, 2020 This is the load order I have. The crash still happens. It's definitely something with MO2, since launching the game outside of it, works. Is there any other info I could give?
endomiel Posted April 18, 2020 Author Posted April 18, 2020 Well, lo and behold! I changed the MO data folder to the same drive where I installed MO itself & NV and all of a sudden, it worked!
dborg2 Posted April 18, 2020 Posted April 18, 2020 1 hour ago, endomiel said: Well, lo and behold! I changed the MO data folder to the same drive where I installed MO itself & NV and all of a sudden, it worked! oh... I just realize what the issue might have been. Did you install Fallout New Vegas in the program files-folder?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.