DynDOLOD 3.00 Alpha 173

[Chromatic]

On 11/27/2023 at 8:25 PM, sheson said:

Thanks. RIght now here is what I am seeing: it reserves memory for a texture with X*Y resolution, and a few milliseconds later asks for the X*Y of the reserved memory and at some point the values returned are wrong, while everything worked perfectly fine for the same texture several times before for the earlier worldspaces.

So this seems to be something random. Can you double check that there are no instabilities caused by CPU overclocking, memory timings, other BIOS settings etc?
Can you double check main and video memory usage while the tool runs. Maybe really close everything else, including browsers and whatever else might be using video memory.

Run this test version https://mega.nz/file/9FYRHZ5C#dNqoWMpDrH9LRN1nmGq5Brwnjo29MjQ9eBmVTn4GieY and upload new bugreport.txt, log and debug log.

No overclocking is done on this system, and the only setting enabled in the BIOS is XMP. I haven't run long stress tests yet but everything seems stable otherwise. I also pretty much closed all other programs during the latest DynDOLOD run except from Vortex and DynDOLOD itself but I still got an error. As for memory usage, I haven't checked it this time but system memory is 16GB and the GPU has 8GB of video memory so I assume it should be plenty with everything else closed.

Let me know if you need me to test this further though, I can do another run and closely monitor memory usage and maybe even do some long hardware stress tests if needed.

Latest logs: https://ufile.io/dj87ufng 

Edited December 2, 2023 by Chromatic

[sheson]

2 hours ago, Chromatic said:

No overclocking is done on this system, and the only setting enabled in the BIOS is XMP. I haven't run long stress tests yet but everything seems stable otherwise. I also pretty much closed all other programs during the latest DynDOLOD run except from Vortex and DynDOLOD itself but I still got an error. As for memory usage, I haven't checked it this time but system memory is 16GB and the GPU has 8GB of video memory so I assume it should be plenty with everything else closed.

Let me know if you need me to test this further though, I can do another run and closely monitor memory usage and maybe even do some long hardware stress tests if needed.

Latest logs: https://ufile.io/dj87ufng 

Use this test version https://mega.nz/file/5IhWEABT#kXwLkR67UPnTaDIy-QCug_OgnO2deupYmqxPBPndRzc and upload new logs.

Try to keep an eye on memory just in case.

[Husqvarna1]

Error window:

[Window Title]
TexGen

[Main Instruction]
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds).

[Content]
Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.

[01:05] <Error: OpenGL: out of memory for textures\architecture\whiterun\wrslatefloor01_n.dds>
[01:05] <Error: OpenGL: out of memory for textures\clutter\stockade\stockadeplanks01snow.dds>
[02:13]     Creating C:\AETools\DynDOLOD\TexGen_Output\textures\lod\wrplasterint01lowlod.dds from 4 textures
[02:28] Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
[02:28] Removing temporary files
[02:29] TexGen completed successfully
[02:29] Created a summary of log messages C:\AETools\DynDOLOD\Summary\TexGen_Index.html.
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
Error: Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.
The message dialog has been copied to the clipboard

has anyone encountered this before, if so can someone please help?

[sheson]

17 minutes ago, Husqvarna1 said:

Error window:

[Window Title]
TexGen

[Main Instruction]
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds).

[Content]
Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.

[01:05] <Error: OpenGL: out of memory for textures\architecture\whiterun\wrslatefloor01_n.dds>
[01:05] <Error: OpenGL: out of memory for textures\clutter\stockade\stockadeplanks01snow.dds>
[02:13]     Creating C:\AETools\DynDOLOD\TexGen_Output\textures\lod\wrplasterint01lowlod.dds from 4 textures
[02:28] Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
[02:28] Removing temporary files
[02:29] TexGen completed successfully
[02:29] Created a summary of log messages C:\AETools\DynDOLOD\Summary\TexGen_Index.html.
Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000
Error: Error while loading images from memory E3571008 (357914116 Bytes) (file format: dds). Exception Message: Access violation at address 004BBEC9 in module 'TexGen.exe'. Write of address 00000000.
The message dialog has been copied to the clipboard

has anyone encountered this before, if so can someone please help?

Moved to the DynDOLOD 3 Alpha thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire log, debug log and bugreport.txt to upload when making posts.

https://dyndolod.info/Messages/Exceptions
If there are any kind of memory errors, make sure to use the x64 versions of the tools. Check FAQ answers for High memory usage.

https://dyndolod.info/Messages/Exceptions#OpenGL
If they are memory related also check FAQ answers for High memory usage.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

[TIREDshinigami]

Error  Load Order(if it matters my specs are r7 7735hs 16gb ddr5 mobile rtx 4060 8gb and everything is on an ssd)I installed dyndolod following this guide and everything worked correctly i installed silent horizons 2 universal core enb as well no issues after that was just following a list of mod recommendations and i got to majestic mountains after installing it i followed as the mod said and tried to re run tex gen and dyndolod at first i forgot to disable the previous outputs so after dealing with that tex gen gave me this error
my game reaches skyrim logo i get the enb binaries thing and then it crashes to desktop.

