DynDOLOD 3.00 Alpha 196

[sheson]

5 hours ago, Nutt_lemmings said:

dyndolod64.exe has these erros, not sure how to fix them

Read the first post which entire log of the session, debug log and bugreort.txt if it exists to upload when making posts.

As explained in the documentation DynDOLOD reports certain error in the load order. See https://dyndolod.info/Messages

The osex.pex script maybe be corrupt. Check if it works in game without errors and it doesn't have errors in the papapyrus log. Otherwise try reinstalling/recompiling it.

https://dyndolod.info/Messages/File-Not-Found-Scripts

https://dyndolod.info/Messages/Billboard-For-Model-Has-Different-CRC32

[DoubleYou]

@sheson

I know DynDOLOD allows using LOD via rules for MSTT moveable statics, but since I only have xLODGen for Fallout 4, is there any built-in way to add LOD to MSTT references? For the raider wind turbines, I used fake static references to generate the LODs, but this is less then ideal for a lot of objects, especially as far as mod compatibility is concerned. Fallout 4 has a very large portion of its cars and trucks as MSTT references, since they are designed to exploded if you shoot them. I could develop a script of some sort to generate the fake statics I suppose, but I'd rather save myself the hassle if there already is a way to do this. Could it be possible for xLODGen to automatically use a specific naming structure LOD model (say lod\path_to_model_lod_0.nif) for LOD if I add the Has Distant LOD flag?

[sheson]

3 hours ago, DoubleYou said:

@sheson

I know DynDOLOD allows using LOD via rules for MSTT moveable statics, but since I only have xLODGen for Fallout 4, is there any built-in way to add LOD to MSTT references? For the raider wind turbines, I used fake static references to generate the LODs, but this is less then ideal for a lot of objects, especially as far as mod compatibility is concerned. Fallout 4 has a very large portion of its cars and trucks as MSTT references, since they are designed to exploded if you shoot them. I could develop a script of some sort to generate the fake statics I suppose, but I'd rather save myself the hassle if there already is a way to do this. Could it be possible for xLODGen to automatically use a specific naming structure LOD model (say lod\path_to_model_lod_0.nif) for LOD if I add the Has Distant LOD flag?

xLODGen is a CK replacement LOD generator. It requires LOD models to be defined on base records. Only STAT base records can do that. So only reference that use STAT or SCOL which then use STAT base records can be used for static object LOD generation.

If anything, we would use DynDOLOD for anything beyond that. Either way, that would be a considerable time investment - the list of things to add to xLODGen (bake fake grass for example) and DynDOLOD is already quite long... so  anything like this is still some time in the future.

If you have a fixed list of LOD objects you could add them to the export file manually for the xLODGen or maybe via LOD options file.

Keep in mind though , that the static object LOD will truly be static, it can not move and not change how it looks.

[DoubleYou]

4 hours ago, sheson said:

xLODGen is a CK replacement LOD generator. It requires LOD models to be defined on base records. Only STAT base records can do that. So only reference that use STAT or SCOL which then use STAT base records can be used for static object LOD generation.

If anything, we would use DynDOLOD for anything beyond that. Either way, that would be a considerable time investment - the list of things to add to xLODGen (bake fake grass for example) and DynDOLOD is already quite long... so  anything like this is still some time in the future.

If you have a fixed list of LOD objects you could add them to the export file manually for the xLODGen or maybe via LOD options file.

Keep in mind though , that the static object LOD will truly be static, it can not move and not change how it looks.

Thanks. That confirms what I had expected was the case. I don't want to heap extra work onto that list. I just didn't want to be creating extra work for myself if there already was an easier way to do this.

[Blackread]

After my latest DynDOLOD run I decided to run around the arnimaDuplicate003 worldspace from Beyond Reach to check what the lods look like and if there's anything I would need to fix. While doing this I came across a cell with large reference bugs. The plugin doesn't have large references by default, but I added them myself with the xEdit script. The cell with the bugs is 18 -3. So I started checking the objects in the cell to see if there were any that had the initially disabled flag. I couldn't find any in arnima.esm nor in DynDOLOD.esm or Occlusion.esp, which were the only plugins to edit the cell in question. DynDOLOD.esp does add some tundra stream objects in there that are initially disabled, but since they aren't large refs they shouldn't be the cause of this issue right? There are 8 large refs in the cell, 2 of which are tundra streams. I found 5 objects being affected by this, so it does seem to be a legitimate large reference issue. It also only affects just this cell, neighbouring cells are all completely fine.

