Jump to content

DynDOLOD 3.00 Alpha 180


sheson

Recommended Posts

I have followed the install instructions, updated my video drivers. Ideas? Thank you!

[Window Title]
TexGen

[Main Instruction]
Error: OpenGL: E:\DynDOLOD\TexGen_Output\textures\lod\impextrubble01lod framebuffer objects unsupported.

[Content]


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

Clean install the latest recommended/WHQL (not optional and not beta) graphics drivers only without any bloatware.

If the issue persists, posts a problem report on the official DynDOLOD support forum.

[Exit TexGen]

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

TexGen_SSE_log.txt

Link to comment
Share on other sites

Just now, rmcgloth said:

I have followed the install instructions, updated my video drivers. Ideas? Thank you!

[Window Title]
TexGen

[Main Instruction]
Error: OpenGL: E:\DynDOLOD\TexGen_Output\textures\lod\impextrubble01lod framebuffer objects unsupported.

[Content]


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

Clean install the latest recommended/WHQL (not optional and not beta) graphics drivers only without any bloatware.

If the issue persists, posts a problem report on the official DynDOLOD support forum.

[Exit TexGen]

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

TexGen_SSE_log.txt 471.24 kB · 0 downloads

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to also upload.

As explained in the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, click "Click on this link for additional explanations and help for this message" which should open https://dyndolod.info/Messages/Exceptions, scroll down to https://dyndolod.info/Messages/Exceptions#OpenGL.

As explained on the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search, use search, check older posts.
Assuming you have an NVIDIA card/driver, you will find an interim workaround https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-155/?do=findComment&comment=275186 and the information that this is caused by latest NVIDIA drivers. There are further post with test versions to see if the driver issue can be worked around but still ongoing.

Link to comment
Share on other sites

16 minutes ago, sheson said:

Upload log and debug log from this test version https://mega.nz/file/5Bg0BT5T#020KpwisvQdHItYhzEqqddfpYie3b9MpAwiyio-aQZA

Ran it three times without any issues with KeepRenderer=0 in the configuration.

Just in case, I ran it once without KeepRenderer=0 as well, and encountered no issues either.

Attaching the logs from all four runs.

Logs.success.KeepRenderer0.1.zip Logs.success.KeepRenderer0.2.zip Logs.success.KeepRenderer0.3.zip Logs.success.noKeepRenderer.zip

Link to comment
Share on other sites

5 hours ago, adancau said:

Ran it three times without any issues with KeepRenderer=0 in the configuration.

Just in case, I ran it once without KeepRenderer=0 as well, and encountered no issues either.

Attaching the logs from all four runs.

Logs.success.KeepRenderer0.1.zip 565.56 kB · 1 download Logs.success.KeepRenderer0.2.zip 568.91 kB · 1 download Logs.success.KeepRenderer0.3.zip 571.45 kB · 1 download Logs.success.noKeepRenderer.zip 575.33 kB · 1 download

Interesting. Thanks for testing. Will keep the changes for next alpha version.

Link to comment
Share on other sites

Having a consistent CTD all of a sudden. Crash at game load, not at menu. No changes to plugins except some changes to weather. Crash logs all mention Dyndolod and each one has different other keywords, ex: NiNode, Lanterns of Skyrim II, AI Overhaul, etc.

No crash without Dyndolod.  Using the same Dyndolod preset I always have. Tried an older version but same crash. Same for all MO2 profiles and a new profile. Summary has the same messages it always has, which I still can't figure how to fix. But the game ran fine for months.

The only thing I noticed was a mention of an area out of bounds. 

Went to any relevant mod pages and checked posts, also Reddit, got no replies. So here I am.

There was no bug report. I can submit more of my 6 crash logs if needed.

Debug log since it is huge. https://ufile.io/amky7nxb   One of today's  crash logs  https://ufile.io/7klb9wob

DynDOLOD_SSE_log.txt crash-2023-10-24-04-09-48.log

Link to comment
Share on other sites

33 minutes ago, mitzie92 said:

Having a consistent CTD all of a sudden. Crash at game load, not at menu. No changes to plugins except some changes to weather. Crash logs all mention Dyndolod and each one has different other keywords, ex: NiNode, Lanterns of Skyrim II, AI Overhaul, etc.

