DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[Vokans]

 

In that case mark the entire text and copy paste the log from the message window. Use the "Check log" button after DynDOLOD ran.

 

However, from the TexGen_SSE.log I can see that the xEdit loader reported that there are ESPs flagged as ESL that have invalid ObjectID

 

A: Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. 

 

https://www.dropbox.com/s/1s0xfeubw68zhl8/DynDOLOD?dl=0 Copy of "Check log"

 

I will try to fix the errors.

Edited November 24, 2018 by Vokans

[gem2492]

 

LOL it is trying to load a txt file as a texture. Such an obscure bug (has to do with billboards that allow more than one texture). Thanks for all the help figuring this one out.

 

This all should be fixed in 2.52. Please let me know how it goes.

 

2.52 was successful and there are no more "FAILED" errors. Thanks a lot!

 

And thank you for explaining everything instead of just "do this then do that." I feel a tad smarter now. lol

 

By the way, I noticed that the DynDOLOD SSE log has a lot of "Warning: Error loading Textures/..." as well as "missing model"

http://www.mediafire.com/file/mk93lrlxrdeb797/Logs2.zip/file

 

I'm not sure if that is normal, so I just want to confirm if everything is fine now.

Edited November 24, 2018 by gem2492

[sheson]

https://www.dropbox.com/s/1s0xfeubw68zhl8/DynDOLOD?dl=0 Copy of "Check log"

 

I will try to fix the errors.

The log shows additional, unrelated errors:

 

There is one Access Denied error where the OS prevents creation of the atlas texture for LabyrinthianMazeWorld. Run the tools "As Admin" in case that keeps happening.

 

It seems that terrain LOD meshes are in a BSA file(s), which might have problems. LODGenx64.exe was unable to read terrain LOD meshes for several worldspaces as you can see from the LODGenx64.exe errors at the end of the log.

 

You want to double check the BSA files are valid and can be read properly by the game. I generally do not recommend that users pack generated LOD files into BSA for various reasons. LODGenx64.exe should be able to work without problem with loose terrain LOD meshes. 

[sheson]

2.52 was successful and there are no more "FAILED" errors. Thanks a lot!

 

And thank you for explaining everything instead of just "do this then do that." I feel a tad smarter now. lol

 

By the way, I noticed that the DynDOLOD SSE log has a lot of "Warning: Error loading Textures/..." as well as "missing model"

http://www.mediafire.com/file/mk93lrlxrdeb797/Logs2.zip/file

 

I'm not sure if that is normal, so I just want to confirm if everything is fine now.

 

Because of our troubleshooting there may be now a few too many unnecessary error messages. It is possible they were formerly silent and intended to be ignored.

Or they show a problem that should be fixed. 

 

Please upload (some or all) of these textures for me to review.

Edited November 24, 2018 by sheson

[sirjesto]

Updated from 2.44/2.50  to 2.45/2.52  today.

 

 

[00:16:59.455] DynDOLOD Worlds completed successfully.

[00:20:28.204] [20:47] Saving: DynDOLOD.esm

[00:20:28.204] [20:47] Error saving DynDOLOD.esm: Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 14550)

[00:20:28.216] [20:48] Saving: DynDOLOD.esp.save.2018_11_24_18_00_33

Can't quit the program without killing the process...just keeps saying failed to create .esm and making  a 0k backup file over and over.

Edited November 25, 2018 by sirjesto

[gem2492]

Because of our troubleshooting there may be now a few too many unnecessary error messages. It is possible they were formerly silent and intended to be ignored.

Or they show a problem that should be fixed. 

 

Please upload (some or all) of these textures for me to review.

As an example, one of the warnings says

<Warning: Error loading Textures\Terrain\LODGen\Skyrim.esm\ReachFern02_000B8A6F.dds>

I tried looking for that specific file in the TexGen_Output and DynDOLOD Resources, but I can't find it. This is also the case with the other warnings. All of them are pointing to "Textures\Terrain\LODGen\..."

 