p.s: I have missing masters of CC content with COTN I dont know if i can resolve that i was planning on just ignoring them but i can try disabling those mods to see if that is causing the issue

p.s2:im not new to modding but its my first time using dyndolod and enbs and i have no idea what im doing

p.s3:im on vortex sse 1.5.97 latest enb binaries and skse 2_00_20 i think.

[z929669]

Moved to the correct forum.

Please read the entire DynDOLOD Alpha OP for basics, and provide your log files for the most recent generation as described. There's also links to more information.

Also, there is mention of COTN on the DynDOLOD Alpha topic: https://stepmodifications.org/forum/search/?q=COTN&quick=1&type=forums_topic&item=17510

[TIREDshinigami]

tex gen logs
https://ufile.io/x9ie06ew

removed COTN and now my game launches but the tex gen issue persists.

[sheson]

2 hours ago, TIREDshinigami said:

tex gen logs
https://ufile.io/x9ie06ew

removed COTN and now my game launches but the tex gen issue persists.

Moved to the DynDOLOD 3 Alpha thread.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log to also upload in addition to the debug log.
As explained on the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text, do not post screenshots of messages but use the Copy message to clipboard and paste the text instead.
As explained on the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, use the Click on this link for additional explanations and help for this message to open additional help.
As explained in the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search, search the forum for similar posts before posting.

https://dyndolod.info/Messages/Exceptions
If there are any kind of memory errors, make sure to use the x64 versions of the tools. Check FAQ answers for High memory usage.

https://dyndolod.info/Messages/Exceptions#OpenGL
If they are memory related also check FAQ answers for High memory usage.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

[TIREDshinigami]

so adding the line lodcache=10 texturecache=10 to the texgen_sse didnt help by itself but after playing around with the output format i changed it to bc7max and that didnt help either but using both this line and bc7max it worked now i have removed the line and it still works i am very confused with and without it i had alot of ram and vram left so idk why i was getting that error thanks for the amazing mod and the quick support 
also sorry for making a post in the wrong place and providing incorrect logs maybe im an idiot or i got redirected to the wrong page but i saw nothing about how to provide logs and all that anywhere.

Edited December 3, 2023 by TIREDshinigami

[sheson]

3 hours ago, TIREDshinigami said:

so adding the line lodcache=10 texturecache=10 to the texgen_sse didnt help by itself but after playing around with the output format i changed it to bc7max and that didnt help either but using both this line and bc7max it worked now i have removed the line and it still works i am very confused with and without it i had alot of ram and vram left so idk why i was getting that error thanks for the amazing mod and the quick support 
also sorry for making a post in the wrong place and providing incorrect logs maybe im an idiot or i got redirected to the wrong page but i saw nothing about how to provide logs and all that anywhere.

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

Use the x64 version.
BC7 Max just means texconv will spend a considerable longer time to create a BC7 texture compared to BC7 Quick.

[Brambleshire]

On 12/2/2023 at 6:35 AM, sheson said:

What other errors are reported by xEdit that you choose to ignore?

To be precise there are 140 in total.
5 "Found a DIAL reference, expected: GLOB" in the STEP Conflict resolution - WACCF patch
2 "Tint index not found" in Summerset Isle
about 10 "navmesh triangle not found" in a few location mods, all involving some kind of doorway.
about 15 "quest alias not found" in a few mods that have quests
1 "HAZD \ Record Header \ Record Flags -> <Unknown: 25 $19>" in Odin
4 "PTDA - Target \ Target Data \ Target -> Target is not persistent" in AI Overhaul
4 "placed mapmarker" in Bruma
The rest are all either something about "Using encoding (from language): 1252  (ANSI - Latin I)" or "NULL reference, expected fact".

However these two I am very unsure about:
[03:08] Tamriel [WRLD:0000003C]
[03:08]     WRLD -> Warning: internal file FormID is a HITME: 0100003C (should be 0000003C ) 
and 
[02:37] [NAVI:00012FB4]
[02:37]     NAVI \ Navigation Map Infos \ NVMI - Navigation Map Info \ Navigation Mesh -> [141D5064] <Error: Could not be resolved>

When I try going to their FormID I dont see anything that says error or warning. I have no idea what to do.

On 12/2/2023 at 6:35 AM, sheson said:

You said Yes to this message prompt:
Update existing plugin(s)? If this is not successful start from scratch.

Yes.

On 12/2/2023 at 6:35 AM, sheson said:

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Pay attention to all log messages. 

For example these messages which are repeated many times:
<Warning: File [B9] DynDOLOD.esp with Group GRUP World Children of [..] is missing an overriden record for[..]

Delete the output folder log folder, delete bugreport,.txt and then generate DynDOLOD from scratch - that means to disable/remove old DynDOLOD output in the load order. If problem persists, upload new log, debug log and bugreport.txt.

https://dyndolod.info/Updating