Do you have any ideas what might be causing this bug? DynDOLOD didn't report any large ref issues when running it. Here are the relevant log files: https://ufile.io/f/cmfrr

Edit: Noticed that the tundra stream objects might not be affected by this, but I think their LOD is handled a bit differently?

Edited September 7, 2022 by Blackread

[sheson]

1 hour ago, Blackread said:

After my latest DynDOLOD run I decided to run around the arnimaDuplicate003 worldspace from Beyond Reach to check what the lods look like and if there's anything I would need to fix. While doing this I came across a cell with large reference bugs. The plugin doesn't have large references by default, but I added them myself with the xEdit script. The cell with the bugs is 18 -3. So I started checking the objects in the cell to see if there were any that had the initially disabled flag. I couldn't find any in arnima.esm nor in DynDOLOD.esm or Occlusion.esp, which were the only plugins to edit the cell in question. DynDOLOD.esp does add some tundra stream objects in there that are initially disabled, but since they aren't large refs they shouldn't be the cause of this issue right? There are 8 large refs in the cell, 2 of which are tundra streams. I found 5 objects being affected by this, so it does seem to be a legitimate large reference issue. It also only affects just this cell, neighbouring cells are all completely fine.

Do you have any ideas what might be causing this bug? DynDOLOD didn't report any large ref issues when running it. Here are the relevant log files: https://ufile.io/f/cmfrr

Edit: Noticed that the tundra stream objects might not be affected by this, but I think their LOD is handled a bit differently?

Have you tested if problems go away when setting uLargeRefLODGridSize to 5?

Make sure to use latest version to generate large refs  https://github.com/TES5Edit/TES5Edit/blob/dev-4.1.5/Build/Edit Scripts/Skyrim SE - Generate Large References.pas

Only large references can trigger large reference bugs.

[Blackread]

1 hour ago, sheson said:

Have you tested if problems go away when setting uLargeRefLODGridSize to 5?

Make sure to use latest version to generate large refs  https://github.com/TES5Edit/TES5Edit/blob/dev-4.1.5/Build/Edit Scripts/Skyrim SE - Generate Large References.pas

Only large references can trigger large reference bugs.

Tested it now, with uLargeRefLODGridSize=5 there's just LOD models as expected.

The large references were generated with that version of the script.

[sheson]

1 hour ago, Blackread said:

Tested it now, with uLargeRefLODGridSize=5 there's just LOD models as expected.

The large references were generated with that version of the script.

See if there is anything different if you generate large references with the attached version.

Skyrim SE - Generate Large References.pas

[Blackread]

2 hours ago, sheson said:

See if there is anything different if you generate large references with the attached version.

Skyrim SE - Generate Large References.pas 13.08 kB · 2 downloads

I'm afraid not. I removed the old large refs, redid them with this version of the script and regenerated LOD, but that cell was still bugged. But I did notice that a couple initially disabled references that were added with the old script were not added with this one, so that's helpful. With the old one I had to delete them manually afterwards when the DynDOLOD Summary reported them.

[sheson]

2 hours ago, Blackread said:

I'm afraid not. I removed the old large refs, redid them with this version of the script and regenerated LOD, but that cell was still bugged. But I did notice that a couple initially disabled references that were added with the old script were not added with this one, so that's helpful. With the old one I had to delete them manually afterwards when the DynDOLOD Summary reported them.

If the CRC32 of your version of arnima.esm is not EE7FCD5E, send it to me.

[Blackread]

57 minutes ago, sheson said:

If the CRC32 of your version of arnima.esm is not EE7FCD5E, send it to me.

Here it is: https://ufile.io/jews6e37

I have (manually) merged some fixes into it.

[sheson]

3 hours ago, Blackread said:

Here it is: https://ufile.io/jews6e37

I have (manually) merged some fixes into it.