No crash without Dyndolod.  Using the same Dyndolod preset I always have. Tried an older version but same crash. Same for all MO2 profiles and a new profile. Summary has the same messages it always has, which I still can't figure how to fix. But the game ran fine for months.

The only thing I noticed was a mention of an area out of bounds. 

Went to any relevant mod pages and checked posts, also Reddit, got no replies. So here I am.

There was no bug report. I can submit more of my 6 crash logs if needed.

Debug log since it is huge. https://ufile.io/amky7nxb   One of today's  crash logs  https://ufile.io/7klb9wob

DynDOLOD_SSE_log.txt 2.59 MB · 0 downloads crash-2023-10-24-04-09-48.log 226.6 kB · 0 downloads

Enable/upload the papyrus log as explained at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Upload the c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log as explained at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing

https://dyndolod.info/Messages/Worldspace-Bounds
https://dyndolod.info/Messages/Deleted-Reference
https://dyndolod.info/Messages/Root-Block

https://dyndolod.info/Help/Summary-Of-Messages
In case a specific message needs further explanation, help is required or to report a problem, search for or report it on the official DynDOLOD support forum.

If the order of plugins or their contents changed, generate LOD for the current load order. Could be unresolved form id in a DynDOLOD record after changing plugins.

Link to comment
Share on other sites

Well I don't know where MO2 put the Papyrus logs but there not in Users or Documents. Just  some old ones from 2021. I checked the Skyrim ini's and made sure to enable logging but can't find them, even in search. Ran the game and of course, a crash. I'll have to continue to search.

Link to comment
Share on other sites

45 minutes ago, mitzie92 said:

Well I don't know where MO2 put the Papyrus logs but there not in Users or Documents. Just  some old ones from 2021. I checked the Skyrim ini's and made sure to enable logging but can't find them, even in search. Ran the game and of course, a crash. I'll have to continue to search.

Make sure to edit the correct Skyrim.ini to enable logging for the currently used profile. MO2 menu Tools / Tool Plugin / INI Editor.

Also read the rest of my post.

Link to comment
Share on other sites

On 10/27/2023 at 11:02 PM, Mousetick said:
  • Test 1: Same as previous test 1 where DynDOLOD DLL attempts to disable 7D3022EC several times unsuccessfully. Papyrus log doesn't contain anything of interest: Papyrus.0.log.7z

Any idea why the reference fails to disable?

Then I made 2 new cleaned saves (one inside Honningbrew Meadeary, load-door within FarGrid, the other inside Frostfruit Inn, load-door outside FarGrid) and did all the tests you suggested. Everything worked fine and as expected, so I'll skip the details.

I thought the issue is not with the initial enabling of the initially disabled dynamic LOD, rather at some point the dynamic LOD should be disabled but is not for some reason and this leaves it into a "wonky" state. Then I thought about possible scenarios that might cause this. And I was able to reproduce it from scratch, yeah!

Make sure you're seated comfortably because this is a bit convoluted.

  • I use the Clockwork mod. It provides a teleportation system in the form of access terminals at each city and a central hub. To fast-travel from one city to another, one enters the departure terminal, teleports to the hub, then from the hub teleports to the destination terminal. Each terminal and the hub are separate interior cells.
  • The Whiterun terminal is located near the Whiterun gates. Its load-door is within the FarGrid containing 7D3022EC, but outside the NearGrid.
  • The Windhelm terminal is located at the Windhelm docks. Its load-door is obviously outside the FarGrid containing 7D3022EC.

The steps I used to reproduce:

  1. Load clean save with DynDOLOD plugins enabled, inside Honningbrew Meadery.
  2. Exit the meadery. 7D3022EC Initially Disabled -> Enabled.
  3. Go to the Whiterun teleportation terminal and enter it. 7D3022EC still Enabled.
  4. Teleport to Clockwork Hub. 7D3022EC still Enabled.
  5. Teleport to Windhelm terminal. 7D3022EC still Enabled.
  6. Exit Windhelm terminal. We're now in Tamriel on the Windhelm Docks, very far from the Whiterun Watchtower. 7D3022EC still Enabled.
  7. Re-enter Windhelm terminal. Teleport to Hub then back to Whiterun terminal. Exit Whiterun terminal. 7D3022EC still Enabled.
  8. Walk to the Whiterun Watchtower. 7D3022EC still Enabled. And same disabling failures as before:
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif

