DynDOLOD 3.00 Alpha 198

[DDCrusader]

14 hours ago, sheson said:

Use a legal version of the game. Pay attention to log messages.

Delete old log. Run this test version https://mega.nz/file/FMx1AaRT#p2BwU-k73CCk3tRlgZsFJBRPqqAt3wJR8Lts4h3OvbI. Upload new logs.

Then add ExportLANDBinary=0 under [DynDOLOD] to D:\Games\Skyrim\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini
Delete old logs. Run test version. Upload these new logs as well.

Thank you, Mr. sheson!

As for the logs, I followed your instructions:

Logs: https://ufile.io/f/hpb6t

1. I replaced the .exe, cleared logs folder;

2. First run failed, like before, results are in DynDOLOD-I.zip;

3. I cleared logs folder, added ExportLANDBinary=0 and second run finished successfully, results are in DynDOLOD-II.zip.

[sheson]

10 hours ago, UnNateUrals said:

Hello, short message here.  when starting up dynDOLOD, I get almost a couple minutes worth of these:  https://imgbox.com/MxePV9rZ  I don't have anything crashing, but I don't know if this is normal or not.  Does anyone know how to handle this?

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

Do not post screenshots of text. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

See https://dyndolod.info/Messages and https://dyndolod.info/Help/Summary-Of-Messages for explanations and a list of messages further help for messages.

Ask specific question(s) about a particular message if further help is required.

[sheson]

6 hours ago, DDCrusader said:

Thank you, Mr. sheson!

As for the logs, I followed your instructions:

Logs: https://ufile.io/f/hpb6t

1. I replaced the .exe, cleared logs folder;

2. First run failed, like before, results are in DynDOLOD-I.zip;

3. I cleared logs folder, added ExportLANDBinary=0 and second run finished successfully, results are in DynDOLOD-II.zip.

Thanks for those logs.

Delete old logs. Restore default INI or change to ExportLANDBinary=1
Run this test version https://mega.nz/file/MMwCTTwA#7KeWZNiBGTMXlu24VP6yg91JAcFc-ItDQRx6K0psgmk
Upload new logs.

[Atardecer]

16 hours ago, sheson said:

Only debug logs were uploaded.

The debug log reports that there is a file C:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\seasons\MainFormSwap_WIN.ini, it is loaded and processed.
As usual, to find files in the data folder, use MO2 right window Data tab. Make sure enable the Mod column. Make sure to check Enable archives parsing under menu Tools, Workarounds tabs.

Thanks Sheson.

Found the pesky ini buried in the Mo2 Data tab, which was physically located elsewhere. All sorted now and DLOD runs just fine.

[tk421storm]

Hey - I've been experiencing some repeatable crashes attempting to generate LOD for my load order using the latest alpha (190). I am able to get to the last step (completed LODgen, ACMOS road, parallaxgen and texgen). I get an access denied error along these lines:

`Error: Access violation at address 0000000000800330 in module 'DynDOLODx64.exe' (offset 10330). Read of address FFFFFFFFFFFFFFFF while processing Skyrim.esm [REFR:0005A94B] (Places DweRubblePile01Snow [STAT:000765F5] in MzulftExteriorB02`

Trouble is, i'm currently finalizing a PBR texture pack for dwemer/markarth stuff and I feel like it might be failing on my textures. In game I'm able to play as normal (with dynlod disabled) however before I release on the nexus I want to ensure it can be LOD'd successfully. Is there anything in these logs that can help me understand what might be happening? I have freed up around 40gb of space on the output drive, and set the TEMP directory to a drive with ~200gb of free data, and I have 64gb of RAM.

https://drive.google.com/file/d/1de8W6AbBei1jDM3sd90q7vzYd08OpbPs/view?usp=sharing

Happy to share any of the texture files as well, they're generally 4k dds with around 5 passes/nif.

[sheson]

8 hours ago, tk421storm said:

Hey - I've been experiencing some repeatable crashes attempting to generate LOD for my load order using the latest alpha (190). I am able to get to the last step (completed LODgen, ACMOS road, parallaxgen and texgen). I get an access denied error along these lines:

`Error: Access violation at address 0000000000800330 in module 'DynDOLODx64.exe' (offset 10330). Read of address FFFFFFFFFFFFFFFF while processing Skyrim.esm [REFR:0005A94B] (Places DweRubblePile01Snow [STAT:000765F5] in MzulftExteriorB02`

