Jump to content
  • 0

DynDOLOD not starting at all


Sayoregg
 Share

Question

I am using MO2. I installed DynDOLOD in a separate directory than my game and not in program files or anything. In MO2 I added -sse to the arguments for both programs (I'm using the x64 versions of them if that's relevant). Without the arguments the programs give a totally different error so I'm guessing that it isn't the issue. When I do try to run the programs (Both DynDOLOD and texgen), I'm getting this error log. Gonna use TexGen's as an example.
               [00:00:00.063]    TexGen based on xEdit x64 (DAB7081D) starting session 2021-04-15 10:01:59
               [00:00:00.073]    Game Mode: SSE
               [00:00:00.078]    Game Name: Skyrim Special Edition
               [00:00:00.084]    Using Skyrim Special Edition Data Path: C:\Program Files(x86)\Steam\steamapps\common\Skyrim Special Edition\Data\
               [00:00:00.089]    Using Backup Path: C:\Program Files(x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Backups\
               [00:00:00.095]    Using Scripts Path: D:\Programs (D)\DyndoLOD\Edit Scripts\
               [00:00:00.101]    Using Cache Path: D:\Programs (D)\DyndoLOD\Edit Scripts\DynDOLOD\cache\
               [00:00:00.107]    Using Temp Path: C:\Users\Sayor\AppData\Local\Temp\SSEEdit\
               [00:00:00.114]    Using ini: C:\Users\Sayor\Documents\My Games\Skyrim Special Edition\Skyrim.ini
               [00:00:00.124]    Using save path: C:\Users\Sayor\Documents\My Games\Skyrim Special Edition\Saves\
               [00:00:00.132]    Using plugin list: C:\Users\Sayor\AppData\Local\Skyrim Special Edition\Plugins.txt
               [00:00:00.140]    Using settings file: C:\Users\Sayor\AppData\Local\Skyrim Special Edition\DynDOLOD_settings.ini
               [00:00:00.157]    Using language: English
               [00:00:00.167]    Using general string encoding: 1252  (ANSI - Latin I)
               [00:00:00.176]    Using translatable string encoding: 1252  (ANSI - Latin I)
               [00:00:00.192]    Using VMAD string encoding: 65001 (UTF-8)
               [00:00:00.202]    Loading active plugin list: C:\Users\Sayor\AppData\Local\Skyrim Special Edition\Plugins.txt
               [00:00:00.218]    Fatal: Error loading plugin list: <EDirectoryNotFoundException: The specified path was not found>

I have checked the path it is trying to load "Plugins.txt" from and there wasn't any file called like that there, only a "DynDOLOD_settings.ini". I asked one guy in a discord server for help because I knew he used DynDOLOD. His Plugins.txt file is completely empty, and DynDOLOD worked for him, so I created an empty Plugins.txt file there, yet the programs still give the same error.

Link to comment
Share on other sites

Recommended Posts

  • 0

C:\Users\[username]\AppData\Local\Skyrim Special Edition\Plugins.txt is the standard location the game stores/expects the plugin list.

When starting programs from MO2, MO2  substitutes that file with the version from its profile folder.

If the OS tells a program that a file does not exist, it either does not exist or access is prevented by the OS, UAC, antivir etc.

Best not to install the game (or any modding tools for that matter) into special Windows folder like Program Files x86

Link to comment
Share on other sites

  • 0
4 minutes ago, sheson said:

C:\Users\[username]\AppData\Local\Skyrim Special Edition\Plugins.txt is the standard location the game stores/expects the plugin list.

When starting programs from MO2, MO2  substitutes that file with the version from its profile folder.

If the OS tells a program that a file does not exist, it either does not exist or access is prevented by the OS, UAC, antivir etc.

Best not to install the game (or any modding tools for that matter) into special Windows folder like Program Files x86

DynDOLOD itself is in my D drive, so not a special folder. and The location of Skyrim is where the default steam folder is. Do you suggest to move my steam installation folder to the D drive as well?

Also, the programs give the same error when trying to start them manullay (Through shortcuts with an -sse argument added).

Link to comment
Share on other sites

  • 0

If a file does not exist or if the OS, UAC, antivir blocks programs from access, it does not matter how the program is started.

Note that we do not know if MO2 is being blocked from virtually putting the plugins.txt there or if DynDOLOD is prevented from accessing it.

You should have similar issues with other tools trying to use that file to get the plugin list. Like when using xEdit for cleaning for example.

Basically every modding guide starts with explanations and instructions about not and installing the game into Program Files x86 and how to move it. This most likely is not directly affecting the plugins.txt file not existing where it should or programs being blocked from accessing it.

Link to comment
Share on other sites

  • 0

I searched up online how to move my Steam library and am doing that right now, to a new folder in the D drive.
So what do you suggest doing to resolve the issue? I never had issues with using MO2 or modding tools before. Nor do I have any antivirus that would block it. I also always run MO2 as administrator, and have tried running the shortcuts manually as administaror as well. Neither worked, still getting the same error.

Link to comment
Share on other sites

  • 0

I can not really help much with OS setup, its native or 3rd party programs, but you might want to check the built-in Microsoft Defender Antivirus and maybe add an exception or something.

MO2 adds an exception to it for itself. Check the MO2 log. It should show everything its virtual file system does, including redirecting plugins.txt and all accesses to it.

Link to comment
Share on other sites

  • 0
12 minutes ago, sheson said:

I can not really help much with OS setup, its native or 3rd party programs, but you might want to check the built-in Microsoft Defender Antivirus and maybe add an exception or something.

MO2 adds an exception to it for itself. Check the MO2 log. It should show everything its virtual file system does, including redirecting plugins.txt and all accesses to it.

I finished transfering my steam library to the D drive, it is now "D:\SteamLibrary\steamapps\common". Still getting the same error.
I found the logs from yesterday. Only places where DynDOLOD is mentioned in here (Several times, same text, probably from each time I tried to run it.

"38:07.861 inithooks called mod_organizer_instance in process D:\Programs (D)\DyndoLOD\TexGenx64.exe:4640 (log level 1, dump type 1, dump path C:/Users/Sayor/AppData/Local/ModOrganizer/SkyrimSE/crashDumps)"

Checked that dump path, it only has a "SkyrimSE.exe-16012.dmp". Empty when I open it with notepad, and last modified two months ago.

Link to comment
Share on other sites

  • 0

As mentioned "This most likely is not directly affecting the plugins.txt file not existing where it should or programs being blocked from accessing it."

xEdit/xLODGen/DynDOLOD use standard OS function to access files. There is nothing a program can do if a file does not exist or the OS, UAC, antivir or anything else prevents access through the standard OS functions. The program can only relay the error message returned from the OS function so the user might be able to fix the cause of the problem.

Link to comment
Share on other sites

  • 0
11 minutes ago, sheson said:

The OS, UAC, antivir or some other 3rd party crapware is blocking access. Find out what it is that is blocking access and change it so that access is allowed.

Disabled UAC, doesn't work. Added them as an exception to windows defender/ antivirus, doesnt work. I dont have any 3rd party antiviruses or something like that. Is there any more concrete way to find out what is blocking acess to it?

Link to comment
Share on other sites

  • 0

Copy the loadorder.txt and plugins.txt from teh MO2 profile folder into that standard folder. If tools are started from MO2 it will still redirect to the files in its profile folder, but at least the this ensures that original paths and files exist even before that.

Other than that, I can't help much other than the already given pointers. See what happens when you clean and error check with xEdit, which should be done before generating LOD anyways.

Link to comment
Share on other sites

  • 0
3 minutes ago, sheson said:

Copy the loadorder.txt and plugins.txt from teh MO2 profile folder into that standard folder. If tools are started from MO2 it will still redirect to the files in its profile folder, but at least the this ensures that original paths and files exist even before that.

Other than that, I can't help much other than the already given pointers. See what happens when you clean and error check with xEdit, which should be done before generating LOD anyways.

Copied them, no luck.
Never used xEdit in my life and was hoping not to. But It seems I have no choice, gonna do that now.

Link to comment
Share on other sites

  • 0

I moved this to Mod Organizer 2 Support since it is not a DynDOLOD issue.

A few things to check:

  • Verify you've installed Mod Organizer in its own folder away from UAC controlled folders (C:\Program Files and C:\Program Files (x86) and that is not installed in anywhere in the Steam, SteamLibrary or Skyrim Special Edition folders. The virtual file system does not work correctly and may be blocked by Windows if it's installed in these folders. I suggest installing Mod Organizer in a folder like D:\Mod Organizer or D:\Tools\Mod Organizer.
  • If the above does not solve the issue, open File Explorer and browse to the Mod Organizer folder. Right click on ModOrganizer.exe and click Properties. If you see an Unblock button or a checkbox with "Unblock", click it and click OK. If you see the Unblock button or checkbox, you should repeat this for every *.exe and *.dll file in the Mod Organizer folder and subfolders. Unfortunately, Windows 10 can be a royal pain about blocking the virtual file system if these files are blocked.
  • If you are still having issues, open Windows Defender (or whatever antivirus software you are using) and add a rule to exclude ModOrganizer.exe and the entire Mod Organizer folder.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.