Jump to content

Recommended Posts

Posted
11 hours ago, David2408 said:

Judging from the multple reports regarding "sticky" LOD glow fx in Solstheim, it seems like this bug is somewhat tied to the Solstheim worldspace, whereas in Tamriel these sticky lights do not occur (as often?). Counting this forum and Nexusmods, there are minimum a dozen individual reports stating that LOD glow fx is sticky in Solstheim worldspace.

If you have a problem or bug, report it as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum

There are currently two different reports about a fake glow issue on Solstheim with Alpha-138.
All other reports that have been made here in the past had been resolved at the time.

I do not use the Comments or Bugs feature on Nexusmods. Posts anywhere else but the official DynDOLOD support forum made by users ignoring the official DynDOLOD documentation, requirements and messages from the tools might as well yell at clouds.

Posted
10 hours ago, Blackread said:

The swap file generated by DynDOLOD is not working. Looks like Base Object Swapper is strict about the letter case: the _SWAP suffix needs to be all upper case, and the file generated by DynDOLOD has it in lower case.

Yeah, I kind of know that. Filename will be fixed next alpha (and test version below)

10 hours ago, Blackread said:

There's also this bit of road sticking through the Whiterun front gate:

Will be added to the list of things not to copy next alpha.

10 hours ago, Blackread said:

Lastly the dark elf lantern glow LOD has made a return. I didn't see them with Alpha-134.

rbovjoq.pngR62hsre.png

EDIDs, respectively:
telmithrynesp_078BF5_DLC2SolstheimWorld_DynDOLOD_OBJECT
telmithrynesp_040FF2_DLC2SolstheimWorld_DynDOLOD_OBJECT

Logs: https://mega.nz/file/YbU33bCS#orQb99fQmxXAdE3TPJ6BRRZRxtbBVdFkyMogM432rqg

Let me know if this is fixed with this test version https://mega.nz/file/sBwU3RxY#P5csfxnK62FKCSZpkj7alOL-VkDkqRhu-idjUlM9HWM

If not upload new log, debug log.

Posted
4 hours ago, sheson said:

For future reference, since you made screenshots for a different generation than the logs, the screenshots are a bit "out of date".

In any case, the logs show you did not check "Fake lights selected world" but only "Fake light child world", so there should not be such fake lights to begin with.
"Fake light selected world" are supposed to not show in the active cells either. But that is not the problem here.

This happens because of some weird interaction with Worldspace Transition Tweaks and will be fixed next alpha version.

Edit: You can test with this test version https://mega.nz/file/sBwU3RxY#P5csfxnK62FKCSZpkj7alOL-VkDkqRhu-idjUlM9HWM in the meantime.

Ah, yes, sorry.  I should have updated the More Informative Console screenshots so it showed the IDs corresponding to the linked log files.  The test version of DunDOLODx64.exe resolved the issue.  Thanks!

image.thumb.png.b2ca3992b694e495a0ed5e52efaf1670.png

Posted
6 minutes ago, Kattmandu said:

Ah, yes, sorry.  I should have updated the More Informative Console screenshots so it showed the IDs corresponding to the linked log files.  The test version of DunDOLODx64.exe resolved the issue.  Thanks!

image.thumb.png.b2ca3992b694e495a0ed5e52efaf1670.png

Great. Thanks for letting us know.

  • Like 1
Posted (edited)

I am using the latest version of DynDOLOD (alpha 139), NG DLL (alpha 12), and Resources (alpha 42)

[Window Title]
DynDOLOD

[Main Instruction]
Error: Assertion failure (C:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 12868)

[Content]


Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

https://www.dropbox.com/scl/fi/v3736fyuo0rvzoa0lk9jt/bugreport.txt?rlkey=3fsty4f8pdjkhvqbuhx4wnbci&dl=0

https://www.dropbox.com/scl/fi/g4mtx3ly6bbtqbgf2lsha/DynDOLOD_SSE_log.txt?rlkey=u9mmgnknse59nfeaeg9f4r33j&dl=0

https://www.dropbox.com/scl/fi/wown1vyzl5xdy3qpk85b6/DynDOLOD_SSE_Debug_log.txt?rlkey=guljdgxq44rta3eti1qqdzgss&dl=0

Will you please tell me what I need to do to fix this?

Edited by BuddyKidd
Posted

Thank you for your quick response on this. I've been checking over everything. Sorry for not posting correctly. 

The issue I was having was caused by incomplete grass cache I believe. I have regenerated just now, after regenerating my grass cache again and the atlas includes the grass.

If anyone else is having the same issue: Check your grass cache is complete for each world you have generated it for if you've checked everything else.

It works really well! I'm very happy with the results, can't sing TexGen and DynDOLOD's praises enough.

Posted
1 hour ago, Lulie said:

Thank you for your quick response on this. I've been checking over everything. Sorry for not posting correctly. 

The issue I was having was caused by incomplete grass cache I believe. I have regenerated just now, after regenerating my grass cache again and the atlas includes the grass.

If anyone else is having the same issue: Check your grass cache is complete for each world you have generated it for if you've checked everything else.

It works really well! I'm very happy with the results, can't sing TexGen and DynDOLOD's praises enough.

That is the first thing the https://dyndolod.info/Help/Grass-LOD#No-Grass-LOD-Check-List suggests to check.

Posted

Skyrim SE, DynDOLOD 3a134

Hello, I'm the crazy guy who is obsessed with trees (or lack thereof) outside the walls of Solitude in SolitudeWorld not matching the Tamriel ultra tree LODs, and who made a big fuss about them in the past. I'm very grateful for the Parent > Child feature - this is a dream come true, so thank you very much. I'm also grateful for moving the vanilla occlusion planes further away so that more stuff is visible outside the walls in the child worldspaces. This is beautiful.

I'm trying to understand why some references are not being copied to child worldspace when Parent > Child is used. Specifically, some USSEP tree references are not copied to SolitudeWorld, even though object LOD is generated for them in Tamriel worldspace.

Relevant DynDOLOD_SSE_Debug_log.txt log lines for [REFR:05063113]:

[07:39] [BuildReferences] <Debug: Meshes\landscape\trees\treepineforestsnow03.nif_-670_1074_-52_105 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))>
[...]
[08:19] [ApplyReferenceUpdates] <Debug: Processing Default 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))>
[...]
[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))>

What causes the Ignoring master message above? I couldn't find anything in [..]\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_[GAME MODE]_* config files that would cause this.

These references do not appear in DynDOLOD_SSE_ChildworldMatches.txt so there is another reason for them to be skipped.

Trees added by USSEP in [CELL:0000925A]:

image.png

Trees copied by DynDOLOD to DynDOLOD.esm in [CELL:0004E3DC] (they're all from Skyrim.esm):

image.png

Is there a separate log for Parent > Child copies? It looks like [..]\DynDOLOD\Logs\DynDOLOD_SSE_ChildworldCopies_Tamriel.txt is only for Child > Parent copies.

Thank you.

  • +1 1

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

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