DynDOLOD 3.00 Alpha 190

[Roastlawyer]

  On 6/29/2023 at 6:43 AM, sheson said:

When you close the tool via X top right it should also just save the log and debug log you could then upload instead.

Check in task manager if there are TexConv processes the tool might be waiting on.

Test with RenderSingle=1 added under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Expand  

Yesterday when it was freezing like that, pressing the X in the top right would cause the program to hang, then windows would say dyndolod stopped responding. I click end anyways, the main window would close and then a dyndolod process that could not be killed would hang around in task manager untill the PC was forcably restarted. When that happened the normal log files where not generated which is why you had my enable the realtime one before. Anyways I'll give the RenderSingle=1 line a try.

Alright tried again with the RenderSingle=1 line just below [DynDOLOD] in the _SSE.ini. It hung at [Tamriel] Creating texture atlas. In task manager I couldn't find any TexConv processes. After 25 minutes of DynDOLOD being at 0% cpu usage and no further additionsto the realtime log since it stalled I tried to stop generation. Pressing the X gave me the message about how generation would be incomplete, I accepted and now the dyndolod window is greyed out and the both the window and task manager say it's not responding. Pressing end task in task manager does nothing. Because of this I have no DynDOLOD_SSE__debug_log.txt, bugreport.txt, or DynDOLOD_SSE_log.txt.

Here is the realtime log https://drive.google.com/file/d/1fRTAGWFz2OUqAkvpQROdrmSYT77DmVBJ/view?usp=drive_link

[sheson]

  On 6/30/2023 at 1:22 AM, Roastlawyer said:

Yesterday when it was freezing like that, pressing the X in the top right would cause the program to hang, then windows would say dyndolod stopped responding. I click end anyways, the main window would close and then a dyndolod process that could not be killed would hang around in task manager untill the PC was forcably restarted. When that happened the normal log files where not generated which is why you had my enable the realtime one before. Anyways I'll give the RenderSingle=1 line a try.

Alright tried again with the RenderSingle=1 line just below [DynDOLOD] in the _SSE.ini. It hung at [Tamriel] Creating texture atlas. In task manager I couldn't find any TexConv processes. After 25 minutes of DynDOLOD being at 0% cpu usage and no further additionsto the realtime log since it stalled I tried to stop generation. Pressing the X gave me the message about how generation would be incomplete, I accepted and now the dyndolod window is greyed out and the both the window and task manager say it's not responding. Pressing end task in task manager does nothing. Because of this I have no DynDOLOD_SSE__debug_log.txt, bugreport.txt, or DynDOLOD_SSE_log.txt.

Here is the realtime log https://drive.google.com/file/d/1fRTAGWFz2OUqAkvpQROdrmSYT77DmVBJ/view?usp=drive_link

Expand  

Install latest graphics driver only. Disable all overclocking etc.

Add TextureCache=10 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Keep an eye on VRAM usage. Close other programs to free up VRAM usage if needed.

If no change, test with AtlasThreads=1 (and RenderSingle=1) added under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

[Katarsi]

I have some inquiries about Large Reference Bugs Workaround.

I have downloaded DynDOLOD DLL NG and Scripts 3.00, but I don't know how to use it. It says that large references need to be cleaned - but how?

The last time I generated LOD was last year, here is my log. My load order didn't change much regarding large reference offenders, although - how exactly do I find out exactly which mods have large reference bugs? Do I have to determine that and clean them before generating LOD, or will DynDOLOD do it by itself when I start it while the aforementioned script is active?

If it's of any significance, I'm on downgraded Skyrim - version 1.5.97 total, not "best of both worlds".

[Roastlawyer]

  On 6/30/2023 at 5:59 AM, sheson said:

Install latest graphics driver only. Disable all overclocking etc.

Add TextureCache=10 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Keep an eye on VRAM usage. Close other programs to free up VRAM usage if needed.

If no change, test with AtlasThreads=1 (and RenderSingle=1) added under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Expand  

Ensured my CPU overclock was disabled (was already running stock) and that MSI afterburner didn't currently have an GPU overclock set (It didn't)

updated Nvidia driver from 528.24 to 336.40  (latest one for 3080)
updated AMD APU Graphics driver from 22.20.27.09 (November 2022) to 22.49.57.05 (June 1 2023) (latest one for Ryzen 5600g)

Ran DynDOLOD (twice because I forgot to watch Vram usage the first time) Both times it got stuck at "[Tamriel] Creating texture atlas E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 128\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel_Glow.dds"
Vram usage never went above 1.6GB out of 10GB
Ram maxed out at 9.6GB used out of 31.8GB

 