Trouble is, i'm currently finalizing a PBR texture pack for dwemer/markarth stuff and I feel like it might be failing on my textures. In game I'm able to play as normal (with dynlod disabled) however before I release on the nexus I want to ensure it can be LOD'd successfully. Is there anything in these logs that can help me understand what might be happening? I have freed up around 40gb of space on the output drive, and set the TEMP directory to a drive with ~200gb of free data, and I have 64gb of RAM.

https://drive.google.com/file/d/1de8W6AbBei1jDM3sd90q7vzYd08OpbPs/view?usp=sharing

Happy to share any of the texture files as well, they're generally 4k dds with around 5 passes/nif.

Also upload the bugreport.txt as explained in the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Is this error repeatable?

[MrPrideHyde]

Hi! Can someone please help me, TexGen has been giving me a lot of grief for the last few days, I tried choosing recommended settings, lowering those settings, changing various options in the INI file, e.g. RenderThreads=1, or adding TextureCache=10 at the end. The reasoning: 90-100 CPU usage, and when it drops to normal, the crash follows shortly after. I tried regenerating grass cache, parallax and xLODGen more than a few times, removed a mod I was suspicious of and did the previous steps again... If I understand the bugreport.txt file correctly, most of the time I'm getting an integer overflow error. No logs in the Windows Event Viewer, none inside the DynDOLOD folder either (except when I enable real time logging). Here's a zip file packed with logs, load order, bugreport and whatever was generated during the last run. This time I got an exception error though, the program ran for 2,5 minutes (previous averages were around 1 minute mark) and generated 30ish megabyte of output. Which is also strange, I used to get 70-90MB without real time logging and while getting those sweet integer overflows in less time!

Almost sure I'm missing smth real obvious, here are the files: https://disk.yandex.ru/d/_F6aBbe978WaUQ

P.S. I have the latest versions of everything I can think of, the Windows, Nvidia driver, NET and Visual stuff, Mod Organizer and DynDOLOD 3.00 Alpha 190, the DLL (NG version), resources too.

[sheson]

1 hour ago, MrPrideHyde said:

Hi! Can someone please help me, TexGen has been giving me a lot of grief for the last few days, I tried choosing recommended settings, lowering those settings, changing various options in the INI file, e.g. RenderThreads=1, or adding TextureCache=10 at the end. The reasoning: 90-100 CPU usage, and when it drops to normal, the crash follows shortly after. I tried regenerating grass cache, parallax and xLODGen more than a few times, removed a mod I was suspicious of and did the previous steps again... If I understand the bugreport.txt file correctly, most of the time I'm getting an integer overflow error. No logs in the Windows Event Viewer, none inside the DynDOLOD folder either (except when I enable real time logging). Here's a zip file packed with logs, load order, bugreport and whatever was generated during the last run. This time I got an exception error though, the program ran for 2,5 minutes (previous averages were around 1 minute mark) and generated 30ish megabyte of output. Which is also strange, I used to get 70-90MB without real time logging and while getting those sweet integer overflows in less time!

Almost sure I'm missing smth real obvious, here are the files: https://disk.yandex.ru/d/_F6aBbe978WaUQ

P.S. I have the latest versions of everything I can think of, the Windows, Nvidia driver, NET and Visual stuff, Mod Organizer and DynDOLOD 3.00 Alpha 190, the DLL (NG version), resources too.

It is possible a source texture has issues.

Do you have a mod containing textures\_resourcepack\landscape\grass\mesagrass02.dds? If so, which one or could you upload the texture?
Not quite sure if this texture is related to the issue or not, though.

Restore default TexGen_SSE.ini and run this test version https://mega.nz/file/BRYAFYgD#sk54a8RGSkX3Br0qF-qtEmLMS_XeuHOPaVwIqreFZYc

If this runs without error it is possible a generated texture / billboard looks funny. Maybe not. Might be hard to see, if at all.

[MrPrideHyde]

1 hour ago, sheson said:

It is possible a source texture has issues.

Do you have a mod containing textures\_resourcepack\landscape\grass\mesagrass02.dds? If so, which one or could you upload the texture?
Not quite sure if this texture is related to the issue or not, though.

Restore default TexGen_SSE.ini and run this test version https://mega.nz/file/BRYAFYgD#sk54a8RGSkX3Br0qF-qtEmLMS_XeuHOPaVwIqreFZYc