I tried this and some wierd stuff happened. I didn't get the usual "Assertion Error", DynDOLOD ran for while, but then several pop up windows with more flowing text popped up, and now its still running, but stuck. My fans are still spinning loud, when i click X it says "Generation will not be complete", but its been almost 5 hours now. 
Its been stuck here:
[16:31] [XJKislandWorld] Generating object LOD
[16:31] Creating C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\textures\lod\snowstone01lod.dds
[16:32] Creating C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\textures\lod\xjkstockadeplanks01lod.dds
[16:34] [XJKislandWorld] Executing "C:\Modding\ModdingTools\DynDOLOD\Edit Scripts\LODGenx64Win.exe" --inputfile "C:\Modding\ModdingTools\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_XJKislandWorld.txt" --logfile "C:\Modding\ModdingTools\DynDOLOD\Logs\LODGen_SSE_XJKislandWorld_log.txt"
[16:34] [XJKislandWorld] Creating texture atlas C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_XJKislandWorld.dds 8192 x 4096
[16:34] [XJKislandWorld] Creating texture atlas C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_XJKislandWorld_Glow.dds 512 x 512
Its been stuck right here over 4 hours.

Why did you link to the update page? The version has not been changed today or yesterday has it?
Thank you again for your help. 

[sheson]

1 hour ago, Brambleshire said:

To be precise there are 140 in total.
5 "Found a DIAL reference, expected: GLOB" in the STEP Conflict resolution - WACCF patch
2 "Tint index not found" in Summerset Isle
about 10 "navmesh triangle not found" in a few location mods, all involving some kind of doorway.
about 15 "quest alias not found" in a few mods that have quests
1 "HAZD \ Record Header \ Record Flags -> <Unknown: 25 $19>" in Odin
4 "PTDA - Target \ Target Data \ Target -> Target is not persistent" in AI Overhaul
4 "placed mapmarker" in Bruma
The rest are all either something about "Using encoding (from language): 1252  (ANSI - Latin I)" or "NULL reference, expected fact".

However these two I am very unsure about:
[03:08] Tamriel [WRLD:0000003C]
[03:08]     WRLD -> Warning: internal file FormID is a HITME: 0100003C (should be 0000003C ) 
and 
[02:37] [NAVI:00012FB4]
[02:37]     NAVI \ Navigation Map Infos \ NVMI - Navigation Map Info \ Navigation Mesh -> [141D5064] <Error: Could not be resolved>

When I try going to their FormID I dont see anything that says error or warning. I have no idea what to do.

Yes.

I tried this and some wierd stuff happened. I didn't get the usual "Assertion Error", DynDOLOD ran for while, but then several pop up windows with more flowing text popped up, and now its still running, but stuck. My fans are still spinning loud, when i click X it says "Generation will not be complete", but its been almost 5 hours now. 
Its been stuck here:
[16:31] [XJKislandWorld] Generating object LOD
[16:31] Creating C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\textures\lod\snowstone01lod.dds
[16:32] Creating C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\textures\lod\xjkstockadeplanks01lod.dds
[16:34] [XJKislandWorld] Executing "C:\Modding\ModdingTools\DynDOLOD\Edit Scripts\LODGenx64Win.exe" --inputfile "C:\Modding\ModdingTools\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_XJKislandWorld.txt" --logfile "C:\Modding\ModdingTools\DynDOLOD\Logs\LODGen_SSE_XJKislandWorld_log.txt"
[16:34] [XJKislandWorld] Creating texture atlas C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_XJKislandWorld.dds 8192 x 4096
[16:34] [XJKislandWorld] Creating texture atlas C:\Modding\ModdingTools\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_XJKislandWorld_Glow.dds 512 x 512
Its been stuck right here over 4 hours.

Why did you link to the update page? The version has not been changed today or yesterday has it?
Thank you again for your help. 

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

The Navmesh errors can cause CTD.
https://dyndolod.info/Messages/Internal-File-FormID-Is-A-HITME
You need to delete the broken plugins that has HITME errors. Maybe you can fix it as explained.
https://dyndolod.info/Messages/Unresolved-Form-ID the reason the form ID can not be found  is the reason why it is unresolved.
The record with the unresolved error is 00012FB4

https://dyndolod.info/FAQ#TexGen-DynDOLOD-stuck-while-creating-textures

You were trying to update an existing DynDOLOD installation.

[Brambleshire]

30 minutes ago, sheson said:

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

I'm sorry, do you mean that you need the log and debug log for the subsequent run of DynDOLOD?

[Soulmancer]

Might be a dumb question, but checking the log I am seeing.  Perhaps I am looking at the wrong message / log to see if the workaround was successful or failed. 

Large reference bugs workarounds: enabled (DynDOLOD.DLL: NG, Scripts: NG, Deleted references: no)

 

But when dyndolod completes it does note.

Error: Deleted reference Gabby.esp [REFR:0003BF63] (places TreePineShrub02Snow [TREE:0009DAA1] in GRUP Cell Temporary Children of [CELL:00009352] (in Tamriel "Skyrim" [WRLD:0000003C] at -1,18))

[sheson]

8 hours ago, Brambleshire said:

I'm sorry, do you mean that you need the log and debug log for the subsequent run of DynDOLOD?

Yes, if there still is a problem when using the x64 version and after changing settings.