DynDOLOD 3.00 Alpha 196

[Lainkml]

Hello, i have huge problem with Dyndolod generated LOD and Dyndolod - SKSE plugin, for now its crashing my game, and still is showing me when i change the game version 1.1179.0 (gog version) "Dyndolod Problem with worlds config file". When i use old version of SKSE and Dyndolod Resources (nog NG) its working great, but this NG version is really broken for me and bugged as hell. If you need logs just tell me when to search for it, for i know how to generate LOD, not to resolve problem with this tool.

[sheson]

1 hour ago, Lainkml said:

Hello, i have huge problem with Dyndolod generated LOD and Dyndolod - SKSE plugin, for now its crashing my game, and still is showing me when i change the game version 1.1179.0 (gog version) "Dyndolod Problem with worlds config file". When i use old version of SKSE and Dyndolod Resources (nog NG) its working great, but this NG version is really broken for me and bugged as hell. If you need logs just tell me when to search for it, for i know how to generate LOD, not to resolve problem with this tool.

Moved to the DynDOLOD 3 Alpha thread.

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

See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing, also which papyrus and DynDOLOD.log to upload when having problems with DynDOLOD DLL NG.

Obviously post the crash log when reporting crashes in the game. See https://dyndolod.info/FAQ#ILS-or-CTD

Dyndolod Problem with worlds config file probably means the file does not exist, which might mean the DynDOLOD patch was not generated for DynDOLOD DLL NG. DynDOLOD DLL NG is not a drop-in replacement. See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

[Soulmancer]

Hi,

Not sure if this is actually dyndolod related or a false lead.  I recently moved from Net Script Framework to Crash Logger as I updated to 1.6.1170 ... I've been getting occasional crashes on loading a saved game and moving between loading areas and am noticing this is a common theme in every log.

DynDOLOD.esm: count: (1)
    There is a chance that this might cause a CTD when changing locations.

I do see in your FAQ that this will have nothing to do with auto save, but do you think it has enough validity to post a crash log and dyndolod log now or should I follow the steps outlines in your read me?  It's a bit hard to duplicate as the crashes seem at random and not consistent, just sometimes loading a save game or sometimes passing through a loading screen. I can't really "make it CTD" on the fly.

 

 

 

 

[sheson]

52 minutes ago, Soulmancer said:

Hi,

Not sure if this is actually dyndolod related or a false lead.  I recently moved from Net Script Framework to Crash Logger as I updated to 1.6.1170 ... I've been getting occasional crashes on loading a saved game and moving between loading areas and am noticing this is a common theme in every log.

DynDOLOD.esm: count: (1)
    There is a chance that this might cause a CTD when changing locations.

I do see in your FAQ that this will have nothing to do with auto save, but do you think it has enough validity to post a crash log and dyndolod log now or should I follow the steps outlines in your read me?  It's a bit hard to duplicate as the crashes seem at random and not consistent, just sometimes loading a save game or sometimes passing through a loading screen. I can't really "make it CTD" on the fly.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.
Obviously posts the crash log when making posts about CTDs in the game.

https://dyndolod.info/Official-DynDOLOD-Support-Forum
Report the actual problem or error message without making assumptions or asking leading questions. Read the explanations and tips below, especially about what information and logs to provide and how. Also see Don't ask to ask, just ask and How do I ask a good question?

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting
In case of issues in the game, test if the problem persists without any DynDOLOD output.

I will obviously look at the logs regardless of the reason of the CTD and not just make up illogical nonsense just because a filename of a plugin is listed in the load order or suggest to use the Skyrim LE SKSE memory patch with Skyrim SE. How saves, scripts and script instances work is known and documented since decades.

[maxxpower]

Hi all. I've got a question. Is DynDOLOD 3.00 recommended over the old one? (I'm using 1.5.97) I was able to successfully generate TexGen and DynDOLOD Outputs using the NG dll but when I started the game it said that I was missing the dll so I had to replace the NG dll with the old 1.5.97 Steam dll. 

I'm just confused on how that happened.

[sheson]

21 minutes ago, maxxpower said:

