Jump to content


Photo

DynDoLod Error when starting


  • Please log in to reply
9 replies to this topic

#1 Mereinid

Mereinid

    Prisoner

  • Members
  • 12 posts

Posted 08 February 2018 - 12:01 AM

Hello all, I have an issue with DynDoLod Texgen64. I have getting an error

Fatal: Could not open registry key: \SOFTWARE\Bethesda\Skyrim\

I have tried to put the -sse in the command line, however, when I right click DynDoLOD.exe and the 64.exe version and select properties there is no command line for me to edit. I get no tab that gives me access to the Start In line.

I have the DyndoLOD Standalone version of the TechAngel85 STEP guide. 

 

I have dropped the DyDoLOD folder into my SkyrimSE and I still get the same entry, I have pulled all of the files out of the DynDoLOD folder and put them in the same directory, it still gives me the error. 

Is the standalone version, for some reason, not the one I need. Mod Organizer 2 recognizes it and I have a quick access link that I can 'RUN' if from the drop down window in MO. but I get same error on all of the .exe's for DynDoLOD.

 

 

Thank you all for your patience and time on this issue.

 

Regards,

Mereinid


  • 0

#2 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,377 posts

Posted 08 February 2018 - 05:42 AM

See ..\DynDOLOD\Docs\DynDOLOD-Shortcut.txt how to create a Windows shortcut to add command line parameters or how to add command line parameters MO executable drop downs.

 

Start the games launcher once, so the registry settings for the game are set or updated.

 

In addition pay attention to the installation instructions: From the DynDOLOD Standalone archive copy the content of the 'DynDOLOD' folder which contains the files DynDOLOD.exe, TexGen.exe, DynDOLOD_QuickStart.html and the sub folders 'Docs' and 'Edit Scripts' with all their content into a new 'DynDOLOD' folder outside of special OS folders like 'Programs Files' or 'Program Files (x86)', the SteamApps or game folders and Mod Organizers virtual file structure.


Edited by sheson, 08 February 2018 - 05:42 AM.

  • 0

#3 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 04:09 PM

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 
 
 
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

  • 0

#4 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,377 posts

Posted 14 February 2018 - 05:10 PM

Without the full log it is rather hard to guess all the other possible things that could go wrong. It seems the requirements to use DynDOLOD are not met.

There really should be no confusion whatsoever about the plugins that are part of a bug report in the docs folder.

I suggest to carefully read and follow the install instruction in the included manual and watch the embed/linked videos.
  • 0

#5 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 05:42 PM

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

  • 0

#6 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 14 February 2018 - 06:38 PM

@crazy_eYes

I suggest you continue this in just one thread, either here or the MO one but not both.

As stated in the other thread posting a log of what happens when you do not use MO is not going to be helpful in troubleshooting your problem since it is to do with both DynDoLOD and MO.



#7 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,377 posts

Posted 14 February 2018 - 07:06 PM

What is the version of MO2? What is the installation path of MO2?

What is the installation path of DynDOLOD? Test if DynDOLOD 2.36 beta is any different.

What happens when xEdit is started from MO2?


  • 0

#8 crazy_eYes

crazy_eYes

    Prisoner

  • Members
  • 6 posts

Posted 14 February 2018 - 08:17 PM

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.

  • 0

#9 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,377 posts

Posted 14 February 2018 - 08:34 PM

OK, installation paths etc all seems in order.

 

Fix or undo whatever it is that happened between last time xEdit worked and now. Could be 3rd party stuff, like antivirus.

 

Also reboot to clear up any hung file processes or other background things that can prevent access.

 

Check manually if the registry entry actually exists and is correct. Should be HKLM\Software\WOW6432Node\Bethseda Softworks\Skyrim Special Edition\Installed Path


Edited by sheson, 14 February 2018 - 08:34 PM.

  • 0

#10 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 14 February 2018 - 09:21 PM

In your MO2 settings do you have anything in the "Start in" field? If so remove it and try again.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users