Ran a 3rd time but with

[DynDOLOD]
TextureCache=10
RenderSingle=1

Instead of just RenderSingle=1 set in DynDOLOD_SSE.ini

That time it got further, getting to "[06:18] [DLC2SolstheimWorld] Creating texture atlas E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 128\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC2SolstheimWorld_Glow.dds 512 x 256" before CPU usage dropped to 0% and Vram usage dropped back to idle levels (0.5GB used)
No real change in amount of Vram or ram used

Ran a 4th time:

[DynDOLOD]
TextureCache=10
RenderSingle=1
AtlasThreads=1

Whoohoo! finally got a complete run. So that's quite nice. Vram usage was pretty much the same. Ram topped out ~13GB when it peaked, most of the time usage was still around 10GB.

Edit: Spelling/formatting

Edited June 30, 2023 by Roastlawyer

[sheson]

  On 6/30/2023 at 11:38 AM, Katarsi said:

I have some inquiries about Large Reference Bugs Workaround.

I have downloaded DynDOLOD DLL NG and Scripts 3.00, but I don't know how to use it. It says that large references need to be cleaned - but how?

The last time I generated LOD was last year, here is my log. My load order didn't change much regarding large reference offenders, although - how exactly do I find out exactly which mods have large reference bugs? Do I have to determine that and clean them before generating LOD, or will DynDOLOD do it by itself when I start it while the aforementioned script is active?

If it's of any significance, I'm on downgraded Skyrim - version 1.5.97 total, not "best of both worlds".

Expand  

https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
For the Large reference bugs workarounds check box and options to become available on the advanced mode window, the DynDOLOD DLL NG and Scripts must be installed and every plugin containing deleted references needs to be cleaned. [..] See the Prerequisites section of the Generation Instructions for more.

https://dyndolod.info/Generation-Instructions#Prerequisites
Finalize the load order. Install mods and their requirements. Sort and resolve conflicts. Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean [..] Cleaning of plugins that contain deleted large references is mandatory for the large reference bugs workarounds. The Batch Plugin Cleaner for Mod Organizer or the xEdit Cleaning Extension for Vortex help to automate some of that.

Every well made modding guide should include how to clean plugins, for example https://stepmodifications.org/wiki/SkyrimSE:2.2.0#Cleaning_Vanilla_Master_Plugins.

If you generated without the DynDOLOD DLL NG, look for log messages like https://dyndolod.info/Messages/Deleted-Reference

In regards which plugins cause large reference bugs, check the old log for related messages about large references. The Summary Of Messages should create a combined listing them under Large Reference Bugs. It should include messages like https://dyndolod.info/Messages/Overwritten-Large-Reference for example.

The point of the large reference bugs workarounds is that using plugins causing them should not require users having to do anything out of the ordinary.
It is still recommended for mod authors to avoid causing the bugs to minimize the number of workarounds needing to be applied, though.

[Katarsi]

Thank you sheson

My old Summary pages aren't working anymore due to time passed. However, what I managed to glean from my old log is that these have overwritten large references:

