DynDOLOD 3.00 Alpha 198

[Velezarius2]

Thanks for the quick response! I don't know what the reason is, but after your answer... everything worked! Not a single mistake with textures!!! This is some kind of mysticism... or magic. Thanks again so much for DynDOLOD and your help!

[mooit]

22 hours ago, z929669 said:

SO ...

since you have had your LOD issue with alpha 97, you have since run alpha 95 again to confirm it works? You have run alpha 95 AFTER your alpha 97 failed run?

If not, then you cannot say that alpha 95 works and alpha 97 is the source of your issue. The source of your issue is in your configuration as has been mentioned several times.

Why can't you consider that you have made a simple mistake that has nothing to do with DynDOLOD?

I see what the issue is now, but I don't understand why it happens like this.

If I backup/rename my DynDOLOD and xLODGen directories and extract the same versions, when I run xLODGen, TexGen, DynDOLOD from these new directories and put the new output in MO2 and start up SSE it won't work, or if I go to a new version of DynDOLOD it's not working, like how I'm running into this problem.

I don't understand why, but this is the issue, I'm 100% certain of it, because I've been seeing this happen in the past several times, but I didn't really think about it again, as yes, I thought my setup/configurations weren't correct, but they are, as I explained, because I can make it work, it just ends up breaking like this, and then I have to just keep juggling things around, which I have no idea what starts to make it work again, but it can be a real major event, trying to get a working version over.

Here's a screen shot of SSE working with Alpha95.

Alpha95 — Freeimage.host

Now all I do is delete the xLODGen, TexGen, DynDOLOD output from MO2.

Output Trash — Freeimage.host

Then I extract a new version of DynDOLOD Alpha95 and xLODGen (To the right of DynDOLOD is the .new one is for Alpha97 as I test this)

DynDOLOD direc — Freeimage.host

Now you'll have to believe me, but this is all I have done, and that was all I had done before too, but it finally dawned on me, this is the issue.

So now after only making these changes, then I run xLODGen, TexGen, DynDOLOD, and now no trees/terrain again.

NewDynDOLOD — Freeimage.host

Edited September 18, 2022 by mooit

[sheson]

On 9/18/2022 at 2:17 AM, mooit said:

I see what the issue is now, but I don't understand why it happens like this.

If I backup/rename my DynDOLOD and xLODGen directories and extract the same versions, when I run xLODGen, TexGen, DynDOLOD from these new directories and put the new output in MO2 and start up SSE it won't work, or if I go to a new version of DynDOLOD it's not working, like how I'm running into this problem.

I don't understand why, but this is the issue, I'm 100% certain of it, because I've been seeing this happen in the past several times, but I didn't really think about it again, as yes, I thought my setup/configurations weren't correct, but they are, as I explained, because I can make it work, it just ends up breaking like this, and then I have to just keep juggling things around, which I have no idea what starts to make it work again, but it can be a real major event, trying to get a working version over.

As we already suspected, your problem has nothing to do with Alpha 97 specifically. Always use the latest version.

Read my earlier posts and do the troubleshooting suggestion. Test without the DynDOLOD and Occlusion plugins and report if it changes anything.

Do all tests with a new game, e.g. coc whiterun from main menu console.

[Blackread]

22 hours ago, sheson said:

Probably a race condition then. Try with Soulcairn only with this version a couple times to see if it still happens.
https://mega.nz/file/IcpUVJpS#BsaVGNhnEdVT6nJnhEN9wGSp-n8wKu0v7w27diMeBss

All right, I did some tests. Unfortunately simply running Soulcairn only with Alpha 97 produced no errors, so I couldn't really test that. But I did a few runs using the provided exe with all worldspaces, and there were no errors, so likely this has resolved the issue.

Edited September 18, 2022 by Blackread

[myztikrice]

Was it intentional that the Nexus links to the new PapyrusUtil scripts and the like for the latest alpha were archived?

[sheson]

6 hours ago, myztikrice said:

Was it intentional that the Nexus links to the new PapyrusUtil scripts and the like for the latest alpha were archived?

Yes

[Jayombi]

Quick question about :

 

 

Seems only Solitude windmill, the Farm ones are okay. Any reason why I just suddenly got this (or what I pressed during generation to get this) ?

I've checked console info and last touched it referenced  DynDOLOD...

 

Thanks.

Edited September 20, 2022 by Jayombi

[sheson]

52 minutes ago, Jayombi said:

Quick question about :

Seems only Solitude windmill, the Farm ones are okay. Any reason why I just suddenly got this (or what I pressed during generation to get this) ?