Regarding the "missing model" errors, I found this in the DynDOLOD log:

References using base records with missing models can cause CTD.

(1) Verify that all required BSA files are loaded.
MO archive management is incompatible with many 3rd party tools like xEdit and consequently DynDOLOD.exe.
Check this startup log on top, to make sure all required BSA files are loaded via a matching esp filename.

Unfortunately, there is no way to disable MO2 archive management, as far as i know, unlike in MO where there is a checkbox to disable it.

[Martimius]

 

Updated from 2.44/2.50  to 2.45/2.52  today.

 

 

Can't quit the program without killing the process...just keeps saying failed to create .esm and making  a 0k backup file over and over.

 

Yeah, experiencing the same thing here.

[bloody11]

 

Updated from 2.44/2.50  to 2.45/2.52  today.

 

 

Can't quit the program without killing the process...just keeps saying failed to create .esm and making  a 0k backup file over and over.

 

I have the same problem, error saving DynDOLOD.esm: Assertion failure  appears and I can not close the program, I can only use the task manager

[sirjesto]

Yeah, experiencing the same thing here.

 

I have the same problem, error saving DynDOLOD.esm: Assertion failure  appears and I can not close the program, I can only use the task manager

I thought it was just me.  I wonder if this is only happening to a few of us?

 

Are you guys using MO2?

Edited November 25, 2018 by sirjesto

[Vokans]

I still have the issue 

 

 

DynDOLOD Worlds completed successfully.

[00:14:53.473] [00:49] Saving: DynDOLOD.esm

[00:14:53.964] [00:50] Saving: DynDOLOD.esp

[00:14:53.965] [00:50] Error saving DynDOLOD.esp: Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 14550)

[00:14:53.976] [00:50] Errors have occured. At least one file was not saved.

[00:14:53.992] [00:50] Done saving.

 

I have deactivated a plenty of mods, still the same.

 

I'm the only one with " Error saving DynDOLOD.esp"   

Edited November 25, 2018 by Vokans

[Vokans]

All log files https://www.dropbox.com/sh/dwen26vct2s1utr/AAB5xiVIwbVbw35Bj2HsCv4Ua?dl=0

Edited November 25, 2018 by Vokans

[Martimius]

Yeah, using MO2. I don't even have a log though because I had to close the process via Task Manager.

[sirjesto]

I still have the issue 

 

 

I have deactivated a plenty of mods, still the same.

 

I'm the only one with " Error saving DynDOLOD.esp" 

Yeah I am getting it on the .esm

 

 

Yeah, using MO2. I don't even have a log though because I had to close the process via Task Manager.

Ok, yeah me too.

[Martimius]

I still have the issue 

 

 

I have deactivated a plenty of mods, still the same.

 

I'm the only one with " Error saving DynDOLOD.esp" 

No you aren't- for me, the .esm saves nicely but the .esp doesn't save. After I close the program with Task Manager I do somewhat have an .esp actually, but it's 0 bytes. 

[sheson]

As an example, one of the warnings says

<Warning: Error loading Textures\Terrain\LODGen\Skyrim.esm\ReachFern02_000B8A6F.dds>

I tried looking for that specific file in the TexGen_Output and DynDOLOD Resources, but I can't find it. This is also the case with the other warnings. All of them are pointing to "Textures\Terrain\LODGen\..."

 

Regarding the "missing model" errors, I found this in the DynDOLOD log:

References using base records with missing models can cause CTD.

(1) Verify that all required BSA files are loaded.
MO archive management is incompatible with many 3rd party tools like xEdit and consequently DynDOLOD.exe.
Check this startup log on top, to make sure all required BSA files are loaded via a matching esp filename.

Unfortunately, there is no way to disable MO2 archive management, as far as i know, unlike in MO where there is a checkbox to disable it.

If there are no such texture you can ignore the messages about them. I will remove the useless message next update.

 

Missing models with the current Bruma is "normal" at the moment and should be OK. Archive management is is not available in MO2, so it is like always off.