• JK Skyrim (definitely the worst offender, has the largest amount of large references)
• patch for JK Skyrim and eFPS (the patch obviously forwards JK's large reference bug)
• AI Overhaul (this one is weird)
• Dlizzio's Mesh Fixes
• Embers XD
• Lux Via
• Convenient Carriages
• Obsidian Mountain Fogs
• Riverside Lodge
• Depths of Skyrim (second worst offender after JK Skyrim)
• 3D Trees and Plants
• Cutting Room Floor
• Better Dynamic Ash
• The Blackest Reaches

Maybe there are more tiny ones, couldn't sift through the log so much, its quite big.

So regular Quick Cleaning of these plugins will do the trick? I'll make backups of course.

[sheson]

  On 6/30/2023 at 1:09 PM, Katarsi said:

Thank you sheson

My old Summary pages aren't working anymore due to time passed. However, what I managed to glean from my old log is that these have overwritten large references:

• JK Skyrim (definitely the worst offender, has the largest amount of large references)
• patch for JK Skyrim and eFPS (the patch obviously forwards JK's large reference bug)
• AI Overhaul (this one is weird)
• Dlizzio's Mesh Fixes
• Embers XD
• Lux Via
• Convenient Carriages
• Obsidian Mountain Fogs
• Riverside Lodge
• Depths of Skyrim (second worst offender after JK Skyrim)
• 3D Trees and Plants
• Cutting Room Floor
• Better Dynamic Ash
• The Blackest Reaches

Maybe there are more tiny ones, couldn't sift through the log so much, its quite big.

So regular Quick Cleaning of these plugins will do the trick? I'll make backups of course.

Expand  

According to the log, the only plugin left that has a deleted reference would be The Only Cure - Man_Peryite Shrine Patch.esp
https://dyndolod.info/Messages/Deleted-Reference

[Katarsi]

  On 6/30/2023 at 2:07 PM, sheson said:

According to the log, the only plugin left that has a deleted reference would be The Only Cure - Man_Peryite Shrine Patch.esp
https://dyndolod.info/Messages/Deleted-Reference

Expand  

Thank you for narrowing it down for me! I'll clean that one too  

[Katarsi]

@sheson I generated LOD with DLL NG script active, it went great. Lasted around 50min on my 415 plugins load order. The only errors about deleted stuff is something I removed intentionally - a couple of trees from a mod, that were added by that mod (regular ESP); they were only decoration and didn't reference any other function in that mod.

Thanks to the report, I also fixed some NiNode shapes for some flowers and converted them to BSFadeNode.

As for large reference bugs, the process basically mentioned only game masters.

I've noticed that there was a generated mesh that required a texture that TexGen didn't create in the first place:

Warning: File not found textures\architecture\highhrothgar\hhwin02noalpha_n.dds. Used by meshes\lod\highhrothgar\highhrothgarentrance01glow_lod_2.nif Skyrim.esm HighHrothgarEntrance01 [STAT:0008118C]

I also noticed that TexGen had created some textures in 2K, even though I specified beforehand that the limit is 1K. My TexGen preparation looked very similar to this.

Here's my log, if you're interested to see all that went on.

EDIT: The game looks awesome.

Edited June 30, 2023 by Katarsi

[Holt59]

Hi,

I'm trying to run TexGen and DynDOLOD 3 alpha 128 and right now TexGen is crashing when starting to generate texture. The Window event viewer shows

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3640, time stamp: 0x6496035a
Exception code: 0xc0000005
Fault offset: 0x000000000155191a
Faulting process id: 0x0x6D08
Faulting application start time: 0x0x1D9AB821A45779D
Faulting application path: D:\Utilities\DynDOLOD 3\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3917166697074d95\nvoglv64.dll
Report Id: 7b4587b6-10c3-4330-a247-78f05062c0ba
Faulting package full name: 
Faulting package-relative application ID: 

Unfortunately I don't have any logs under TexGen... I have latest drivers for everything, in particular NVidia. I'm running TexGen64 through MO2.

Any idea how could I go about investigating this?

[Mush2023]

  On 6/30/2023 at 7:59 PM, Holt59 said:

Hi,

I'm trying to run TexGen and DynDOLOD 3 alpha 128 and right now TexGen is crashing when starting to generate texture. The Window event viewer shows

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3640, time stamp: 0x6496035a
Exception code: 0xc0000005
Fault offset: 0x000000000155191a
Faulting process id: 0x0x6D08
Faulting application start time: 0x0x1D9AB821A45779D
Faulting application path: D:\Utilities\DynDOLOD 3\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3917166697074d95\nvoglv64.dll
Report Id: 7b4587b6-10c3-4330-a247-78f05062c0ba
Faulting package full name: 
Faulting package-relative application ID: 

Unfortunately I don't have any logs under TexGen... I have latest drivers for everything, in particular NVidia. I'm running TexGen64 through MO2.

Any idea how could I go about investigating this?

Expand  

I'm having the same exact issue running TexGen64: no error logs, creates billboards, app crashes silently when it starts generating textures.  I checked windows event as well, and get the same message.  Running through MO2.  Windows 11, using the latest version of DynDOLOD 3, latest resources, scripts, dll file.

[sheson]

  On 6/30/2023 at 6:36 PM, Katarsi said:

@sheson I generated LOD with DLL NG script active, it went great. Lasted around 50min on my 415 plugins load order. The only errors about deleted stuff is something I removed intentionally - a couple of trees from a mod, that were added by that mod (regular ESP); they were only decoration and didn't reference any other function in that mod.

Thanks to the report, I also fixed some NiNode shapes for some flowers and converted them to BSFadeNode.

As for large reference bugs, the process basically mentioned only game masters.

I've noticed that there was a generated mesh that required a texture that TexGen didn't create in the first place:

Warning: File not found textures\architecture\highhrothgar\hhwin02noalpha_n.dds. Used by meshes\lod\highhrothgar\highhrothgarentrance01glow_lod_2.nif Skyrim.esm HighHrothgarEntrance01 [STAT:0008118C]

I also noticed that TexGen had created some textures in 2K, even though I specified beforehand that the limit is 1K. My TexGen preparation looked very similar to this.

Here's my log, if you're interested to see all that went on.

EDIT: The game looks awesome.

Expand  

When llarge reference bugs workarounds, the log will list all cells that contain large reference bugs, e.g. that will exhibit texture flicker etc. and not the large references causing the bugs anymore. https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing

The texture hhwin02noalpha_n.dds is installed as part of the DynDOLOD Resources "High Hrothgar Windows Glow" option. Do not modify anything in the installed DynDOLOD Resources manually after its installation. https://dyndolod.info/Help/DynDOLOD-Resources

https://dyndolod.info/Help/TexGen#Stitched-Object-LOD-Textures
This sets the typical base size of the generated object LOD textures. The actual texture resolutions varies by texture as defined by the TexGen configuration files.
https://dyndolod.info/Help/TexGen#Rendered-Object-LOD-Textures
This sets the typical base size of the generated object LOD textures. The actual texture resolutions varies by texture as defined by the scale defined in the special models.

https://dyndolod.info/Messages/Deleted-Reference. Clean all plugins with deleted references. It fast and simple to do.

https://dyndolod.info/Messages/Wrong-Billboard-Path. Do not install any third party billboards and remove wrong billboard files at wrong paths. Use TexGen to generate billboards.

Click the links read the pages that open for further explanations.

[sheson]

  On 6/30/2023 at 7:59 PM, Holt59 said:

Hi,

I'm trying to run TexGen and DynDOLOD 3 alpha 128 and right now TexGen is crashing when starting to generate texture. The Window event viewer shows

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3640, time stamp: 0x6496035a
Exception code: 0xc0000005
Fault offset: 0x000000000155191a
Faulting process id: 0x0x6D08
Faulting application start time: 0x0x1D9AB821A45779D
Faulting application path: D:\Utilities\DynDOLOD 3\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3917166697074d95\nvoglv64.dll
Report Id: 7b4587b6-10c3-4330-a247-78f05062c0ba
Faulting package full name: 
Faulting package-relative application ID: 

Unfortunately I don't have any logs under TexGen... I have latest drivers for everything, in particular NVidia. I'm running TexGen64 through MO2.

Any idea how could I go about investigating this?

Expand  

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the real time log in case the tool is being terminated and can not write its log files.

Use search https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. https://stepmodifications.org/forum/search/?q=nvoglv64.dll&quick=1&type=forums_topic&nodes=223&updated_after=any&sortby=newest

Add RenderSingle=1 under [TexGen] in D:\Utilities\DynDOLOD 3\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people in the past that also had an exception in the NVIDIA driver nvoglv64.dll

[Holt59]

  On 7/1/2023 at 6:14 AM, sheson said:

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the real time log in case the tool is being terminated and can not write its log files.

Use search https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. https://stepmodifications.org/forum/search/?q=nvoglv64.dll&quick=1&type=forums_topic&nodes=223&updated_after=any&sortby=newest

Add RenderSingle=1 under [TexGen] in D:\Utilities\DynDOLOD 3\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people in the past that also had an exception in the NVIDIA driver nvoglv64.dll

Expand  

Thanks, using `RenderSingle=1` fixed the issue for me.

[Katarsi]

  On 7/1/2023 at 6:07 AM, sheson said:

https://dyndolod.info/Messages/Wrong-Billboard-Path. Do not install any third party billboards and remove wrong billboard files at wrong paths. Use TexGen to generate billboards.

Expand  

Ah, well, as for those tree billboards... I think I was confused by the description here: https://dyndolod.info/Help/Ultra-Tree-LOD  I thought that installing and activating Skyrim3DTrees and Plants 3dLOD Resources should be done, but apparently not. Myrkvior 3D lods were okay though.

...Do I have to redo TexGen and DynDOLOD now? 

  On 7/1/2023 at 6:07 AM, sheson said:

The texture hhwin02noalpha_n.dds is installed as part of the DynDOLOD Resources "High Hrothgar Windows Glow" option. Do not modify anything in the installed DynDOLOD Resources manually after its installation. https://dyndolod.info/Help/DynDOLOD-Resources

Expand  

I didn't check this option while installing DynDOLOD Resources, maybe that's why the texture is missing. ...If I have to redo TexGen and DynDOLOD, I suppose I'll have to reinstall DynDOLOD Resources too with this option checked beforehand...

  On 7/1/2023 at 6:07 AM, sheson said:

https://dyndolod.info/Messages/Deleted-Reference. Clean all plugins with deleted references. It fast and simple to do.

Expand  

Okay fine, I'll replace "Deleted" with "Initially Disabled" (and the "set opposite to playerref" thing)