DynDOLOD 3.00 Alpha 182

[DoubleYou]

The very first bug on Heart of the Reach is for this. The tree mesh indicates a tree glow map texture that it doesn't provide, which is likely a mistake in the nif file for that mod. If you know how to use Nifskope, it is an easy fix.

https://www.nexusmods.com/skyrimspecialedition/mods/76494?tab=bugs

[Cayamc]

I don't know how to use nifskope but i will learn, thank you for pointing that out. 

[sheson]

5 hours ago, Cayamc said:

When i generate TexGen texture i get missing textures or meshes and i don't understand why. Everything is fine when i play the game. I allready reinstalled all the main files 3 times to be sure anything isnt missing. 

When i use the output afterwards, i get a lot of blue assets in the world.. I'm using mostly parallax textures btw. The logs, the modlist and the skyrim ini is in the files. Thank you so much for your kindness. 

TexGen_SSE_Debug_log.zip 424.26 kB · 3 downloads Skyrim.ini 2.89 kB · 0 downloads modlist.txt 46.77 kB · 0 downloads

Moved to the DynDOLOD 3 Alpha thread.
Read the first post which log file to also upload when making posts. You only uploaded the TexGen log, while the posts hints missing textures problems after the LOD patch generation as well.

Read https://dyndolod.info/Messages/File-Not-Found-Meshes and https://dyndolod.info/Messages/File-Not-Found-Textures.

Find out which mods are missing assets. Double check their requirements and installation instructions. Check their comments or bugs sections for related posts.

https://dyndolod.info/Mods/Beyond-Skyrim-Bruma
File not found errors are because not all required assets for LOD generation ship with the mod.

[IX_Flipyap]

DynDOLOD_SSE_log.txtDynDOLOD_SSE_Debug_log.txtDynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_TerrainUnderside_log.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_TexturesUsed_DLC01SoulCairn.txtLODGen_SSE_DLC01SoulCairn_log.txtDynDOLOD_SSE_BillboardsUsed_DLC01SoulCairn.txtDynDOLOD_SSE_TexturesUsed_DLC2ApocryphaWorld.txtLODGen_SSE_DLC2ApocryphaWorld_log.txtDynDOLOD_SSE_TexturesUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_log.txtDynDOLOD_SSE_BillboardsUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_Dimfrost.txtLODGen_SSE_Dimfrost_log.txtDynDOLOD_SSE_BillboardsUsed_Dimfrost.txtLODGen_SSE_Dimfrost_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_WyrmstoothWorld.txtDynDOLOD_SSE_BillboardsUsed_WyrmstoothWorld.txtLODGen_SSE_WyrmstoothWorld_log.txt      I Ended up getting this issue again. sorry about not posting details. Im using dyndolod3 and here are all the logs made before the process was terminated. the Mo2 version is 2.4.4

 

Edited November 27, 2022 by IX_Flipyap
Added MO2 Version

[sheson]

1 hour ago, IX_Flipyap said:

DynDOLOD_SSE_log.txtDynDOLOD_SSE_Debug_log.txtDynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_TerrainUnderside_log.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_TexturesUsed_DLC01SoulCairn.txtLODGen_SSE_DLC01SoulCairn_log.txtDynDOLOD_SSE_BillboardsUsed_DLC01SoulCairn.txtDynDOLOD_SSE_TexturesUsed_DLC2ApocryphaWorld.txtLODGen_SSE_DLC2ApocryphaWorld_log.txtDynDOLOD_SSE_TexturesUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_log.txtDynDOLOD_SSE_BillboardsUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_Dimfrost.txtLODGen_SSE_Dimfrost_log.txtDynDOLOD_SSE_BillboardsUsed_Dimfrost.txtLODGen_SSE_Dimfrost_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_WyrmstoothWorld.txtDynDOLOD_SSE_BillboardsUsed_WyrmstoothWorld.txtLODGen_SSE_WyrmstoothWorld_log.txt      I Ended up getting this issue again. sorry about not posting details. Im using dyndolod3 and here are all the logs made before the process was terminated. the Mo2 version is 2.4.4

