DynDOLOD 3.00 Alpha 182

[S-Matrix]

4 hours ago, sheson said:

What the crash log seems to point to is Architecture\Solitude\SBlackSmith.nif which is used by the mentioned references and base records defined or overwritten by DynDOLOD plugins.

Test if the NIF opens in NifSkope, run it through CAO or try removing or replacing it.

If you found that the NIF really causes the crash and it comes that way with a mod, then upload the NIF as is.

Hi sheson, thanks for the reply - as per your suggestion I checked to make sure the mesh would open properly in NifSkope, and it did indeed do so.

Next, using MO2's "Data" tab, I was able to see each mod in my load order that was contributing a version of the mesh; the one provided by "Flickering Meshes Fix" was the overriding version, so I isolated and then deactivated that file from the mod, and returned to the problem area, but the issue persisted. Before trying CAO, I decided to try removing the version of the mesh provided by "Assorted Mesh Fixes", which was next in line in terms of override/use by the game, but the crash still occurred. I repeated the process one last time with the "Landscape and Water Fixes" version of the mesh, mostly as a sanity check - alas: crash.

Honestly, I'm not the most knowledgeable about troubleshooting mesh issues, especially with a completed DynDOLOD output in the mix, so this was mostly just me trying to brute force possible resolutions without being able to parse/tinker with the DynDOLOD output itself. While it yielded no results on my end, maybe this info can help with your more seasoned diagnosis. It indicates to me (and again, I'm pretty inexperienced) that the construction of the mesh itself isn't the root cause of the crash, since even across multiple different versions of the mesh, sblacksmith.nif still appears in the crashlog.

If it does end up being related to DynDOLOD, would I need to regenerate LOD in order to test solutions? Is there a "mini-run" I can do, localized to the Solitude region, to save on generation time, in that case? Let me know if anything jumps out about the issue, or if there's some other things I can try in the meantime. Thanks!

[sheson]

27 minutes ago, S-Matrix said:

Hi sheson, thanks for the reply - as per your suggestion I checked to make sure the mesh would open properly in NifSkope, and it did indeed do so.

Next, using MO2's "Data" tab, I was able to see each mod in my load order that was contributing a version of the mesh; the one provided by "Flickering Meshes Fix" was the overriding version, so I isolated and then deactivated that file from the mod, and returned to the problem area, but the issue persisted. Before trying CAO, I decided to try removing the version of the mesh provided by "Assorted Mesh Fixes", which was next in line in terms of override/use by the game, but the crash still occurred. I repeated the process one last time with the "Landscape and Water Fixes" version of the mesh, mostly as a sanity check - alas: crash.

Honestly, I'm not the most knowledgeable about troubleshooting mesh issues, especially with a completed DynDOLOD output in the mix, so this was mostly just me trying to brute force possible resolutions without being able to parse/tinker with the DynDOLOD output itself. While it yielded no results on my end, maybe this info can help with your more seasoned diagnosis. It indicates to me (and again, I'm pretty inexperienced) that the construction of the mesh itself isn't the root cause of the crash, since even across multiple different versions of the mesh, sblacksmith.nif still appears in the crashlog.

If it does end up being related to DynDOLOD, would I need to regenerate LOD in order to test solutions? Is there a "mini-run" I can do, localized to the Solitude region, to save on generation time, in that case? Let me know if anything jumps out about the issue, or if there's some other things I can try in the meantime. Thanks!

Make sure to enable archive parsing in MO2 Settings, tab Workarounds.
Once you are down to the Unofficial Patch or the vanilla Meshes0.bsa for the NIF, we can probably assume that the NIF is OK.

In that case start xEdit and load the entire load order. Then enter 1D0422B9 in the form ID field top left and hit enter so the right window shows the record. In case DynDOLOD.esm is not loaded at load order 1D, adjust the first two digits accordingly to what is shown in the left tree view for DynDOLOD.esm.
Scroll to the very right and make a screenshot. If necessary also scroll down and make more screenshots.
Repeat with form ID 0008618F
Upload those screenshots.

[S-Matrix]

7 minutes ago, sheson said:

Make sure to enable archive parsing in MO2 Settings, tab Workarounds.
Once you are down to the Unofficial Patch or the vanilla Meshes0.bsa for the NIF, we can probably assume that the NIF is OK.

In that case start xEdit and load the entire load order. Then enter 1D0422B9 in the form ID field top left and hit enter so the right window shows the record. In case DynDOLOD.esm is not loaded at load order 1D, adjust the first two digits accordingly to what is shown in the left tree view for DynDOLOD.esm.
Scroll to the very right and make a screenshot. If necessary also scroll down and make more screenshots.
Repeat with form ID 0008618F
Upload those screenshots.

https://imgur.com/a/xNfWHAC

Let me know if this is everything as you wanted it/if you need anything else at the moment, and I appreciate you sticking with this.

[sheson]

42 minutes ago, S-Matrix said:

https://imgur.com/a/xNfWHAC

Let me know if this is everything as you wanted it/if you need anything else at the moment, and I appreciate you sticking with this.

