DynDOLOD 3.00 Alpha 190

[EazyH]

Maybe better to ask here. Hey Sheson, for some reason, sometimes but not all the time I get error EO434352. I have no idea what the problem is. It popped up once saying it was unable to create LODGEN for Tameriel, except it*did generate everything, including the Textures, Meshes, and plug-ins. I just recently selected “execute LODGEN“ to update grass color, and it only gave me meshes. Would I want to rebuild atlas? It only gives me very vague things to troubleshoot, like checking Microsoft visual, which I definitely have otherwise nothing would work
It seems the only time I can get around it is when freshly installing. I added it to my ignore list for Norton, but I don’t see that being the issue since I don’t get any pop up or warning.

 

After searching,found the DL link you shared for LODGGen. I'm trying v34 first, as I was on 33, but will use if no dice

 

Okay, now it wont even fully run forr dyndolod.exe. I'm getting errors for example that tundrabend01 and its lod "not matching"  (only touched by MM, and it & its lod which win all conflicts) along w/ missing bruma stuff (even when disabling bruma's worldspace in ignore ini), before saying "missimg items" and simply stopping. Never had these issues w/v33

Edited July 28, 2021 by EazyH

[sheson]

  On 7/27/2021 at 9:37 PM, RockGodOne said:

I keep getting an error that simply says "Item not found" with the "Help for his message" link that brings me to a page that just says "A problem occured that does not have a specific help page".

Using the newest DynDOLOD 3 alpha version that was just updated, as well as the newest DynDOLOD Resources for v3.

bugreport.txt

Hopefully that's enough because pastebin says the other 2 files were too big unless I upgrade to Pro, which I'm not interested in.

Expand  

Fix file/texture not found errors.

Zip and upload the logs to include in reports to a file service. The debug log is always just the last process. You can truncate the other log to the LOD generation with the error.

  On 7/27/2021 at 11:55 PM, Xgatt said:

I'm using the latest DynDOLOD 3.0 (with resources) from the Misc files section of the DynDOLOD Nexus page. The first two times I ran it, it crashed with invalid form ID errors, which I have since fixed. Now however it just hangs around at 0% CPU usage right after the Generating Object LOD message. Is there anything I should do to debug this? The Debug log shows some records being processed, but the output folder has nothing yet around 30 minutes later.

Expand  

What do you mean DynDOLOD crashed with invalid form ID errors? Was there no proper error message with detailed explanation of what the error in the load order is and with a "help for this message" link?

In case you can not find a plugin/mod causing this, close the program via the X top right, it will prompt a message about incomplete LOD, so acknowledge that and then wait. It should close within a few seconds while it writes the logs. Then upload the logs as explained on the first post.

[sheson]

  On 7/28/2021 at 1:41 AM, Selfishmonkey said:

I'm also getting the Item not found error. Wasn't present in Alpha 33. I can't revert to the previous version as I deleted it. Can't figure out what's causing it.

Expand  

Fix file/texture not found errors.

Read the first post what log files to include when making reports.

  On 7/28/2021 at 1:46 AM, EazyH said:

Maybe better to ask here. Hey Sheson, for some reason, sometimes but not all the time I get error EO434352. I have no idea what the problem is. It popped up once saying it was unable to create LODGEN for Tameriel, except it*did generate everything, including the Textures, Meshes, and plug-ins. I just recently selected “execute LODGEN“ to update grass color, and it only gave me meshes. Would I want to rebuild atlas? It only gives me very vague things to troubleshoot, like checking Microsoft visual, which I definitely have otherwise nothing would work
It seems the only time I can get around it is when freshly installing. I added it to my ignore list for Norton, but I don’t see that being the issue since I don’t get any pop up or warning.

 

After searching,found the DL link you shared for LODGGen. I'm trying v34 first, as I was on 33, but will use if no dice

 

Okay, now it wont even fully run forr dyndolod.exe. I'm getting errors for example that tundrabend01 and its lod "not matching"  (only touched by MM, and it & its lod which win all conflicts) along w/ missing bruma stuff (even when disabling bruma's worldspace in ignore ini), before saying "missimg items" and simply stopping. Never had these issues w/v33

Expand  

Always use the latest available version.

Fix file/texture not found errors.

Read the first post what log files to include when making reports.

[RockGodOne]

  On 7/27/2021 at 11:00 PM, z929669 said:

See instructions and links at top of this page

Expand  

It's still too big for paste.ee too. The log file is 1.6MB and the debug log is 1.2MB. Paste.ee only allows 1MB and pastebin only allows 0.5MB.

 

Since others have reported the same error tho, maybe it'll get fixed with logs they can share.

[sheson]

  On 7/28/2021 at 7:14 AM, RockGodOne said:

It's still too big for paste.ee too. The log file is 1.6MB and the debug log is 1.2MB. Paste.ee only allows 1MB and pastebin only allows 0.5MB.

Since others have reported the same error tho, maybe it'll get fixed with logs they can share.

Expand  

Fix file/texture not found errors.

Zip and upload the logs to include in reports to a file service. The debug log is always just the last process. You can truncate the other log to the LOD generation with the error.

[Wolfpack49]

Hi Sheson,

Just a question on the referenced Majestic Mountain LODs for Alpha 35.  Is the referenced 7z on the first post here more recent than the latest MM LOD version on the Nexus (v1.2)?

[z929669]

  On 7/28/2021 at 2:47 PM, Wolfpack49 said:

Hi Sheson,