Moved to the DynDOLOD 3 Alpha thread.

Delete all logs. Add realtimelog=1 below [DynDOLOD] in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Then execute DynDOLOD again.

See first post which bugreport.txt if it exists to upload in a addition to the new files in the log folder.

https://dyndolod.info/Messages/Deleted-Reference
https://dyndolod.info/Generation-Instructions#Prerequisites
Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean

[IX_Flipyap]

5 hours ago, sheson said:

See first post which bugreport.txt if it exists to upload in a addition to the new files in the log folder.

DynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txt   Here are the new logs. plus the realtime log. https://ufile.io/x2h8efr0 i did not find any files named bugreport.txt

[sheson]

7 hours ago, IX_Flipyap said:

DynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txt   Here are the new logs. plus the realtime log. https://ufile.io/x2h8efr0 i did not find any files named bugreport.txt

Check the Windows Event viewer for related message(s) about the DynDOLODx64.exe or TexConv64.exe

[IX_Flipyap]

I have found some errors. Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x636f6136
Faulting module name: KERNEL32.DLL, version: 10.0.19041.2251, time stamp: 0x73bb7c6b
Exception code: 0xc000001d
Fault offset: 0x00000000000204e3
Faulting process id: 0x3314
Faulting application start time: 0x01d902b5c578301f
Faulting application path: E:\SMEFT\tools\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL
Report Id: db0650b4-34d1-45b5-8117-1f6b68375ab2
Faulting package full name: 
Faulting package-relative application ID:         

 

Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Taking Your Firstborn because of this error.

Program: Taking Your Firstborn
File: 

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

                         

 

[sheson]

1 hour ago, IX_Flipyap said:

I have found some errors. Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x636f6136
Faulting module name: KERNEL32.DLL, version: 10.0.19041.2251, time stamp: 0x73bb7c6b
Exception code: 0xc000001d
Fault offset: 0x00000000000204e3
Faulting process id: 0x3314
Faulting application start time: 0x01d902b5c578301f
Faulting application path: E:\SMEFT\tools\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL
Report Id: db0650b4-34d1-45b5-8117-1f6b68375ab2
Faulting package full name: 
Faulting package-relative application ID:         

 

Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Taking Your Firstborn because of this error.

Program: Taking Your Firstborn
File: 

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0                     

 

Read what the event log message tells you about Windows not being able to access the file and follow its suggestions.
There is nothing a program can do about the OS terminating it because of file system issues.

https://dyndolod.info/Installation-Instructions
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

Could also be power savings related. Also consider adding exceptions to antivir etc.

[Mousetick]

About the "Moved large reference" warnings, thanks for adding them.

It looks like the warning is issued if any ESM plugin in the stack moves the LR to a different cell, even if the last, winning ESM plugin in the stack places it back into its original cell. Is this the expected warning behavior? If yes, why is that?

Hypothetical example (next plugin overrides previous):

• Skyrim.esm REFR XYZ places Object_1 in cell Cell_A (REFR is LR)
• Plugin1.esm REFR XYZ places Object_1 in cell Cell_B (LR is moved)
• Plugin2.esm REFR XYZ places Object_1 in cell Cell_A (winning override)

DynDOLOD (Alpha 106) issues a warning "Moved large reference from Cell_A to Cell_B Skyrim.esm [REFR:XYZ]..."

This looks like a false positive to me.

Thanks.

[IX_Flipyap]

Alright i changed my power plan and moved the dyndolod install folder to my D: drive and added it to an exeption list. i ended up getting a bugreport txt file but the problem still persists. i also missed a new report left by the even viewer it also came with a report file. im going to give CHKDSK a try aswell.  

Fault bucket 1266036580241557564, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DynDOLODx64.exe
P2: 3.0.0.0
P3: 636f6136
P4: KERNEL32.DLL
P5: 10.0.19041.2251
P6: 73bb7c6b
P7: c000001d
P8: 00000000000204e3
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD4C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_a1a2964fe15fe8d846ff13fd2d7e82a82ffab9_76ec4113_3422fec7-78a4-4af9-a4b8-66ee941ee573