Hi all. I've got a question. Is DynDOLOD 3.00 recommended over the old one? (I'm using 1.5.97) I was able to successfully generate TexGen and DynDOLOD Outputs using the NG dll but when I started the game it said that I was missing the dll so I had to replace the NG dll with the old 1.5.97 Steam dll. 

I'm just confused on how that happened.

DynDOLOD 2.x had no updates since years. DynDOLOD 3 is released for alpha testing so people can help with finding and reporting problems.

Since you did mention a problem, read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Also upload the papyrus logs and the c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing

Do not paraphrase messages. Provide the actual message.

It is unclear if "1.5.97 Steam dll" refers to DynDOLOD DLL SE or the DynDOLOD DLL NG version that works for 1.5.97 and not 1.6.1130+
Which DLL is needed, depends on which papyrus scripts are installed last.
However, DynDOLOD DLL SE and DynDOLOD DLL NG are not interchangeable, like DynDOLOD DLL SE and PapyrusUtil are. DynDOLOD DLL NG requires a LOD specifically generated for it. See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

[maxxpower]

Thanks for the response. I'm honestly quite illiterate when it comes to this so I'll read through your message a few times over to digest it and will come back with useful logs. 

[RainingTacco]

On 4/16/2024 at 10:00 PM, Soulmancer said:

Hi,

Not sure if this is actually dyndolod related or a false lead.  I recently moved from Net Script Framework to Crash Logger as I updated to 1.6.1170 ... I've been getting occasional crashes on loading a saved game and moving between loading areas and am noticing this is a common theme in every log.

DynDOLOD.esm: count: (1)
    There is a chance that this might cause a CTD when changing locations.

I do see in your FAQ that this will have nothing to do with auto save, but do you think it has enough validity to post a crash log and dyndolod log now or should I follow the steps outlines in your read me?  It's a bit hard to duplicate as the crashes seem at random and not consistent, just sometimes loading a save game or sometimes passing through a loading screen. I can't really "make it CTD" on the fly.

 

 

 

 

 

Use old papyrus dyndolod scripts for now, i had crashes on load[infamous skyrim.esm::902560] with dyndo alpha 17, but with papyrus i had none. Havent tried alpha 18 yet. The crashes might had been due to my LO too, since i had a patcher for static objects/land textures after dyndolod, some activator objects too and a patch that needed dyndolod as master, which sheson said that's haram basically. So whether the crashes were because of dyndo or my LO[which i now fixed and always put dyndo output plugins last] is unknown. The one thing is almost certain - large reference bug workaround is way less lenient on load order of dyndo.esp plugin due to that activator object switching. If something replace that object, it's scripts/whatever and uses dyndo plugin as master, you gonna have a bad time. 

Edited April 20, 2024 by RainingTacco

[sheson]

5 hours ago, RainingTacco said:

i had crashes on load[infamous skyrim.esm::902560] with dyndo alpha 17, but with papyrus i had none. Havent tried alpha 18 yet. The crashes might had been due to my LO too, since i had a patcher for static objects/land textures after dyndolod, some activator objects too and a patch that needed dyndolod as master, which sheson said that's haram basically. So whether the crashes were because of dyndo or my LO[which i now fixed and always put dyndo output plugins last] is unknown. 

Read the first post and/or  https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload. Also upload the papyrus log as explained. Also upload the c:\Users\[USERNAME]\Documents\My Games\[Skyrim Special Edition|Skyrim VR]\SKSE\DynDOLOD.log for as explained at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing
Obviously upload the crash log when having crashes.

https://dyndolod.info
Use the Latest Versions
Participating in the alpha test requires to report any problems to the official DynDOLOD support forum. 

https://dyndolod.info/Official-DynDOLOD-Support-Forum:
Report the actual problem or error message without making assumptions or asking leading questions. 

Do not make patches that require DynDOLOD plugins as a master. Create all required patches before generating LOD. Otherwise report the problem or technical issue that makes you believe you need to do this afterwards.

Not using something is a troubleshooting step and not a fix. Report the problem so it can be fixed.

Do not tell users not to use something as a fix. Tell users to report the actual issue so it can be fixed.

This is the DynDOLOD 3 Alpha test to find and report bugs so they can be troubleshooted and fixed. If you are unable to meet the requirements, do not participate in the alpha test. The is just not very useful random ramblings if the actual reason for the crash "is unknown". We actually troubleshoot things here to find the actual causes of problems so we can understand and fix them.

