DynDOLOD 3.00 Alpha 198

[sdexy]

Hello,

i have been trying to generate the textures but texgen stops after around 35 minutes, processor usage goes to 0, ram usage drops. no error no messages

this is the log after the last attempt, i just force closed the application
https://paste.ee/p/hNDAZ

antivirus or firewall and etc is disabled, both texgen and texconverter is granted elevated rights

a couple days ago before the new dyndolod update i managed to run it and complete it in around 30 minutes

any idea what might be causing the issue? how can i troubleshoot it?

Edited March 15, 2023 by sdexy

[sheson]

20 minutes ago, sdexy said:

Hello,

i have been trying to generate the textures but texgen stops after around 35 minutes, processor usage goes to 0, ram usage drops. no error no messages

this is the log after the last attempt, i just force closed the application
https://paste.ee/p/hNDAZ

antivirus or firewall and etc is disabled, both texgen and texconverter is granted elevated rights

a couple days ago before the new dyndolod update i managed to run it and complete it in around 30 minutes

any idea what might be causing the issue? how can i troubleshoot it?

Moved to the DynDOLOD 3 Alpha thread. Read the first post which debug log to also upload when making posts.

Check the Windows task manager if there are stuck Texconvx64.exe (a command line tool from MS) processes TexGen might be waiting for.

If that is the case, then something is blocking Texconvx64.exe from executing/continuing. If you kill it TexGen will most likely continue and fail with an error message.

If it is not the OS, UAC, antivir or the mod manager blocking execution, file or folder access, it could be old/outdated graphics drivers or a problem with them preventing it from continuing. Do a clean re-install of the latest official drivers (not beta or optional versions). Do not install any bloat/crapware that comes with drivers, just the drivers only.

[sdexy]

25 minutes ago, sheson said:

Moved to the DynDOLOD 3 Alpha thread. Read the first post which debug log to also upload when making posts.

Check the Windows task manager if there are stuck Texconvx64.exe (a command line tool from MS) processes TexGen might be waiting for.

If that is the case, then something is blocking Texconvx64.exe from executing/continuing. If you kill it TexGen will most likely continue and fail with an error message.

If it is not the OS, UAC, antivir or the mod manager blocking execution, file or folder access, it could be old/outdated graphics drivers or a problem with them preventing it from continuing. Do a clean re-install of the latest official drivers (not beta or optional versions). Do not install any bloat/crapware that comes with drivers, just the drivers only.

Thank you for the quick response
Here is the debug file of the latest run, for some reason pastee was not responding so I used ufile
https://ufile.io/xuo3gzm7

There was a command line tool in the processes next to textgen and texconv, idling as well

[sheson]

13 minutes ago, sdexy said:

Thank you for the quick response
Here is the debug file of the latest run, for some reason pastee was not responding so I used ufile
https://ufile.io/xuo3gzm7

There was a command line tool in the processes next to textgen and texconv, idling as well

This is how Windows works, in order to run a command line tool, the command line prompt cmd/conhost is spawned to run it in.

If that is the case, then something is blocking Texconvx64.exe from executing/continuing. If you kill it TexGen will most likely continue and fail with an error message.

If it is not the OS, UAC, antivir or the mod manager blocking execution, file or folder access (reboot), it could be old/outdated graphics drivers or a problem with them preventing it from continuing. Do a clean re-install of the latest official drivers (not beta or optional versions). Do not install any bloat/crapware that comes with drivers, just the drivers only.

[sdexy]

38 minutes ago, sheson said:

This is how Windows works, in order to run a command line tool, the command line prompt cmd/conhost is spawned to run it in.

If that is the case, then something is blocking Texconvx64.exe from executing/continuing. If you kill it TexGen will most likely continue and fail with an error message.

If it is not the OS, UAC, antivir or the mod manager blocking execution, file or folder access (reboot), it could be old/outdated graphics drivers or a problem with them preventing it from continuing. Do a clean re-install of the latest official drivers (not beta or optional versions). Do not install any bloat/crapware that comes with drivers, just the drivers only.

I updated my graphics drivers and it completed the generating process, thank you

[RainingTacco]

Any good photo op comparisons with complex grass lods between 118 and 119? Worth rerunning?

[sheson]

2 hours ago, RainingTacco said:

Any good photo op comparisons with complex grass lods between 118 and 119? Worth rerunning?

As explained on the first post, use search to find similar questions and answers or just click a couple pages back.

https://stepmodifications.org/forum/search/?&q="alpha 119"&type=forums_topic&quick=1&item=17510

Only you can compare and test changes for your custom load order and preference.

[Pawelekdabek]

Quick noob question. Would lods generated on pc work on xbox?

[sheson]

8 hours ago, Pawelekdabek said:

Quick noob question. Would lods generated on pc work on xbox?

Meshes and textures work for the load order they were generated for. https://dyndolod.info/How-LOD-Works https://dyndolod.info/Mod-Authors

All mods and assets are created on PC.

[VladossX]

