Running the game tries to launch another instance of mod organizer

[TheRedBaron56]

mo2 starts without issue. try to run the nvse, cmd runs FalloutNVLauncher.exe.

(couldn't copy the code for some reason) Then I get the window popup An instance of Mod Organizer is already running.

Tried to run New Vegas; same result. Tried Fallout Launcher; same result. Tried reinstalling mo2. Still didn't work. Tried downloading a new copy of the mo2 installer; installed using that. Still didn't work. Don't know why this is happening; ran the game fine yesterday and I haven't installed any new mods.

[poxy100]

I appear to be getting the same issue, were you able to find a solution?

[ParzivalWolfram]

I've had the same issue for about a month now, as well. NVSE does load correctly, but then relaunches the fake launcher. If you have the 4GB patch, that also loads NVSE, which seems to do the same thing in that situation as well. If you open MO2, then rename the fake launcher to something else, and rename the actual launcher properly, everything works again for that launch.

[ConvexTlc97]

I've had the same issue for about a month now, as well. NVSE does load correctly, but then relaunches the fake launcher. If you have the 4GB patch, that also loads NVSE, which seems to do the same thing in that situation as well. If you open MO2, then rename the fake launcher to something else, and rename the actual launcher properly, everything works again for that launch.

Not sure what you mean. What files are you renaming? I am having the same issue.

[ParzivalWolfram]

The MO2 install script renames the original launcher to _FalloutNVLauncher.exe. You have to swap this file back in as the actual launcher (remove the underscore) after launching MO2. Leaving the normal launcher as the current launcher place seems to work if you launch the NVSE EXE directly, but I haven't tested that super well.

On Wed, Mar 15, 2023 at 6:29 PM ConvexTlc97 @.***> wrote:

I've had the same issue for about a month now, as well. NVSE does load correctly, but then relaunches the fake launcher. If you have the 4GB patch, that also loads NVSE, which seems to do the same thing in that situation as well. If you open MO2, then rename the fake launcher to something else, and rename the actual launcher properly, everything works again for that launch.

Not sure what you mean. What files are you renaming? I am having the same issue.

— Reply to this email directly, view it on GitHub https://github.com/rockerbacon/modorganizer2-linux-installer/issues/454#issuecomment-1470977102, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHE6CQLU4TXWK4FMQLLFW63W4JGEFANCNFSM6AAAAAAU7TLGNU . You are receiving this because you commented.Message ID: @.*** com>

[poxy100]

okay so were somewhere forward. if its just a matter of adding a "_" to the exe file, would it be difficult to tweek MO or NVSE to just launch that _version instead of doing it manually every time? im kinda looking for a way I can use it in the decks default mode.

[poxy100]

I've been messing around with the exe files, if you rename the exe files back to original and add MO2's exe to steam, you can still run it in either mode, this gets rid of the loop, but then the game just won't run at all. the NVSE and fallout NV options wont do anything, the launcher however runs, but it thinks that the game isn't installed.

Im not an expert, but to me it just seems like there no simple fix here, either way it only goes half way...

I. Hate. Managers.

[MrRollton]

Looks like the cause of the issue is the same as in #387 . Try repeating the steps I provided there.

[rockerbacon]

Duplicate of #387