If this runs without error it is possible a generated texture / billboard looks funny. Maybe not. Might be hard to see, if at all.

I'm afraid my PC doesn't contain a single mesagrass02.dds file, searched using Everything. I brought back the original INI file, replaced the EXE with the one you provided, and it followed the same pattern, 1 minute generating, crash at a random tree or grass file, 70MB output, no error message, no log, only the bugreport file changed.

Here's a fragment from the beginning:

callstack crc      : $731e0d9d, $94169911, $5d9c0414
exception number   : 13
exception class    : EIntOverflow
exception message  : Unknown.

[sheson]

2 hours ago, MrPrideHyde said:

I'm afraid my PC doesn't contain a single mesagrass02.dds file, searched using Everything. I brought back the original INI file, replaced the EXE with the one you provided, and it followed the same pattern, 1 minute generating, crash at a random tree or grass file, 70MB output, no error message, no log, only the bugreport file changed.

Here's a fragment from the beginning:

callstack crc      : $731e0d9d, $94169911, $5d9c0414
exception number   : 13
exception class    : EIntOverflow
exception message  : Unknown.

No new realtime log or bugreport.txt was uploaded. Upload those entire logs.

It will be at least in _ResourcePack.bsa.
As usual, to find files in the data folder, use MO2 right window Data tab. Make sure enable the Mod column. Make sure to check Enable archives parsing under menu Tools, Workarounds tabs.

[MrPrideHyde]

14 hours ago, sheson said:

No new realtime log or bugreport.txt was uploaded. Upload those entire logs.

It will be at least in _ResourcePack.bsa.
As usual, to find files in the data folder, use MO2 right window Data tab. Make sure enable the Mod column. Make sure to check Enable archives parsing under menu Tools, Workarounds tabs.

Sorry, tis as you said, I found _ResourcePack.bsa (classified as Creation Club: _ResourcePack), inside it: textures\_resourcepack\landscape\grass\mesagrass02.dds, I also skimmed through every other BSA file in Data, haven't found another mesagrass02.dds

Wasn't able to unpack it using BSAopt, if the file itself is still necessary, pls share the correct method to extract it

Here are the files from the most recent try (EXE version 188, default TexGen_SSE.ini except the added RealTimeLog=1): https://disk.yandex.com/d/nVZTjSahZJbnvw

[z929669]

3 hours ago, MrPrideHyde said:

Sorry, tis as you said, I found _ResourcePack.bsa (classified as Creation Club: _ResourcePack), inside it: textures\_resourcepack\landscape\grass\mesagrass02.dds, I also skimmed through every other BSA file in Data, haven't found another mesagrass02.dds

Wasn't able to unpack it using BSAopt, if the file itself is still necessary, pls share the correct method to extract it

Here are the files from the most recent try (EXE version 188, default TexGen_SSE.ini except the added RealTimeLog=1): https://disk.yandex.com/d/nVZTjSahZJbnvw

Using MO:

Just create a temp folder somewhere for extraction of the archive.

[MrPrideHyde]

19 minutes ago, z929669 said:

Using MO:

Just create a temp folder somewhere for extraction of the archive.

Alright: https://disk.yandex.ru/d/9Nip-thRk_AVEA

[sheson]

6 hours ago, MrPrideHyde said:

Sorry, tis as you said, I found _ResourcePack.bsa (classified as Creation Club: _ResourcePack), inside it: textures\_resourcepack\landscape\grass\mesagrass02.dds, I also skimmed through every other BSA file in Data, haven't found another mesagrass02.dds

Wasn't able to unpack it using BSAopt, if the file itself is still necessary, pls share the correct method to extract it

Here are the files from the most recent try (EXE version 188, default TexGen_SSE.ini except the added RealTimeLog=1): https://disk.yandex.com/d/nVZTjSahZJbnvw

Use xEdit Asset Browser (CTRL+F3) to extract single files from archives or maybe BSArch.

Delete all old logs and bugreport.txt. Run this test version https://mega.nz/file/gUIGkbDL#1MrXg5ErgBHhSdZkuk3CsJTWPyQCHCB_xQ_Mdc1zNp4

Upload new log(s), bugreport.

[tk421storm]

On 3/4/2025 at 2:11 AM, sheson said:

Also upload the bugreport.txt as explained in the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Is this error repeatable?

Yes! Quite repeatable, seems to die on the same two textures every time.

bug report.txt