Jump to content

DynDOLOD 3.00 Alpha 180


sheson

Recommended Posts

13 minutes ago, Mousetick said:

I'll give you a proper report with screenshots, console info, logs etc. but it's going to take a long while. I'd need to update to Alpha 139 first, I guess.

Meanwhile, please read my description in plain English which should be pretty clear without looking at pictures:

  • Tree ref added by USSEP in Tamriel:
[REFR:05063113] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Temporary Children of [CELL:0000925A] (in Tamriel "Skyrim" [WRLD:0000003C] at -17,26))
  • Copy of previous tree ref, in SolitudeWorld, also added by USSEP:
[REFR:0506313A] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Persistent Children of [CELL:00037EE6] (in SolitudeWorld "Solitude" [WRLD:00037EDF]) at -17,26)
  • Relevant excerpts of debug log:
[01:49] [DynDOLODGenerate] <Debug: 101	unofficial skyrim special edition patch.esp;0006313A None None None None None Delete Unofficial Skyrim Special Edition Patch.esp [REFR:0506313A] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Persistent Children of [CELL:00037EE6] (in SolitudeWorld "Solitude" [WRLD:00037EDF]) at -17,26)>
[...]
[04:55] [ApplyReferenceRules] <Debug: Processing Unofficial Skyrim Special Edition Patch.esp [REFR:0506313A] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Persistent Children of [CELL:00037EE6] (in SolitudeWorld "Solitude" [WRLD:00037EDF]) at -17,26)>
[04:55] [DisableReference] <Notice: Disabled Unofficial Skyrim Special Edition Patch.esp [REFR:0506313A] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Persistent Children of [CELL:00037EE6] (in SolitudeWorld "Solitude" [WRLD:00037EDF]) at -17,26)>
[04:55] [CopyMainRecordToFile] <Debug: Processing DynDOLOD.esm Unofficial Skyrim Special Edition Patch.esp [REFR:0506313A] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Persistent Children of [CELL:00037EE6] (in SolitudeWorld "Solitude" [WRLD:00037EDF]) at -17,26)>
[...]
[16:13] [AddMissingReferences] <Debug: Ignoring master Unofficial Skyrim Special Edition Patch.esp [REFR:05063113] (places TreePineForestSnow03 [TREE:0005C070] in GRUP Cell Temporary Children of [CELL:0000925A] (in Tamriel "Skyrim" [WRLD:0000003C] at -17,26))>
  • Commentary:
    • At 1:49, DynDOLOD acknowledges the Delete rule from DynDOLOD_SSE_unofficialskyrimspecialeditionpatchesp.ini concerning [REFR:0506313A].
    • At 4:55, DynDOLOD applies that rule by disabling [REFR:0506313A] in DynDOLOD.esm. After that point, [REFR:0506313A] no longer "exist" in SolitudeWorld, it's not visible anymore. [REFR:05063113] in Tamriel has become "orphaned": it no longer has a matching copy in SolitudeWorld, since [REFR:0506313A] has been permanently disabled.
    • At 16:13, DynDOLOD decides to "Ignore master" for [REFR:05063113] because it apparently doesn't see that its copy [REFR:0506313A] has been previously disabled by DynDOLOD.esm. That evaluation is incorrect, as there is effectively no visible copy for [REFR:05063113] in SolitudeWorld anymore.

Repeat each step above for each and every tree reference added by USSEP in Tamriel, with its corresponding copy in SolitudeWorld disabled by DynDOLOD_SSE_unofficialskyrimspecialeditionpatchesp.ini.

End result: USSEP tree references in the cells outside the walls of Solitude have Tamriel LODs (as expected). Inside SolitudeWorld, when those LODs fade, no full models appear for those trees, since their copy was disabled and no new copy was made by DynDOLOD during Parent > Child.

Full logs (using Alpha 134) here if you'd like to take a look: https://drive.google.com/file/d/19EQbVwyzUSpR3ReaOWITDJFmMuKv5JYF/view

Thanks.

If there are visual issues in the game, then make useful screenshots of them and upload those screenshots together with the log and debug log for that generation.
Always use the latest version. Maybe something changed in the meantime, maybe not. You do not have to do a full generation. Just Tamriel without extra options Occlusion etc. A small test load order with minimum required mods.

Link to comment
Share on other sites

On 8/29/2023 at 5:06 PM, sheson said:

DynDOLOD does not change terrain/land or generates terrain LOD.

What makes you believe DynDOLOD has anything to do with the gap between a reference that is placed by a 3rd patry plugins and the terrain/land?
What rudimentary troubleshooting have you done? Does the problem go away without DynDOLOD output or plugins in the load order?

Hi,

as you have released two? new Versions i will investigate this matter further after i have done a new generation. 

It would be a waste of our time to chase ghosts in different/outdated software versions :) 

If the matter persists, i will take a look in xedit etc. and will posts the data.

 

Thx 

Link to comment
Share on other sites

I had some of the grass cache but not ALL of the grass cache for Tamriel. I had some issues with MO2 when generating towards the end of the process the first time I did it. So I thought this first point was OK because I did indeed have grass cache files.

Link to comment
Share on other sites

Tried to update my modding setup and ran DynDOLOD and this error came up:

Error: Error processing cell CWILustratorium [CELL:6137F33A] (in CWILustratoriumWorld "Lustratorium" [WRLD:6137F110] at 28,27): Invalid argument.

Anything I can do so this doesn't come up the next time I run it?

Link to comment
Share on other sites

1 hour ago, JakoJako said:

Tried to update my modding setup and ran DynDOLOD and this error came up:

Error: Error processing cell CWILustratorium [CELL:6137F33A] (in CWILustratoriumWorld "Lustratorium" [WRLD:6137F110] at 28,27): Invalid argument.

Anything I can do so this doesn't come up the next time I run it?

See the first post of this DynDOLOD 3 Alpha thread and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug and bugreport.txt (if it exists) to upload.

Link to comment
Share on other sites

1 hour ago, JakoJako said:

I installed a few patches for ICOW and reran DynDOLOD, which seemed to fix the issue.

Anyways, thank you!

It prevents the issue from happening, because the load order is different now. Upload the old log, bugreport.txt with the error.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.