I've checked console info and last touched it referenced  DynDOLOD...

 

Thanks.

Read the first post which log and debug log to upload when making posts.

Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

You mentioned the last plugin to touch the reference is DynDOLOD but the screenshot is not showing that information. Which of the two references? What about the base records? https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

Read the answers for "Out of place or floating objects" at  https://dyndolod.info/FAQ

Maybe you installed SMIM after generating LOD.

[Jayombi]

45 minutes ago, sheson said:

Read the answers for "Out of place or floating objects" at  https://dyndolod.info/FAQ

Maybe you installed SMIM after generating LOD.

I have SMIM but never include it in the generation.

I noticed I had not included the Unofficial Skyrim Special Edition Patch so this time around I ticked it, and the result is a correct windmill.. 

[sheson]

39 minutes ago, Jayombi said:

I have SMIM but never include it in the generation.

I noticed I had not included the Unofficial Skyrim Special Edition Patch so this time around I ticked it, and the result is a correct windmill.. 

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Finalize the load order as explained in the prerequisites above. Make sure all mods, plugins and patches (that affect exterior cells and worldspaces and base records used by references in exterior cells) are enabled and their overwrite order is sorted. Ignore wrong 3rd party advice to temporarily disable plugins, mods, meshes or textures. Such advice is categorically wrong or outdated. In case of issues, solve the cause or use appropriate rules or settings for desired results.

[Abbot]

Hello,

 

Please help me. I'm desperate. This problem keep presenting itself and I don't have the slightest cue on how to solve it.

 

While playing, I regularly CTD in exteriors in the Tamriel worldspace and NetScriptFramework ALWAYS gives me this error: https://pastebin.com/NVduwQie

 

In "possible relevant objects", only the first two lines stay always the same, while in "Probable callstack" I always get "BSExtraDataList::GetExtraDataWithoutLocking_107480+A6" as the first line... What does it mean?

 

If we solve this, my game should be perfectly stable since this is the only kind of CTD that I get!!

Edited September 20, 2022 by Abbot

[sheson]

2 hours ago, Abbot said:

Hello,

 

Please help me. I'm desperate. This problem keep presenting itself and I don't have the slightest cue on how to solve it.

 

While playing, I regularly CTD in exteriors in the Tamriel worldspace and NetScriptFramework ALWAYS gives me this error: https://pastebin.com/NVduwQie

 

In "possible relevant objects", only the first two lines stay always the same, while in "Probable callstack" I always get "BSExtraDataList::GetExtraDataWithoutLocking_107480+A6" as the first line... What does it mean?

 

If we solve this, my game should be perfectly stable since this is the only kind of CTD that I get!!

Read the first of the DynDOLOD 3 Alpha thread which log and debug log to upload when making posts.

Upload the entire crash log.

The crash is of since that ACTI base record does not have a model, while BSExtraDataList seems to be a block in a NIF.

Double check the crash does not happen when DynDOLOD output is not active.

See https://dyndolod.info/FAQ which explains to check ..\DynDOLOD\docs\DynDOLOD-README.txt. Enable the debug option in DynDOLOD_Worlds.json or DynDOLOD_Worlds.txt as explained and upload the papyrus as well.

It seems the DynDOLOD.esp is being overwritten by other plugins, which seems odd. LOD and the DynDOOLOD plugins and then Occlusion should be the last things to generate and then overwrite everything.

[dkjcyxc]

Sorry but how can I change the path that TexGen uses? It kept using my former Skyrim game path, which didn't exist any more. I want to let it use my current Skyrim game path, but I don't know how I can do it. Thanks for your help!

[sheson]

5 hours ago, dkjcyxc said:

Sorry but how can I change the path that TexGen uses? It kept using my former Skyrim game path, which didn't exist any more. I want to let it use my current Skyrim game path, but I don't know how I can do it. Thanks for your help!

Do not post screens of text, post the text instead, though asking the question is already sufficient in this case.

See https://dyndolod.info/Installation-Instructions
Use the game launcher to set the current location of the game in the Windows Registry. See Windows Registry Key for more.

See https://dyndolod.info/Messages/Windows-Registry-Key for more detailed explanations.

[myztikrice]

On 9/19/2022 at 9:40 PM, sheson said:

Yes

Sorry you're not psychic, I should just ask what I want to ask

They're still being linked in the Large Reference Bugs Workaround page

https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

Why are they archived if users are still supposed to use them?

Edited September 21, 2022 by myztikrice