DynDOLOD 3.00 Alpha 182

[xytyyy]

https://ufile.io/f/orpg5 Here are the logs.

1 hour ago, sheson said:

Read the first post which log and debug log to upload when making reports so I can try to reproduce the problem.

 

[sheson]

4 hours ago, xytyyy said:

https://ufile.io/f/orpg5 Here are the logs.

Thanks, this helps. The issue should be fixed next version.

[ignotus_patronus]

Hi, I've tried searching for this to no avail. I have multiple new worldspaces added to my Skyrim. I generated a DynDOLOD Output using the 2.0.0 guide after about 45 minutes. I recently added LOTD to the Tamriel Worldspace. For updating DynDOLOD, can I just select the Tamriel Worldspace? Will this overwrite all of my other worldspaces or only the Tamriel Worldspace?

[sheson]

2 hours ago, ignotus_patronus said:

Hi, I've tried searching for this to no avail. I have multiple new worldspaces added to my Skyrim. I generated a DynDOLOD Output using the 2.0.0 guide after about 45 minutes. I recently added LOTD to the Tamriel Worldspace. For updating DynDOLOD, can I just select the Tamriel Worldspace? Will this overwrite all of my other worldspaces or only the Tamriel Worldspace?

See https://dyndolod.info/Updating#New-or-Updated-Mods-or-Plugins

[ignotus_patronus]

6 hours ago, sheson said:

See https://dyndolod.info/Updating#New-or-Updated-Mods-or-Plugins

Thank you! I will see if I can figure it out.

[fattyzhouse]

Hello. Hope everyone is doing well. Here's one that I don't understand. An "assertion failure." It just happened as I started re-running TexGen from Dyn 3 Alpha 83. Alpha 82 ran through fine, but I'm not sure what to do about this one. No hurries or worries, modkin. Here's a look at the debug file. 

https://paste.ee/p/rw8SG

[sheson]

14 minutes ago, fattyzhouse said:

Hello. Hope everyone is doing well. Here's one that I don't understand. An "assertion failure." It just happened as I started re-running TexGen from Dyn 3 Alpha 83. Alpha 82 ran through fine, but I'm not sure what to do about this one. No hurries or worries, modkin. Here's a look at the debug file. 

https://paste.ee/p/rw8SG

Check what happens if you load the load order in xEdit 4.0.4.

If hat works, see what happens with xEdit_4.1.4b_EXTREMELY_EXPERIMENTAL from the xEdit discord #xedit-builds.

What mod is Ayleid Aquarium.esp from?

[fattyzhouse]

Ayleid Aquarium is a modified version of The Dragonborn's Aquarium by Betalille. I made quite a few changes so it's entirely possible that I'm the culprit here. LoL! I don't have a discord but I'll sign up and snag the experimental version if need be. I have my load order opened up in xedit 4.0.4 now. It opened up without a hitch.

[fattyzhouse]

I have permission from Betalille to upload my version to Nexus so if I've made a mistake now would be a perfect time to catch it. I could copy it to my google drive and drop a link to it if you want to have a look see. 

[sheson]

25 minutes ago, fattyzhouse said:

Ayleid Aquarium is a modified version of The Dragonborn's Aquarium by Betalille. I made quite a few changes so it's entirely possible that I'm the culprit here. LoL! I don't have a discord but I'll sign up and snag the experimental version if need be. I have my load order opened up in xedit 4.0.4 now. It opened up without a hitch.

Note that xEdit often continues to load despite a plugin having problems so that it can still be worked on and fixed. Pay attention to the log messages.

See if loading/saving plugin in CK makes a difference.

Since DynDOLOD is based on the 4.1.4 experimental, test with that if possible. Otherwise send me link in a PM.

[fattyzhouse]

Will do. Be back in a few with a report. Thanks!

[fattyzhouse]

Found it. TexGen fired up and is running as it should. The xedit log messages pointed me right to it. I think I realize now how I messed up. I had made one single change to the Ayleid Aquarium plugin using the creation kit AFTER I flagged the esp as an esl using xedit. That one change gave me a bad form id. (Or an un-compacted form id?) I have several of what they call 'twinkle lights' scattered about the interior and I remember adding one more 'twinkle light' after flagging as an esl. 
My solution here was to
(1)unflag the esp. (2)Resave it without the esl flag. (3)Close xedit. (4)Reopen xedit. (5)Recompact the form id's and reflag the plugin as esl.
That eliminated the error in xedit and TexGen fired up and is running proper. I'll come back if there's anything else worth reporting, or if you have any questions about my ramblings. Have a great one you holy cow you! Thanks for the help!

[sheson]

50 minutes ago, fattyzhouse said:

Found it. TexGen fired up and is running as it should. The xedit log messages pointed me right to it. I think I realize now how I messed up. I had made one single change to the Ayleid Aquarium plugin using the creation kit AFTER I flagged the esp as an esl using xedit. That one change gave me a bad form id. (Or an un-compacted form id?) I have several of what they call 'twinkle lights' scattered about the interior and I remember adding one more 'twinkle light' after flagging as an esl. 
My solution here was to
(1)unflag the esp. (2)Resave it without the esl flag. (3)Close xedit. (4)Reopen xedit. (5)Recompact the form id's and reflag the plugin as esl.
That eliminated the error in xedit and TexGen fired up and is running proper. I'll come back if there's anything else worth reporting, or if you have any questions about my ramblings. Have a great one you holy cow you! Thanks for the help!

Oh yeah, CK is the one that ignores the ESL flag when editing plugins, meaning it happily creates new form IDs outside the allowed limits.

Odd that this resulted in an assertion error and not the invalid object ID error message.

[Vernon]

LODGenx64.exe randomly stops using CPU, even with antivirus turned off. It uses all of my RAM but has CPU usage at 0%

[sheson]

4 hours ago, Vernon said:

LODGenx64.exe randomly stops using CPU, even with antivirus turned off. It uses all of my RAM but has CPU usage at 0%

See if using the LODGenThreadSplit setting explained at https://dyndolod.info/Help/LODGen#Out-of-Memory helps.

If problem persists, set verbose=1 in DynDOLOD_SSE.INI, run and then upload LODGen log and DynDOLOD log, debug as explained on the first post.