crazy_eYes

What is the version of MO2? 2.1.1 What is the installation path of MO2? X:\Storage\Game Resources\Skyrim SE\Mods\Mod Organizer What is the installation path of DynDOLOD? X:\Storage\Game Resources\Skyrim SE\Tools\DYNLODODSSE\Dyndolod Test if DynDOLOD 2.36 beta is any different. Ok. Same error. What happens when xEdit is started from MO2? Thats odd. It stopped working but was fine yesterday. xEdit has been installed on X:\Storage\Game Resources\Skyrim SE\Tools\SSEEdit\SSEEdit.exe it was working until I just tested it. @GrantSP Thanks for help I was a bit on the fence where to post. Perhaps a tad over my head here. I hope any of this was useful.

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.

Once trying to launch it without MO logs generated the following.

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

Hello and thanks for all the work put into this as its always a game changer. I am still getting the same fatal error after using the SSE launcher and verifying through steam and have followed your steps and suggestions. I made a post here on step in MO support at https://forum.step-project.com/topic/13130-issue-with-apps-launched-from-within-mo2/ I tried to take things a step further by experimienting with adding my DynDOLOD directory contents in through MO overwrite to see what would happen. After activing the files in MO I no longer get the fatal error. MO reports process completion but nothing happens TexGen does not pop up. However I noticed the six optional ESP's available now Overwrite.esl, esm, esp, RNAM.esl, RNAM.esm, RNAM.esp. Is there another guide to follow explaining if playing with these files will help? Otherwise I suppose I will have to install the related files manually into my vanilla directory in order to get the tools to work. Then remove and paste into Overwrite. Or I could wait for updates and fixes. I suppose I should mention I am aware Vortex is on the way so MO support is what it is right now. Thanks again

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