There are about twice as many disabling attempts compared to test 1 so I guess DynDOLOD tried to disable it on two occasions, but I have no idea when the first one occurred. Perhaps step 6? I guess I can rerun the test and quit after step 6 to confirm.

Thanks.

There is really no reason why going into interiors and come out somewhere else should affect references in any way.

I installed both mods, enabled the terminal in order to be able to recreate the steps but can not reproduce the problem.

The references are disabled when entering Tamriel from the Windhelm terminal. When going back through the terminal and entering Tamriel from the Whiterun terminal, they enable and then disable when walking to the tower as expected.
The dynamic LOD references do not have any connections to mods/plugins, so there are no direct relationships to other plugins/records, like for example the enable parent in Environs - Whiterun Watchtower.esp that could have an effect.

Can you test/confirm that you can disable the reference from console after entering Tamriel from the Windhelm terminal? Does this have an affect on subsequent travels?

Is there anything different in the behavior or DynDOLOD.log when using this version? https://mega.nz/file/ZIZxAA6J#GvwoZvriC0gSQcn_luqB0QcsksBSuJhZqVsGpV1dOW0

Link to comment
Share on other sites

3 hours ago, sheson said:

The dynamic LOD references do not have any connections to mods/plugins, so there are no direct relationships to other plugins/records, like for example the enable parent in Environs - Whiterun Watchtower.esp that could have an effect.

I agree. There is nothing special about Environs - Whiterun Watchtower, it's a red herring. It just so happens that it produces a bunch of dynamic LOD references that are enabled and then fail to disable after a specific sequence of events and under specific conditions that remain to be determined. The same issue could probably be reproduced with any other enabled dynamic LOD reference, using the same sequence of events under the same conditions.

3 hours ago, sheson said:

Is there anything different in the behavior or DynDOLOD.log when using this version?

This made no difference at all.

3 hours ago, sheson said:

Can you test/confirm that you can disable the reference from console after entering Tamriel from the Windhelm terminal?

Yes. Annotated DynDOLOD.log:

Spoiler
Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt
Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Tamriel.txt
# Exit Whiterun meadery
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Approach Whiterun watchtower (Disable succeeds)
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Go to Whiterun terminal
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Enter Whiterun terminal and teleport to Windhelm
# Exit Windhelm terminal (Disable fails)
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Manually disable 7D3022EC in console
# Enter Windhelm terminal and teleport to Whiterun
# Exit Whiterun terminal (Enable succeeds, but repeated 3 times?)
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Approach Whiterun watchtower (Disable succeeds)
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif

 

3 hours ago, sheson said:

Does this have an affect on subsequent travels?

No. Repeating the same travel again after "fixing" the reference by manually disabling it in the console, results in the same failure. Annotated DynDOLOD.log:

Spoiler
Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt
Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Tamriel.txt
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Enter Whiterun terminal, teleport to Windhelm
# Exit Windhem terminal (Disable fails)
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Manually disable 7D3022EC in console
# Enter Windhelm terminal, teleport to Whiterun
# Exit Whiterun terminal
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Enable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
# Enter Whiterun terminal, teleport to Windhelm
# Exit Windhelm terminal (Disable fails again)
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif
Disable - Reference 7D3022EC Base 5A231849 lod\clutter\stockade\stockadegate01_lod_0.nif

 

Other points to consider:

  • I chose Windhelm for my test, but I confirmed that the same failure occurred when travelling from Whiterun to the Solitude terminal. I suspect other destinations would fail in the same way.
  • Once the dynamic LOD reference is in the 'failed disable' state, it remains that way forever (unless manually disabled in console) and its failed state persists in the (co)save files across sessions.
  • If you can't reproduce there is probably another factor/mod/component involved. TBD.

Thanks.

 

Update: I just reproduced the issue by simply taking the carriage from Whiterun to Windhelm. Duh.

I should have tried the simplest way to fast travel first instead of seeking the most convoluted one. My apologies for making you install Clockwork and wasting your time with it.

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.