Jump to content


Photo

Issue With Apps Launched from Within MO2


  • Please log in to reply
7 replies to this topic

#1 DsevenO

DsevenO

    Prisoner

  • Members
  • 14 posts

Posted 28 January 2018 - 10:27 AM

Everything was working mostly well until recently. I wanted to be able to use Merge Plugins, so I had to install a "portable" version of MO2 in order to be able to use it. Everything seemed to be fine, but then seemingly out of nowhere every time I would launch MO2 and use an app like LOOT, the tiny lockout window would stay up after closing LOOT saying that the mergeplugins.exe was still running (even if I hadn't used it since launching MO2). 

 

Now I can't even launch LOOT. It's saying "failed to spawn Loot.exe...parameter is incorrect[87]". Not sure if this is related to the issue with Merge Plugins, but whatever the cause I can no longer use LOOT from within MO2. Any thoughts?


  • 0

#2 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 12,527 posts

Posted 28 January 2018 - 11:21 AM

Is MO2 installed outside the game folder? If it's not, it should no longer be installed within the game folder. Install it in Common or any other location outside of UAC control.



#3 DsevenO

DsevenO

    Prisoner

  • Members
  • 14 posts

Posted 28 January 2018 - 02:00 PM

Yep, it's installed outside the game folder. Actually, I used your SSE guide for setting up my game. I've since added to it, but your method of demarcating mod categories has been extremely helpful for keeping things organized. Thanks a lot!


  • 0

#4 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 02:48 PM

 
I get a Fatal: Could not open registry key: \SOFTWARE\Bethesda Softworks\Skyrim when running TextGen64 and DynDOLOD64 from MO which is all I use as I prefere to keep my install folder vanilla. There is already a similar post under DYNDOLOD support. I followed the suggestions and it still is not working. So I thought I should try posting it here to see if anyone has a similar issue or fix.
 
I have followed all the steps in the Forest of Dibella guide by LupusHegemonia up until installing and running TexGen and DynDOLOD for SSE. Adding -sse to the shortcut did not seem to help nor did giving the files admin. I tried the steam launcher and tried verifying files and that did not make a difference. I even looked around in my registry to find skyrim and only thing listed in Bethesda Softworks is bethesda.net even after veryfing. Is it reccomended I install envrionment mods related to DynDOLOD directly into my games folder manually for now as a work around? I understand windows 10 is also picky with running things from certain locations. I have all installed in a tools directory on a seperate partition along with other skyrim resources. Skyrim SE is on its own drive seperate drive from windows and the tools.
 
At one point I was able to launch TexGen or DynDOLOD without MO. It did recognize file paths from windows users plugins and Skyrim SE on its other drive. Plugins reported no data as the Skyrim SE install is vanilla and I get thats because its not reading what MO adds.
 
Thanks again 

  • 0

#5 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 14 February 2018 - 04:30 PM

@crazy_eYes Please post your logs, inside spoiler tags, so we can see what is happening.



#6 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 05:34 PM

Once trying to launch it without MO logs generated the following. Tools are installed on x:
 

  • 0

#7 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 14 February 2018 - 06:33 PM

No, I need to see the MO logs from when you call it.



#8 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 07:53 PM

Ok log file is huge and i'm not familiar with it. The entire log crashes my browser so here are any lines that include TexGenx64 to start.
 

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users