Analysis symbol: 
Rechecking for solution: 0
Report Id: abb8aaf2-edb1-49a6-965d-007adb0a4bbc
Report Status: 268435456
Hashed bucket: f7a4d1104eaf8d0f0191dd8fddf2c83c
Cab Guid: 0

bugreport.txt Report.txt

[sheson]

43 minutes ago, IX_Flipyap said:

Alright i changed my power plan and moved the dyndolod install folder to my D: drive and added it to an exeption list. i ended up getting a bugreport txt file but the problem still persists. i also missed a new report left by the even viewer it also came with a report file. im going to give CHKDSK a try aswell.  

Fault bucket 1266036580241557564, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DynDOLODx64.exe
P2: 3.0.0.0
P3: 636f6136
P4: KERNEL32.DLL
P5: 10.0.19041.2251
P6: 73bb7c6b
P7: c000001d
P8: 00000000000204e3
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD4C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_a1a2964fe15fe8d846ff13fd2d7e82a82ffab9_76ec4113_3422fec7-78a4-4af9-a4b8-66ee941ee573

Analysis symbol: 
Rechecking for solution: 0
Report Id: abb8aaf2-edb1-49a6-965d-007adb0a4bbc
Report Status: 268435456
Hashed bucket: f7a4d1104eaf8d0f0191dd8fddf2c83c
Cab Guid: 0

bugreport.txt 69.87 kB · 0 downloads Report.txt 16.2 kB · 0 downloads

Upload the realtime log, assuming there is still no normal log / debug log. Also upload the attached files mentioned in the event log.

Is that event log entry the only one related to this around this timestamp?

There is still not much the program can do about being terminated without its crash handler being invoked.

In addtion to chkdsk run sfc /scannow as admin. Doublecheck BIOS (memory timing settings for example) and/or disable overclocking etc.

[IX_Flipyap]

2 hours ago, sheson said:

Upload the realtime log, assuming there is still no normal log / debug log. Also upload the attached files mentioned in the event log.

Is that event log entry the only one related to this around this timestamp?

There is still not much the program can do about being terminated without its crash handler being invoked.

In addtion to chkdsk run sfc /scannow as admin. Doublecheck BIOS (memory timing settings for example) and/or disable overclocking etc.

https://ufile.io/w4pkf8yx Heres the real time log Dyndolod still doesnt make any normal logs. and yes there are other logs from the event viewer around the same 1331 timestamp. The system scan did find some corrupt files and has repaired them, i am now going to check my memory XMP.

Report1.txt Report2.txt Report3.txt

Edited November 28, 2022 by IX_Flipyap

[sheson]

1 hour ago, IX_Flipyap said:

https://ufile.io/w4pkf8yx Heres the real time log Dyndolod still doesnt make any normal logs. and yes there are other logs from the event viewer around the same 1331 timestamp. The system scan did find some corrupt files and has repaired them, i am now going to check my memory XMP.

Report1.txt 16.17 kB · 1 download Report2.txt 16.1 kB · 1 download Report3.txt 16.1 kB · 1 download

As MO2 mentions there is still a (or more) TexConvx64.exe active when this happens. Can you check in Windows task manager it/they just linger around or eventually dissapear?

Add LockTexconv=1 below [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and see if it makes a difference.

If not, use task manager to keep an eye on memory usage of DynDOLODx64.exe and any spawned TexConvx64.exe and LODGenx64.exe processes with task manager.

[IX_Flipyap]

1 hour ago, sheson said:

As MO2 mentions there is still a (or more) TexConvx64.exe active when this happens. Can you check in Windows task manager it/they just linger around or eventually dissapear?

Add LockTexconv=1 below [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and see if it makes a difference.

If not, use task manager to keep an eye on memory usage of DynDOLODx64.exe and any spawned TexConvx64.exe and LODGenx64.exe processes with task manager.

It finally generated the LOD successfully. im not sure if LockTexconv, or changing my XMP profile from 1 to 2 fixed the issue. but tysm for all the help! this was an annoying two days.