I can not replicate. This is the plugin after generating large refs https://mega.nz/file/MMI0HTwL#o0zRU_fJPzS5iTctFMeN6TUwVnPGXqrwE4i35vJ6x6s

Can you list all plugin that overwrite
Wordspace: arnimaDUPLICATE003 "The Reach" [WRLD:xx000D62]
Persistent Worldspace Cell: [CELL:xx003882] (in arnimaDUPLICATE003 "The Reach" [WRLD:06000D62])
Cell: [CELL:xx01DCBE] (in arnimaDUPLICATE003 "The Reach" [WRLD:06000D62] at 18,-3)

[Blackread]

2 hours ago, sheson said:

I can not replicate. This is the plugin after generating large refs https://mega.nz/file/MMI0HTwL#o0zRU_fJPzS5iTctFMeN6TUwVnPGXqrwE4i35vJ6x6s

Can you list all plugin that overwrite
Wordspace: arnimaDUPLICATE003 "The Reach" [WRLD:xx000D62]
Persistent Worldspace Cell: [CELL:xx003882] (in arnimaDUPLICATE003 "The Reach" [WRLD:06000D62])
Cell: [CELL:xx01DCBE] (in arnimaDUPLICATE003 "The Reach" [WRLD:06000D62] at 18,-3)

I did some quick tests with your plugin and comparing it to mine. With my generated LODs the bug was present with both. With the pregenerated LODs from the mod it was absent with both. I'll do a full LOD regeneration with your plugin just to be sure, as it looks like they are different based on CRC32.

Here are the overwriting plugins:

Worldspace: Beyond Reach - Skyrim Border Tweak.esp, DynDOLOD.esm, Missives - Beyond Reach.esp, Water for ENB - Patch - Beyond Reach.esp, ACMOS - Beyond Reach.esp, Clear Map - Water for ENB Patch.esp (this is my personal plugin patching the latter two together), Synthesis.esp, DynDOLOD.esp, Occlusion.esp

Persistent Worldspace Cell: Beyond Reach - Skyrim Border Tweak.esp, DynDOLOD.esm, Missives - Beyond Reach.esp, DynDOLOD.esp

Cell: DynDOLOD.esm, Occlusion.esp

[sheson]

39 minutes ago, Blackread said:

I did some quick tests with your plugin and comparing it to mine. With my generated LODs the bug was present with both. With the pregenerated LODs from the mod it was absent with both. I'll do a full LOD regeneration with your plugin just to be sure, as it looks like they are different based on CRC32.

Here are the overwriting plugins:

Worldspace: Beyond Reach - Skyrim Border Tweak.esp, DynDOLOD.esm, Missives - Beyond Reach.esp, Water for ENB - Patch - Beyond Reach.esp, ACMOS - Beyond Reach.esp, Clear Map - Water for ENB Patch.esp (this is my personal plugin patching the latter two together), Synthesis.esp, DynDOLOD.esp, Occlusion.esp

Persistent Worldspace Cell: Beyond Reach - Skyrim Border Tweak.esp, DynDOLOD.esm, Missives - Beyond Reach.esp, DynDOLOD.esp

Cell: DynDOLOD.esm, Occlusion.esp

The LOD included with the mod does not mark anything as large reference, so all cells not ever unload any LOD inside  the uLargeRefLODGridSize. The two mountaincliff objects in the screenshot do not have vanilla LOD, though.

I only generated large refs for ArnimaDuplicate003 and none of the other worldspaces.

[Blackread]

2 hours ago, sheson said:

The LOD included with the mod does not mark anything as large reference, so all cells not ever unload any LOD inside  the uLargeRefLODGridSize. The two mountaincliff objects in the screenshot do not have vanilla LOD, though.

I only generated large refs for ArnimaDuplicate003 and none of the other worldspaces.

Ah, that explains.

Well, this is a stubborn one. I've done everything I could think of, but the cell is still bugged:

I've gone to a bare minimum list, I've reset my DynDOLOD rules to the default high, and I switched from papyrusutil to DynDOLOD dll. With vanilla meshes it's not as visible as the LODs are mostly covered, but it's still there. Can't think of anything else to try and fix it.