[04:09] Created a summary of log messages S:\DynDOLOD 3.00-68518-Alpha-119-1678452757\DynDOLOD\Summary\DynDOLOD_Index.html.
Access violation at address 000000000040FDA5 in module 'DynDOLODx64.exe'. Read of address 0000004000000008 while processing Dawnguard.esm [REFR:0200299F] (places sc_freewallCap02 [STAT:0200F9F0] in GRUP Cell Temporary Children of SoulCairnStartAmbush [CELL:02002CFB] (in DLC01SoulCairn "Каирн Душ" [WRLD:02001408] at -4,-3))
Error: Access violation at address 000000000040FDA5 in module 'DynDOLODx64.exe'. Read of address 0000004000000008 while processing Dawnguard.esm [REFR:0200299F] (places sc_freewallCap02 [STAT:0200F9F0] in GRUP Cell Temporary Children of SoulCairnStartAmbush [CELL:02002CFB] (in DLC01SoulCairn "Каирн Душ" [WRLD:02001408] at -4,-3))
User says "OK"
Can someone help?

[sheson]

16 minutes ago, VladossX said:

[04:09] Created a summary of log messages S:\DynDOLOD 3.00-68518-Alpha-119-1678452757\DynDOLOD\Summary\DynDOLOD_Index.html.
Access violation at address 000000000040FDA5 in module 'DynDOLODx64.exe'. Read of address 0000004000000008 while processing Dawnguard.esm [REFR:0200299F] (places sc_freewallCap02 [STAT:0200F9F0] in GRUP Cell Temporary Children of SoulCairnStartAmbush [CELL:02002CFB] (in DLC01SoulCairn "Каирн Душ" [WRLD:02001408] at -4,-3))
Error: Access violation at address 000000000040FDA5 in module 'DynDOLODx64.exe'. Read of address 0000004000000008 while processing Dawnguard.esm [REFR:0200299F] (places sc_freewallCap02 [STAT:0200F9F0] in GRUP Cell Temporary Children of SoulCairnStartAmbush [CELL:02002CFB] (in DLC01SoulCairn "Каирн Душ" [WRLD:02001408] at -4,-3))
User says "OK"
Can someone help?

Read the first post which entire log of the meaningful session, entire debug log and bugreport.txt if it exists to upload when making posts.

[heheloveer]

On 3/3/2023 at 4:37 PM, heheloveer said:

I made a save on the Whiterun watchtower and every time I load the save the grass lod bug appears, even if when I made the save the grass looked completely normal. As I suspected this only happened in large reference cells outside the loaded zone, since changing uLargeRefLODGridSize to 5 apparently fix this. Moving the player character to the previously affected area also makes the lod grass go away. Notice in the screenshots how not all cells are affected by this. I can't seem to find any particular pattern in affected cells either. The second screenshot shows how it looks like up close. I enabled papyrus logging and there doesn't seem to be anything related to SHESON_DynDOLOD scripts in Papyrus.0.log. Should I disable large reference bugs workarounds and regenerate DynDOLOD to see what happens?

Papyrus.0.log 202.35 kB · 1 download

Reported this in version 118 and after updating to version 119 it seems the large reference bugs persist in the same cells. Maybe version 119 fixed such occurrences in some other cells, I'm not sure. Also I can confirm this does not only happen in Whiterun, but in Falkreath as well, so it's pretty widespread. Logs and the files you requested last time are here: https://anonfiles.com/88s8c5fbz8/Logs_and_Stuff_rar

Also, two unrelated questions: 1) The mod Northern Roads replaced the Whiterun bridges with its own unique models. The bridges looked and worked completely fine but after generating lod with DynDOLOD I noticed the lod models of the bridges seem a little bit misplaced, as shown in the screenshots. What could have caused this and is there a fix?

2) How to make the Whiterun Temple Tree show up on the map? I use LOD Level 32 object lod for the map and tried editing the wrtempletree rule, but nothing seemed to work.

[VladossX]

Forgive my ignorance.
But I thought that I do not care so much cairn and just removed the check mark. Without it seems to be generated smoothly

[sheson]

25 minutes ago, VladossX said:

Forgive my ignorance.
But I thought that I do not care so much cairn and just removed the check mark. Without it seems to be generated smoothly

You mean you decided to simply not check a worldspace in order to ignore the problem?

You are participating in an ALPHA TEST that is done specifically to find and report problems. Read the first post which log, debug log and bugreport.txt to upload, so that the issue can be troubleshooted and fixed.

[sheson]

40 minutes ago, heheloveer said:

Reported this in version 118 and after updating to version 119 it seems the large reference bugs persist in the same cells. Maybe version 119 fixed such occurrences in some other cells, I'm not sure. Also I can confirm this does not only happen in Whiterun, but in Falkreath as well, so it's pretty widespread. Logs and the files you requested last time are here: https://anonfiles.com/88s8c5fbz8/Logs_and_Stuff_rar

Also, two unrelated questions: 1) The mod Northern Roads replaced the Whiterun bridges with its own unique models. The bridges looked and worked completely fine but after generating lod with DynDOLOD I noticed the lod models of the bridges seem a little bit misplaced, as shown in the screenshots. What could have caused this and is there a fix?

2) How to make the Whiterun Temple Tree show up on the map? I use LOD Level 32 object lod for the map and tried editing the wrtempletree rule, but nothing seemed to work.

For the large reference issue, can you check the papyrus log if there are any problems reported by the DYNDOLOD scripts?

For the question about northern roads, a screenshot with more informative console would be helpful https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots.

IIRC the mod includes the LOD model for the bridge itself. If its position is off, it could be because its root node has a translation. If there are no translations, then the vertices themselves are off. The game ignores root node translation, while the CK/LODGen LOD generation does not.