All good. Records are fine.

To double check if the records or NIF are causing the crash, make a backup of DynDOLOD.esm, bring up 1D0422B9 in xEdit again and then right click DynDOLOD.esm in the header column of the right window that shows the record, select remove, save.

If there is still a crash, upload the new crash log. If there is not crash just let me know.

[S-Matrix]

15 minutes ago, sheson said:

All good. Records are fine.

To double check if the records or NIF are causing the crash, make a backup of DynDOLOD.esm, bring up 1D0422B9 in xEdit again and then right click DynDOLOD.esm in the header column of the right window that shows the record, select remove, save.

If there is still a crash, upload the new crash log. If there is not crash just let me know.

Voila, that's fixed it! Thanks so much Sheson, and let me know if you need anything else from my end to figure out the root cause of this, or if there's anything else I need to do as far as generation is concerned now that the ESM is edited.

[sheson]

30 minutes ago, S-Matrix said:

Voila, that's fixed it! Thanks so much Sheson, and let me know if you need anything else from my end to figure out the root cause of this, or if there's anything else I need to do as far as generation is concerned now that the ESM is edited.

That was just a troubleshooting step.

So it still crashed with the NIF from unofficial patch or the vanilla NIF? Make sure in MO2 right window data tab.
In that case we should have a look at the used textures.

To list the used textures, open the Asset Browser in xEdit with CTRL+F3
Enter sblacksmith.nif into the filter field.
Highlight the found file in the list, the status at the bottom will then list all used textures.
Check with MO2 right data tab again which mods the used textures come from.

[S-Matrix]

10 minutes ago, sheson said:

So it still crashed with the NIF from unofficial patch or the vanilla NIF? Make sure in MO2 right window data tab.
In that case we should have a look at the used textures.

That's correct. Here's the list of textures you asked for: https://imgur.com/a/aK9UYFE
As you can probably see, we have a lot of conflicts; however, these conflicts are all (I hovered over each one to be sure) between Mrf's Solitude and Kartoffel's Cleaned Textures. This specific conflict is completely expected, as Kartoffel's mod covers every texture in the game and I'm using it as a base.

The one exception to this, as you also probably noticed, is in the case of swindow01_g.dds (which I assume is a glowmap or something similar). TexGen Output takes precedence here, but that texture is also found in USSEP, the lighting mod "Lux", and then again in Mrf's Solitude. My amateur's hunch is that this may be significant, given that Wizkid's mod for ENB window glow was also implicated in the crashlogs I'd posted.

Keep me posted with new things to look at and report back with.

[sheson]

46 minutes ago, S-Matrix said:

That's correct. Here's the list of textures you asked for: https://imgur.com/a/aK9UYFE
As you can probably see, we have a lot of conflicts; however, these conflicts are all (I hovered over each one to be sure) between Mrf's Solitude and Kartoffel's Cleaned Textures. This specific conflict is completely expected, as Kartoffel's mod covers every texture in the game and I'm using it as a base.

The one exception to this, as you also probably noticed, is in the case of swindow01_g.dds (which I assume is a glowmap or something similar). TexGen Output takes precedence here, but that texture is also found in USSEP, the lighting mod "Lux", and then again in Mrf's Solitude. My amateur's hunch is that this may be significant, given that Wizkid's mod for ENB window glow was also implicated in the crashlogs I'd posted.

Keep me posted with new things to look at and report back with.

Can you make a screenshot of the asset browser showing the list of used textures as well?

[S-Matrix]

5 minutes ago, sheson said:

Can you make a screenshot of the asset browser showing the list of used textures as well?

Here it is: https://imgur.com/a/7Df35ed
Not sure if it's normal for there to be two instances of it appearing in the asset window search results, but the assets listed for both entries are the exact same.

[sheson]

13 minutes ago, S-Matrix said:

Here it is: https://imgur.com/a/7Df35ed
Not sure if it's normal for there to be two instances of it appearing in the asset window search results, but the assets listed for both entries are the exact same.

That's odd that it shows twice. Which xEdit version are you using? This is a Windows OS, not Wine/Proton on Linux?

Before we spend much time on the textures lets do another check first:

Make a backup of DynDOLOD.esm. Start xEdit and bring up 1D0422B9 again, double click on the entry SBlackSmith [STAT:0008618F] in the row NAME - Base row in order to edit it. Type 3B then hit enter to change it to the XMaker [STAT:0000003B].

If that does not crash, restore DynDOLOD.esm, start xEdit and this time bring up 0008618F. Double clock the entry Architecture\Solutide\SBlackSmith.nif in the row MODL - Model FileName in the right column for DynDOLOD.esp and replace it with MarkerX.nif (it is just the filename without folders). Test if that still crashes.

[S-Matrix]

1 hour ago, sheson said:

That's odd that it shows twice. Which xEdit version are you using? This is a Windows OS, not Wine/Proton on Linux?

Before we spend much time on the textures lets do another check first:

Make a backup of DynDOLOD.esm. Start xEdit and bring up 1D0422B9 again, double click on the entry SBlackSmith [STAT:0008618F] in the row NAME - Base row in order to edit it. Type 3B then hit enter to change it to the XMaker [STAT:0000003B].

If that does not crash, restore DynDOLOD.esm, start xEdit and this time bring up 0008618F. Double clock the entry Architecture\Solutide\SBlackSmith.nif in the row MODL - Model FileName in the right column for DynDOLOD.esp and replace it with MarkerX.nif (it is just the filename without folders). Test if that still crashes.

Using xEdit 4.04, I believe - I saw today that there's an update available, so it's probably a good idea to move to the newest version. Gonna be afk for an hour or two, so I'll post with news later in the day.

[aristotle]

I'm having difficulty with the BSHeartland worldspace for DynDOLOD.  The Beyond Skyrim people gave an answer in their bug report that their own custom LODs are preferred to those in DynDOLOD, and that they advise not generating LOD files via DynDOLOD for the Beyond Skyrim mod.

So I followed your instructions and figured out how to make the BSHeartland worldspace show up in the list of worldspaces available for DynDOLOD.  I unticked BSHeartland in the selection window, selected everything else, and ran DynDOLOD.

Except it didn't work.  At the end, I got the same list of warnings about missing meshes and textures in BSHeartland.  I'm sure I unticked it, but it appears to have ignored me.  Don't know what to do except uninstall Beyond Skyrim.

Edited November 30, 2023 by aristotle

[sheson]

5 hours ago, aristotle said:

I'm having difficulty with the BSHeartland worldspace for DynDOLOD.  The Beyond Skyrim people gave an answer in their bug report that their own custom LODs are preferred to those in DynDOLOD, and that they advise not generating LOD files via DynDOLOD for the Beyond Skyrim mod.

So I followed your instructions and figured out how to make the BSHeartland worldspace show up in the list of worldspaces available for DynDOLOD.  I unticked BSHeartland in the selection window, selected everything else, and ran DynDOLOD.

Except it didn't work.  At the end, I got the same list of warnings about missing meshes and textures in BSHeartland.  I'm sure I unticked it, but it appears to have ignored me.  Don't know what to do except uninstall Beyond Skyrim.

https://dyndolod.info/Mods/Beyond-Skyrim-Bruma

Changing the setting to show the worldspace in the list and then not ticking it, means that nothing is done differently. LOD for the worldspace will still not be generated.

Changing the setting does not change the fact that the mod has missing assets. In this case that typically won't affect LOD being generated for other worldspaces.

[TioDrakul]

On 11/27/2023 at 2:11 PM, sheson said:

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 problem reports.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make use full screenshots of the full model with more informative console, both with and without DynDOLOD enabled.

By default DynDOLOD is not doing anything to the vanilla reference for the bridge when running in the TES5 game mode.
When DynDOLOD is running in TES5 game mode, it does not load any patch files for the SSE game mode.
The cause of the problem will be most likely something else entirely.
Making manual edits to generated files or patches is not really solving the cause of the problem.
Making baseless assumptions without having any understanding how anything works is not going to help with finding the actual cause of problems. Proper troubleshooting with the help of the log files and screenshots is.

Do not use DynDOLOD and do not participate in the alpha test until you are able to meet the requirements to do so which includes being able to provide repeatedly requested logs and screenshots so the problem can be properly troubleshooted and solved.

 

Honestly, why would I waste my time on that? I've already fixed my problem myself, now I understand what you did and how you did it so I can fix similar problems in the future, and most importantly you've already decided it's not a problem with your plugin even though you haven't seen any logs yet, so you wouldn't even read said log.

 

[sheson]

1 hour ago, TioDrakul said:

 

Honestly, why would I waste my time on that? I've already fixed my problem myself, now I understand what you did and how you did it so I can fix similar problems in the future, and most importantly you've already decided it's not a problem with your plugin even though you haven't seen any logs yet, so you wouldn't even read said log.

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 problem reports.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make use full screenshots of the full model with more informative console, both with and without DynDOLOD enabled.

If you use DynDOLOD and participate in the alpha test, then you are required to upload the repeatedly requested logs and screenshots. This will ensure nobody, including you is wasting time doing useless things. You do not seem to know how anything works. You do not seem to know how to properly troubleshoot the problem to find the actual cause. So you already wasted days.

You are wasting time by actively refusing to simply upload the repeatetly requested logs and screenshots. The actual cause could have probably been found and fixed by now.

You are wasting time by making up reasons for the cause of the problem. I am trying to reply to these assumptions as best as possible by explaining how things normally work for everyone else. It doesn't help anyone, including you, to find the actual cause of the problem.

I have not decided anything because you did not upload any of the repeatedly requested logs and screenshots.

I suggest to read the past decade of posts being made here. You are making a fool of yourself with your attitude, behavior and and wrong claims.

If you know how to fix the actual cause of the problem in DynDOLOD, then provide your fix so it can be applied for everyone.

Do not use DynDOLOD and do not participate in the alpha test until you are able to meet the requirements.