DynDOLOD 3.00 Alpha 182

[sheson]

1 hour ago, iReptar said:

Hello!

I just finished up the SkyrimSE v2.3 STEP Guide and it was absolutely fantastic, extremely easy to follow. However, after I completed DynDOLOD, I received the following errors. I put the Textures do not match error message into pastebin because of how much there was!

Textures Do Not Match:

https://pastebin.com/nHDmQce9

This is for Files Not Found:

Warning: File not found textures\effects\glowsoft01_enbl.dds. Used by Meshes\clutter\blackreach\blackreachbush01.nif Skyrim.esm BlackreachBush01 [TREE:000CE101]
Warning: File not found textures\effects\glowsoft01_enbl.dds. Used by Meshes\clutter\blackreach\blackreachbush02.nif Skyrim.esm BlackreachBush02 [TREE:000CE102]

Currently trying to understand where I went wrong! Any assistance that can be provided to resolve these errors would be greatly appreciated.

Read this first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.

If you follow a third party guide like STEP, then you should ask in their part of this forum if the warning messages are expected as explained in the Summary page that opens or if they mean something went wrong.

Each page that lists similar messages either have detailed explanations on top or a link to them

Read all of https://dyndolod.info/Messages/Textures-Do-Not-Match
There are outdated LOD models in the load order or full models have been replaced without providing updated LOD models.
If and only if there are obvious differences of the textures between full models and LOD models, the log messages can aid in quickly finding the reason.

A mod replaced the vanilla roads meshes so they are using different textures while another mods 3rd party LOD models were made for the vanilla version of the roads. If you do not notice any texture discrepancies in Blackreach, the automatic LOD texture replacements worked out OK.

Read all of https://dyndolod.info/Messages/File-Not-Found-Textures
This can happen if a mod is installed that requires the textures from another mod that is not installed. Verify the requirements of the reported models, plugins and their related mods.

[z929669]

5 hours ago, sheson said:

Read this first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.

If you follow a third party guide like STEP, then you should ask in their part of this forum if the warning messages are expected as explained in the Summary page that opens or if they mean something went wrong.

Each page that lists similar messages either have detailed explanations on top or a link to them

Read all of https://dyndolod.info/Messages/Textures-Do-Not-Match
There are outdated LOD models in the load order or full models have been replaced without providing updated LOD models.
If and only if there are obvious differences of the textures between full models and LOD models, the log messages can aid in quickly finding the reason.

A mod replaced the vanilla roads meshes so they are using different textures while another mods 3rd party LOD models were made for the vanilla version of the roads. If you do not notice any texture discrepancies in Blackreach, the automatic LOD texture replacements worked out OK.

Read all of https://dyndolod.info/Messages/File-Not-Found-Textures
This can happen if a mod is installed that requires the textures from another mod that is not installed. Verify the requirements of the reported models, plugins and their related mods.

A mod or mod option was probably installed that is not in our guide, as I don't have this texture in my instance. Nor do I have any DynDOLOD Summary generated (so no such errors with the mods in our guide).

[iReptar]

1 hour ago, z929669 said:

A mod or mod option was probably installed that is not in our guide, as I don't have this texture in my instance. Nor do I have any DynDOLOD Summary generated (so no such errors with the mods in our guide).

 

7 hours ago, sheson said:

Read this first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.

If you follow a third party guide like STEP, then you should ask in their part of this forum if the warning messages are expected as explained in the Summary page that opens or if they mean something went wrong.

Each page that lists similar messages either have detailed explanations on top or a link to them

Read all of https://dyndolod.info/Messages/Textures-Do-Not-Match
There are outdated LOD models in the load order or full models have been replaced without providing updated LOD models.
If and only if there are obvious differences of the textures between full models and LOD models, the log messages can aid in quickly finding the reason.

A mod replaced the vanilla roads meshes so they are using different textures while another mods 3rd party LOD models were made for the vanilla version of the roads. If you do not notice any texture discrepancies in Blackreach, the automatic LOD texture replacements worked out OK.

Read all of https://dyndolod.info/Messages/File-Not-Found-Textures
This can happen if a mod is installed that requires the textures from another mod that is not installed. Verify the requirements of the reported models, plugins and their related mods.

 

Thank you both so very much! I will go ahead and see if I can determine where I went wrong with one of the FOMOD installers. Is there a way to determine for the "textures do not match" error, which mod has those files associated with it?