What object activator switching? What is using DynDOLOD as a master?

[Guest]

Hey Sheson, sorry to bother you, I've never needed help modding before but I am at a loss. I can't for the life of me figure out what is going wrong, and I've tried every ini fix on here already.

I've seen dyndolod freeze up many times, and I've seen it work no hiccups.

I'm trying to get lux and seasons to work and just can't. I run a very light load order.

It usually crashes 6mins into generation, this time it 30 mins

There is like 30 different logs. What should I send?

I'm crashing consistently at Generating Markarth world SUMer i think.

 

Thank you, sorry again.

Mark

[sheson]

41 minutes ago, bloodmage said:

Hey Sheson, sorry to bother you, I've never needed help modding before but I am at a loss. I can't for the life of me figure out what is going wrong, and I've tried every ini fix on here already.

I've seen dyndolod freeze up many times, and I've seen it work no hiccups.

I'm trying to get lux and seasons to work and just can't. I run a very light load order.

It usually crashes 6mins into generation, this time it 30 mins

There is like 30 different logs. What should I send?

I'm crashing consistently at Generating Markarth world SUMer i think.

 

Thank you, sorry again.

Mark

Moved to the DynDOLOD 3 Alpha thread.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and bugreport.txt if it exists to upload.

[Guest]

Thank you for relocating me.

I haven't been able to generate a bug report because I haven't finished the process since.

I enabled Live logging but still didn't see it.

here's all the logs I have in a rar.

Logs.rar

[sheson]

1 hour ago, bloodmage said:

Thank you for relocating me.

I haven't been able to generate a bug report because I haven't finished the process since.

I enabled Live logging but still didn't see it.

here's all the logs I have in a rar.

Logs.rar

If you uploaded all logs from the ..\DynDOLOD\Logs\ folder, then I find it curious that there are no TexGen logs. Did you not run it?

After setting RealTimeLog=1 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.INI, you should see ..\DynDOLOD\Logs\DynDOLOD_SSE_realtime_log.txt appear shortly after the background loader finished, just before the wizard, advanced or expert options window shows.

If it doesn't, you probably edited the wrong INI or the setting was not added correctly. Copy and paste it, make sure it is added under the [DyNDOLOD] section heading at the top.

[Guest]

Sorry, Texgen ran fine, I had cleared the logs and didn't run it again, hence it missing.

texgen always runs fine for me tbh, very fast.

I reran everything and gave you the new logs

from what I can tell when it freezes up, its generating texture atlas (usually for markarth world sometimes hunterworld) and its looking for a tree mesh for the season and then memory skyrockets and it freezes. (I've tried the recommended fixes in the  atlas and memory help section)

I've tried just generating markarth world and also see the freeze, but I have a feeling this tree is in more than one spot.

txtgen logs.rar

[sheson]

10 hours ago, bloodmage said:

Sorry, Texgen ran fine, I had cleared the logs and didn't run it again, hence it missing.

texgen always runs fine for me tbh, very fast.

I reran everything and gave you the new logs

from what I can tell when it freezes up, its generating texture atlas (usually for markarth world sometimes hunterworld) and its looking for a tree mesh for the season and then memory skyrockets and it freezes. (I've tried the recommended fixes in the  atlas and memory help section)

I've tried just generating markarth world and also see the freeze, but I have a feeling this tree is in more than one spot.

txtgen logs.rar

Still not DynDOLOD log or debug, which are written, when you close DynDOLOD via clicking X top right. Only kill it via task manager if that closing does not work for a minute.

In that case, edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini with notepad and add RealTimeLog=1 under [DynDOLOD] at the top. Then start DynDOLOD. Once it shows the options window, check the ..\DynDOLOD\Logs\ folder that DynDOLOD_SSE_realtime_log.txt is being created. If that does not work, reboot and try again. If it still does not work, upload your version of DynDOLOD_SSE.ini. With the log we have a good chance to troubleshoot this more quickly.

I assume high memory usage means that DynDOLODx64.exe shows high memory usage in task manager? Check if it has sub processes like LODGenx64.exe or Texconvx64.exe that might be using lots of memory.