Just a question on the referenced Majestic Mountain LODs for Alpha 35.  Is the referenced 7z on the first post here more recent than the latest MM LOD version on the Nexus (v1.2)?

Expand  

I would always use files provided by sheson and override with anything provided by the mod (just like DynDOLOD Resources). That way, it's a moot point.

[Wolfpack49]

  On 7/28/2021 at 3:02 PM, z929669 said:

I would always use files provided by sheson and override with anything provided by the mod (just like DynDOLOD Resources). That way, it's a moot point.

Expand  

Yep, good point and will do.

[Selfishmonkey]

  On 7/28/2021 at 6:36 AM, sheson said:

Fix file/texture not found errors.

Read the first post what log files to include when making reports.

Always use the latest available version.

Fix file/texture not found errors.

Read the first post what log files to include when making reports.

Expand  

I've looked through the log now - it seems to me most of the errors are missing nifs from Beyond Skyrim Bruma. Opening the bsa I can't the ones missing either. So, either the esp makes reference to nifs never included, or something else is going on. Weird, though, this has never been an issue before.

[sheson]

  On 7/28/2021 at 2:47 PM, Wolfpack49 said:

Hi Sheson,

Just a question on the referenced Majestic Mountain LODs for Alpha 35.  Is the referenced 7z on the first post here more recent than the latest MM LOD version on the Nexus (v1.2)?

Expand  

There is no LOD Pack for DynDOLOD 3 for Alpha 34 and newer available yet at the mods file section. I sent it to T4gtr34um3r and it will hopefully be added soon.

  On 7/28/2021 at 3:10 PM, Selfishmonkey said:

I've looked through the log now - it seems to me most of the errors are missing nifs from Beyond Skyrim Bruma. Opening the bsa I can't the ones missing either. So, either the esp makes reference to nifs never included, or something else is going on. Weird, though, this has never been an issue before.

Expand  

Textures end in *.DDS and not in *.NIF. Those are models.

Read the first post what log files to include when making reports.

[xcal68]

  On 7/28/2021 at 1:21 AM, xcal68 said:

Just reporting an issue with the DynDOLOD 3, Alpha 34, related to the UI.  When adding a new rule (right click > insert) in the "Mesh and Reference rules" section of the Advanced window, the last line gets pushed down (as expected), but you cannot scroll down to see it.  Adding further rules continues to push the last line further down, out of sight.  At first I thought it was removing or overwriting the rule that you happen to be right clicking on, but if you remove a rule, it brings the hidden line back up and it's viewable again.  This does not happen in Alpha 33.

As a side note, I'm also getting the "Item not found" error that RockGodOne and verrik are reporting, which was introduced (for me) in Alpha 34.  This issue is not present when generating LODs in Alpha 33 (which I've reverted back to for now).  I'll consider posting logs for that, if I get a chance, but for now I really just wanted to mention the UI thing.

Expand  

Thanks for the update.  Alpha 35 resolved both issues for me.

[sheson]

  On 7/28/2021 at 5:43 PM, xcal68 said:

Thanks for the update.  Alpha 35 resolved both issues for me.

Expand  

Great. Thanks for letting us know.

[EazyH]

Dyndo-log... get it? - Pastebin.com

Thankfully it now generates w/ v35. This is a truncated version of the warnings that seem most important. Unable to fit everything, but beyond is mostly large reference warnings which if I understand correctly, are hard to get rid of. What is this mismatch texture warning? All of my textures are definitely loaded correctly, MM lod especially. I mention MM since alot are mountain  related

 

I may have been overanalyzing the log, since I believe most of the warnings simply came from different overwriting records. The important thing is that as others have said, it generates fine again, and helped me track down a couple minor unresolved script errors. Thanks for the quick update!

Edited July 29, 2021 by EazyH

[Selfishmonkey]

So Alpha 35 solved my Item not Found error, but now I'm getting a Duplicates not Allowed error.

 

Bug report and Dyndolod SSE log https://drive.google.com/file/d/1LgWt2JWPmce0FiPIBsF3IgoYOru-BXzw/view?usp=sharing

Edited July 29, 2021 by Selfishmonkey

[sheson]

  On 7/28/2021 at 11:53 PM, EazyH said:

Dyndo-log... get it? - Pastebin.com

Thankfully it now generates w/ v35. This is a truncated version of the warnings that seem most important. Unable to fit everything, but beyond is mostly large reference warnings which if I understand correctly, are hard to get rid of. What is this mismatch texture warning? All of my textures are definitely loaded correctly, MM lod especially. I mention MM since alot are mountain  related

 

I may have been overanalyzing the log, since I believe most of the warnings simply came from different overwriting records. The important thing is that as others have said, it generates fine again, and helped me track down a couple minor unresolved script errors. Thanks for the quick update!

Expand  

Read the first post what logfiles to include in posts. Always post entire logs for the last meaningful process, e.g. from starting the tools to the end.

ESP plugins overwriting large references should be considered visually incompatible with a Skyrim Special Edition engine feature. If the visual issues are a problem, either do not use the plugin, fix the cause of the errors with the help of the log messages or do not use the feature.

The texture mismatch means there are "older"/vanilla LOD models from other mods overwriting the Core Files from DynDOLOD Resources. Install the Majestic Mountain LOD Pack for DynDOLOD 3 from the first post and as explained in the "Compatibility" section of docs/DynDOLOD_Manual_SSE.html. The log message is about the textures defined in the NIFs, not about installed textures.

Also read docs\help\LogMessages.html