[sheson]

10 minutes ago, iReptar said:

Thank you both so very much! I will go ahead and see if I can determine where I went wrong with one of the FOMOD installers. Is there a way to determine for the "textures do not match" error, which mod has those files associated with it?

Use the MO2 right window Data tab to find out the winning mod for specific files like the mentioned NIF comes from. Do not forget to enable archive parsing in Tools, Settings, Workarounds tab.

[iReptar]

4 minutes ago, sheson said:

Use the MO2 right window Data tab to find out the winning mod for specific files like the mentioned NIF comes from. Do not forget to enable archive parsing in Tools, Settings, Workarounds tab.

So, I did some digging in my files and I found where those files located! I will need to go back and reinstall "Cathedral Landscapes" and "Skyrim Realistic Overhaul" it looks like.

https://ibb.co/QP9hyDQ
https://ibb.co/3RgZK0R

I will refer back to the STEP Guide support forums now since it seems to be an issue with how I followed the guide and not really anything to do with DynDOLOD. Thank you so very much for your assistance.

[Earl500]

Hello. I don't normally like asking for help, but I have been banging my head against TextGen for the past two days and had very little success for all my troubles. My original problem was simply that TextGen kept trying to find the Steam version of the game, whereas my version is the GOG version (aka, a problem with the Windows Registry). I eventually had to use -i,-m,-p,-d arguments in order to even get TextGen to find the correct folders and files ("-sse" did not work). My joy was short-lived, however, as I was immediately confronted with a "Skyrim.ini was not found" error message upon starting TextGen, even though it is a fact that the correct .ini file is present at the exact path which I had specified in the command line arguments. The exact error message which I receive is this:
https://imgur.com/a/biEAMAK

I have the latest GOG version of Skyrim AE, freshly installed on a new rig.

Exhaustive list of what I have so far tried:
disabling anti-virus
eliminating "special" characters including any and all spaces) from only the command line arguments, only the actual folder names, or both.
starting the launcher to generate a new Skyrim.ini file
using "-sse" (minus the "") in the argument line

Does anyone know/think there is any workable solution to this problem? I am more or less at my wits end here.

[sheson]

6 hours ago, Earl500 said:

Hello. I don't normally like asking for help, but I have been banging my head against TextGen for the past two days and had very little success for all my troubles. My original problem was simply that TextGen kept trying to find the Steam version of the game, whereas my version is the GOG version (aka, a problem with the Windows Registry). I eventually had to use -i,-m,-p,-d arguments in order to even get TextGen to find the correct folders and files ("-sse" did not work). My joy was short-lived, however, as I was immediately confronted with a "Skyrim.ini was not found" error message upon starting TextGen, even though it is a fact that the correct .ini file is present at the exact path which I had specified in the command line arguments. The exact error message which I receive is this:
https://imgur.com/a/biEAMAK

I have the latest GOG version of Skyrim AE, freshly installed on a new rig.

Exhaustive list of what I have so far tried:
disabling anti-virus
eliminating "special" characters including any and all spaces) from only the command line arguments, only the actual folder names, or both.
starting the launcher to generate a new Skyrim.ini file
using "-sse" (minus the "") in the argument line

Does anyone know/think there is any workable solution to this problem? I am more or less at my wits end here.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log to upload when making posts.

Copy the text of the message to the clipboard and post the text of the message instead of a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text
The message tells you what the problem is. The path is wrong, there is no such path/filename. xEdit asks the OS if the file exists at the shown path and the OS reports that it does not. No information about the actual path has been provided.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages
Click on the link Click on this link for additional explanations and help for this message, which opens https://dyndolod.info/Messages/INI-Files.
The screenshot shows the game mode is SSE, so -sse seems to be working as expected.
Alternatively set the path to the INI with a command line argument. If the path to the INI is already set with command line arguments, make sure they have been added correctly.

See https://dyndolod.info/Help/Command-Line-Argument. Also see https://dyndolod.info#Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG or https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG
The explanations which commands line to use do not include the -i command line. They instead explain to use -m to the folder.
Do not removes spaces. Best not edit folder or filenames. Copy and paste paths/filenames to avoid mistakes.

[Earl500]

8 hours ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log to upload when making posts.

