DynDOLOD 3.00 Alpha 190

[iReptar]

  On 12/23/2024 at 2:58 PM, 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.

Expand  

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]

  On 1/1/2025 at 3:49 AM, 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.

Expand  

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]

  On 1/1/2025 at 10:07 AM, 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.

Expand  

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]

  On 1/1/2025 at 7:53 PM, 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

Expand  

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]

  On 1/4/2025 at 1:39 AM, 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.

Expand  

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]

  On 1/4/2025 at 7:50 AM, 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.

Expand  

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

[sheson]

  On 1/4/2025 at 9:34 PM, bruhdude3 said:

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

Expand  

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]

  On 1/5/2025 at 9:29 AM, 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.

Expand  

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 January 5 by bruhdude3

[sheson]

  On 1/5/2025 at 4:58 PM, 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.

Expand  

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.

[bruhdude3]

  On 1/5/2025 at 6:42 PM, sheson said:

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.

Expand  

https://mega.nz/file/3cYTAY6Q#UXxGE-CmyVp7YcXt_gOdS5IQdc7S6Z1EIjWgy2Al4xQ - Real-time log

The last line is this one - "[03:20] [BuildCells] <Debug: Processing Skyrim.esm VolskyggeExterior03 [CELL:00006EE6] (in Tamriel "Skyrim" [WRLD:0000003C] at -33,22)>"

I can't use xEdit as it has the same problem that DynDOLOD is having, exiting without a log. I believe some corrupted mod is being loaded and causing the crash. Is there a way to force xEdit to build a realtime log? (Like the DynDOLOD setting I was told to turn on?)

Edit: I was able to fix SSEEdit problem, after a while, but now I will try to see which other mod is causing problems.

Edit: I seemed to have solved the crash issue with DynDOLOD, I will keep testing to see if anymore issues arise. What I believe fixed it for me was that I edited my Skyrim.ini with a stupid edit, setting the iMaxAllocatedMemoryBytes = 4000000, this was a bad thing to do and reverting it seems to have fixed the issue.

Edited January 6 by bruhdude3

[sheson]

  On 1/5/2025 at 9:53 PM, bruhdude3 said:

https://mega.nz/file/3cYTAY6Q#UXxGE-CmyVp7YcXt_gOdS5IQdc7S6Z1EIjWgy2Al4xQ - Real-time log

The last line is this one - "[03:20] [BuildCells] <Debug: Processing Skyrim.esm VolskyggeExterior03 [CELL:00006EE6] (in Tamriel "Skyrim" [WRLD:0000003C] at -33,22)>"

I can't use xEdit as it has the same problem that DynDOLOD is having, exiting without a log. I believe some corrupted mod is being loaded and causing the crash. Is there a way to force xEdit to build a realtime log? (Like the DynDOLOD setting I was told to turn on?)

Edit: I was able to fix SSEEdit problem, after a while, but now I will try to see which other mod is causing problems.

Edit: I seemed to have solved the crash issue with DynDOLOD, I will keep testing to see if anymore issues arise. What I believe fixed it for me was that I edited my Skyrim.ini with a stupid edit, setting the iMaxAllocatedMemoryBytes = 4000000, this was a bad thing to do and reverting it seems to have fixed the issue.

Expand  

Skyrim INI settings like iMaxAllocatedMemoryBytes do not affect xEdit or DynDOLOD.
I suggest to use BethINIs.

[kindperson]

Hello.

I'm sorry to bother asking for help, but I have a problem that I have spent over 20 hours trying to solve, I tried everything, read everything, and nothing works : (.

I'm trying to make my lod perfectly match my grass, in fact it does most of the time except for around 12:00 in-game time, I use Cabbage ENB, and Veydosebrom Regions, which utilizes complex grass. Here on this gallery https://imgbox.com/g/JUVuyKsZ5E the first picture taken around 12:00 in-game time shows how the grass lod doesn't match, it is too dark, but on every other time as you can see in the other pictures it matches perfectly. I'm baking HD Grass on texgen using 0 direct light and 202 ambient light, on Dyndolod ini I set ComplexGrassBrightness to 0.500, I tinkered with ComplexGrassBacklightMask from 0 to 100 it didn't solve the problem. 

Any help is greatly appreciated, thank you.

 

 

[z929669]

  On 1/8/2025 at 3:06 AM, kindperson said:

Hello.

I'm sorry to bother asking for help, but I have a problem that I have spent over 20 hours trying to solve, I tried everything, read everything, and nothing works : (.

I'm trying to make my lod perfectly match my grass, in fact it does most of the time except for around 12:00 in-game time, I use Cabbage ENB, and Veydosebrom Regions, which utilizes complex grass. Here on this gallery https://imgbox.com/g/JUVuyKsZ5E the first picture taken around 12:00 in-game time shows how the grass lod doesn't match, it is too dark, but on every other time as you can see in the other pictures it matches perfectly. I'm baking HD Grass on texgen using 0 direct light and 202 ambient light, on Dyndolod ini I set ComplexGrassBrightness to 0.500, I tinkered with ComplexGrassBacklightMask from 0 to 100 it didn't solve the problem. 

Any help is greatly appreciated, thank you.

 

 

Expand  

First, as the OP states, any posts here require the relevant log files.

It's not clear from your images where LOD grass begins. Use tll in the console as a reference (and the very first image) in image sets like this. This toggles LOD off/on. If you are referring to the dark-ish grass in the mid distance of the first image, this appears to be full grass, IMO. The LOD grass matches further back. I would guess it to be a cloud shadow (or some other shadow effect). You can test it by toggling cloud shadows in ENB or by changing similar settings in the ENB GUI.