Copy the text of the message to the clipboard and post the text of the message instead of a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text
The message tells you what the problem is. The path is wrong, there is no such path/filename. xEdit asks the OS if the file exists at the shown path and the OS reports that it does not. No information about the actual path has been provided.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages
Click on the link Click on this link for additional explanations and help for this message, which opens https://dyndolod.info/Messages/INI-Files.
The screenshot shows the game mode is SSE, so -sse seems to be working as expected.
Alternatively set the path to the INI with a command line argument. If the path to the INI is already set with command line arguments, make sure they have been added correctly.

See https://dyndolod.info/Help/Command-Line-Argument. Also see https://dyndolod.info#Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG or https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG
The explanations which commands line to use do not include the -i command line. They instead explain to use -m to the folder.
Do not removes spaces. Best not edit folder or filenames. Copy and paste paths/filenames to avoid mistakes.

Hello and thank you for the response.

First of all, I feel that I ought to provide more information. My initial problem was simply that starting TextGen at all (no command line arguments at all) through MO2 resulted in the following error message after selecting the SSE option, with no change by using the "-sse" argument or not doing so:

[Window Title]
TexGen

[Main Instruction]
Fatal: Could not open registry key: \SOFTWARE\Bethesda Softworks\Skyrim Special Edition\

[Content]
This can happen after Steam updates, run the game's launcher to restore registry settings.

Current game mode: Skyrim Special Edition (SSE)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

I was eventually lead to conclude by the instructions on the DynDOLOD website that this was because I had not put in the three recommended commandline arguments (-m,-p,-d) pointing to the correct folders and files. Upon doing so, I could launch TextGen but was immediately met with this error message:
 

[Window Title]
TexGen

[Main Instruction]
OlavSkyrim.ini can not be found.

[Content]
The INI file is missing from its default location at C:\Users\OlavSkyrim.ini.

Current game mode: Skyrim Special Edition (SSE)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard
 

From this error message I was lead to conclude that the issue was that the name I use as a username (Olav Huitfeldt) presented an issue to TextGen because it included a space, based on the reasoning that TextGen seems to stop registering anything after and included a space (like the space in my user name). Based on this, I attempted to change the username to Olaus in order to get around this issue, but this did not resolve anything. In short, the -m: commandline argument does not work properly. The path I direct it to by using that command ("-m:C:\Users\Olav Huitfeldt\Documents\My Games\Skyrim Special Edition GOG") is the only/proper location of the files in question.

These are the TextGen logs (both):
https://ufile.io/f/4ocx9

[sheson]

42 minutes ago, Earl500 said:

Hello and thank you for the response.

First of all, I feel that I ought to provide more information. My initial problem was simply that starting TextGen at all (no command line arguments at all) through MO2 resulted in the following error message after selecting the SSE option, with no change by using the "-sse" argument or not doing so:

[Window Title]
TexGen

[Main Instruction]
Fatal: Could not open registry key: \SOFTWARE\Bethesda Softworks\Skyrim Special Edition\

[Content]
This can happen after Steam updates, run the game's launcher to restore registry settings.

Current game mode: Skyrim Special Edition (SSE)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

I was eventually lead to conclude by the instructions on the DynDOLOD website that this was because I had not put in the three recommended commandline arguments (-m,-p,-d) pointing to the correct folders and files. Upon doing so, I could launch TextGen but was immediately met with this error message:
 

[Window Title]
TexGen

[Main Instruction]
OlavSkyrim.ini can not be found.

[Content]
The INI file is missing from its default location at C:\Users\OlavSkyrim.ini.

Current game mode: Skyrim Special Edition (SSE)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard
 

From this error message I was lead to conclude that the issue was that the name I use as a username (Olav Huitfeldt) presented an issue to TextGen because it included a space, based on the reasoning that TextGen seems to stop registering anything after and included a space (like the space in my user name). Based on this, I attempted to change the username to Olaus in order to get around this issue, but this did not resolve anything. In short, the -m: commandline argument does not work properly. The path I direct it to by using that command ("-m:C:\Users\Olav Huitfeldt\Documents\My Games\Skyrim Special Edition GOG") is the only/proper location of the files in question.

These are the TextGen logs (both):
https://ufile.io/f/4ocx9

xEdit - on which DynDOLOD is based - is a Windows program and uses DOS/Windows command line standards that enclose paths in double quotes as shown in the examples:

https://dyndolod.info/Help/Command-Line-Argument
-o:"[path to output folder]" for example -o:"c:\Output\"
-m:"[path to INI folder]" for example -m:"c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition GOG\"
-p:"[path to plugins.txt]" for example -p:"c:\Users\[USERNAME]\AppData\Local\Skyrim Special Edition GOG\plugins.txt"
-d:"[path to Data folder]" for example -d:"c:\GOG Games\Skyrim Special Edition GOG\Data\"
A path should always be enclosed between double quotes. Use copy and paste to avoid mistakes, like adding extraneous spaces between the command letter, colon and beginning double quotes.

[bruhdude3]

Hello, I have been using Dyndolod for my new mod list for the past week, after adding some miscellaneous mods, Dyndolod has started doing a weird thing where once it gets to start gathering references, it just closes itself, no log is generated except for a couple that I will attach, no output is generated either. Using MO2 as a mod manager.

Modlist(NSFW): https://docs.google.com/spreadsheets/d/1T4VXMKHpKsgX1B3L-3umq_BsBAvWiz2Ep5RUugmDJf8/edit?usp=sharing

Logs(everything but normal and debug logs since those are not up to date with the latest run): https://ufile.io/f/gyh5x

Sorry if this feels very vague, I will try to upload more logs if needed and follow the tips given on the website while I try to fix the issue.

 

 

[sheson]

6 hours ago, bruhdude3 said:

Hello, I have been using Dyndolod for my new mod list for the past week, after adding some miscellaneous mods, Dyndolod has started doing a weird thing where once it gets to start gathering references, it just closes itself, no log is generated except for a couple that I will attach, no output is generated either. Using MO2 as a mod manager.

Modlist(NSFW): https://docs.google.com/spreadsheets/d/1T4VXMKHpKsgX1B3L-3umq_BsBAvWiz2Ep5RUugmDJf8/edit?usp=sharing

Logs(everything but normal and debug logs since those are not up to date with the latest run): https://ufile.io/f/gyh5x

Sorry if this feels very vague, I will try to upload more logs if needed and follow the tips given on the website while I try to fix the issue.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the realtime log and how to check the Windows Event log for hints in case DynDOLOD is being terminated prematurely.

[bruhdude3]

13 hours ago, sheson said:

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the realtime log and how to check the Windows Event log for hints in case DynDOLOD is being terminated prematurely.

https://ufile.io/q6j28bsx - Here is the realtime log

[sheson]

10 hours ago, bruhdude3 said:

https://ufile.io/q6j28bsx - Here is the realtime log

Make sure d:\documents is not defined as a special Windows folder for documents - it is not what opens if clicking "Documents" in Windows Explorer left 

Check the Windows Event log for related messages.

Make sure the PC is stable with prime95, OCCT etc.

[bruhdude3]

8 hours ago, sheson said:

Make sure d:\documents is not defined as a special Windows folder for documents - it is not what opens if clicking "Documents" in Windows Explorer left 

Check the Windows Event log for related messages.

Make sure the PC is stable with prime95, OCCT etc.

I did all this but it still keeps crashing, Log Viewer does not show anything out of the ordinary but I did see that the program crashes once it gets to processing records for Tamriel, could this have something to do with it?

Edit: specifically this record: "[05:17] [BuildCells] <Debug: Gathering cells Tamriel Skyrim.esm Tamriel "Skyrim" [WRLD:0000003C]>"

2nd Edit: I was able to generate LOD for every other world except Tamriel, probably a mod that screws with the world space or might be broken.

Edited Sunday at 05:35 PM by bruhdude3

[sheson]

1 hour ago, bruhdude3 said:

I did all this but it still keeps crashing, Log Viewer does not show anything out of the ordinary but I did see that the program crashes once it gets to processing records for Tamriel, could this have something to do with it?

Edit: specifically this record: "[05:17] [BuildCells] <Debug: Gathering cells Tamriel Skyrim.esm Tamriel "Skyrim" [WRLD:0000003C]>"

2nd Edit: I was able to generate LOD for every other world except Tamriel, probably a mod that screws with the world space or might be broken.

The Event log should have an entry for the tool being terminated or crashing.

If a plugin/mod causes a problem, there should be an error message or a bugreport.txt etc.

Run this test version https://mega.nz/file/VRxGQKyD#YbGqyCIal5-1Vf9Le2XcFg4eXQryuVxKiFVhVKn0uSA
It will print a line for each cell is it is processing, then check whatever cell record is mentioned last in xEdit.