DynDOLOD 3.00 Alpha 180

[sheson]

7 minutes ago, NeedsMoreBirds said:

After stopping and disabling AMD's hotkey utility, setting DynDOLOD, TexGen, Texconv and xLODGen to run as an admin, and adding the LockTexconv=1 line to the .ini, the program ran to completion in just under 18 minutes and failed to generate objects for Solstheim. It looks like that's the only location it's having trouble with.

The debug log was far too large to attach here or in paste.ee, so here it is on ufile.io.

Also upload E:\Modding\DynDOLOD\Logs\LODGen_SSE_DLC2SolstheimWorld_log.txt
Check Windows Event log a related entry for LODGenx64Win.exe and copy/paste or upload that as well.

You had an eye on total memory usage of everything in task manager when it happened? C000005 can memory or CPU related in high stress situations if random.

Start DynDOLOD in expert mode https://dyndolod.info/Help/Expert-Mode
Only select  DLC2SolstheimWorld and then click Execute LODGen to only run that again. If it runs through without error just by itself, the output is complete and can be used.

[PurpleYellowRosa]

17 hours ago, sheson said:

Thanks.

This test version should fix that new access violation. https://mega.nz/file/1dIGSI7S#hOL6CGqiteRyrdHTOJ38I7K6OtVC4VL7EVgrA2jGwwQ

Upload debug log also if it runs through without a problem.

It worked (cheers!), but didn't generate a debug log for whatever reason. The file is there, there's just no text in it.

[NeedsMoreBirds]

11 hours ago, sheson said:

Also upload E:\Modding\DynDOLOD\Logs\LODGen_SSE_DLC2SolstheimWorld_log.txt
Check Windows Event log a related entry for LODGenx64Win.exe and copy/paste or upload that as well.

You had an eye on total memory usage of everything in task manager when it happened? C000005 can memory or CPU related in high stress situations if random.

Start DynDOLOD in expert mode https://dyndolod.info/Help/Expert-Mode
Only select  DLC2SolstheimWorld and then click Execute LODGen to only run that again. If it runs through without error just by itself, the output is complete and can be used.

Here's the Windows event log for LODGENx64Win.exe:

Quote

Application: LODGenx64Win.exe
CoreCLR Version: 6.0.1322.58009
.NET Version: 6.0.13
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF979DD9370 (00007FF979D30000) with exit code 80131506.

I wasn't keeping an eye on memory usage at the time, but I have 64GB so I don't believe a memory shortage would be a factor. Expert mode is already set to 1 in the .ini, too.

LOD for only DLC2SolstheimWorld generated without issue, but it looks like I'm running an outdated version of .NET v6, so I'm going to update that and rerun the whole thing after I post this.

LODGen_SSE_DLC2SolstheimWorld_log.txt

[Ran]

Hoping you can point me in the right direction or give me a few ideas to try.  I am using SkyrimVR and the last working copy of NG DLL's that I could use was Alpha 5.  When using any past that (6, 7, or 8), I CTD right before the SkyrimVR load screen.  If I load ENB, the CTD is after the ENB splash screen and before the VR load screen.  I removed all mods except SKSEVR, Crash Logger, VR Address Library, VRIK, Dyndolod Resources & DLL NG #, with the same CTD.  I reinstalled MS C++ and Runtime 6, disabled antivirus. reset NVIDIA profiler to default values and ran a Windows memory test. Still CTD.  If I disable the DLL NG and start, everything is fine.  I also have a crashdump log that I added to the combined logs.

 

Thanks in advance for the help,

 

 

 

Combined logs.txt

[sheson]

6 hours ago, PurpleYellowRosa said:

It worked (cheers!), but didn't generate a debug log for whatever reason. The file is there, there's just no text in it.

Maybe the drive was full when it tried to write it? Is there a new/updated bugreport.txt with the time stamp of the tool closing?

In any case, if generation went through and the plugins saved without error all is good.

I just would have liked to check something in the debug log, but do not worry about it. Enjoy.

[sheson]

4 hours ago, NeedsMoreBirds said:

Here's the Windows event log for LODGENx64Win.exe:

I wasn't keeping an eye on memory usage at the time, but I have 64GB so I don't believe a memory shortage would be a factor. Expert mode is already set to 1 in the .ini, too.

LOD for only DLC2SolstheimWorld generated without issue, but it looks like I'm running an outdated version of .NET v6, so I'm going to update that and rerun the whole thing after I post this.

LODGen_SSE_DLC2SolstheimWorld_log.txt 32.53 kB · 0 downloads

The log just stops, so no useful information and the event log also points to internal .Net problem.
If total memory usage is fine, you could double check that CPU and memory settings, cooling, overclocking etc. are stable.

You can install the latest .Net 7 as it typically supports of all former versions.

Since, it ran through without a problem you now should have a complete LOD patch. You might as well just play now and not worry too much about a hard to troubleshoot issue that happens sporadically.

[NeedsMoreBirds]

39 minutes ago, sheson said:

The log just stops, so no useful information and the event log also points to internal .Net problem.
If total memory usage is fine, you could double check that CPU and memory settings, cooling, overclocking etc. are stable.

You can install the latest .Net 7 as it typically supports of all former versions.

Since, it ran through without a problem you now should have a complete LOD patch. You might as well just play now and not worry too much about a hard to troubleshoot issue that happens sporadically.

Running DynDOLOD after updating to the latest version of .NET 6 let it complete properly, so I think the outdated dependency was the problem. Thanks for helping me figure this out! Now I can play and my game looks fantastic.

I'll update to .NET 7 just in case I end up needing to run it again in the future.

[chemistofgor]

Hello. I'm having Texgen hang on a texture in the latest version, all updated  including my GPU drivers. It eventually completes, then DyndoLOD will fail after refusing to launch the LOD window for tamriel, then tamriel will show up as failed at the end. I have tried turning off my anti-virus, adding the rules under [Texgen]:
LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
TexconvAdapterIndex=-1

nothing helps. texgen hangs, then suddenly completes, and it fails in DyndoLOD.

Here are my logs:
https://drive.google.com/drive/folders/1WWfnAQba0kEEn_z4ElGWIp16ZVVeiCPu?usp=sharing

[sheson]

4 hours ago, chemistofgor said:

Hello. I'm having Texgen hang on a texture in the latest version, all updated  including my GPU drivers. It eventually completes, then DyndoLOD will fail after refusing to launch the LOD window for tamriel, then tamriel will show up as failed at the end. I have tried turning off my anti-virus, adding the rules under [Texgen]:
LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
TexconvAdapterIndex=-1

nothing helps. texgen hangs, then suddenly completes, and it fails in DyndoLOD.

Here are my logs:
https://drive.google.com/drive/folders/1WWfnAQba0kEEn_z4ElGWIp16ZVVeiCPu?usp=sharing

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug logs to also upload.
Obviously also upload E:\HaydsModlist\Tools\DynDOLOD 3\Logs\LODGen_SSE_Tamriel_log.txt as explained.

Also upload E:\HaydsModlist\Tools\DynDOLOD 3\Edit Scripts\Export\LODGen_TES5VR_ObjectAtlasMap_Tamriel.txt

TexGen does not hang when it completes. It is waiting for texconv to convert textures. Texconv will take longer when it does not use the GPU or when instructing to only run one at a time.

[chemistofgor]

Thank you! Here's the Texgen report: (too big to attach)
https://drive.google.com/drive/folders/1WWfnAQba0kEEn_z4ElGWIp16ZVVeiCPu?usp=sharing

[sheson]

1 hour ago, chemistofgor said:

Thank you! Here's the Texgen report: (too big to attach)
https://drive.google.com/drive/folders/1WWfnAQba0kEEn_z4ElGWIp16ZVVeiCPu?usp=sharing

"TexGen completed successfully".
As already explained, TexGen waits for Texconv to convert textures. If you want it to complete faster, then allow it to use GPU and/or allow Texconv and/or TexGen to do more things in parallel. Though 3 minutes seems acceptable, considering.

[chemistofgor]

I know what you mean. 3 minutes is actually too fast, based on previous runs. the issue is that i dont think it is generating everything it needs to. it gets stuck on one asset at around 2 minutes, then when i run dyndolod, it doesnt make the lods for tamriel. the window never opens.

[sheson]

11 minutes ago, chemistofgor said:

I know what you mean. 3 minutes is actually too fast, based on previous runs. the issue is that i dont think it is generating everything it needs to. it gets stuck on one asset at around 2 minutes, then when i run dyndolod, it doesnt make the lods for tamriel. the window never opens.

TexGen does not get stuck. TexGen completes successfully.
According to the log messages it does not create a few billboards because they are missing full textures. https://dyndolod.info/Messages/File-Not-Found-Textures.
Stitched and rendered generated without errors or warnings.

[chemistofgor]

this may help, from dyndolod:
[16:01] <Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned 427. Check E:\HaydsModlist\Tools\DynDOLOD 3\Logs\LODGen_SSE_Tamriel_log.txt>
[16:01] Error: LOLODGen_SSE_Tamriel_log.txtDGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)

by the way, thanks for helping!

[sheson]

3 minutes ago, chemistofgor said:

this may help, from dyndolod:
[16:01] <Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned 427. Check E:\HaydsModlist\Tools\DynDOLOD 3\Logs\LODGen_SSE_Tamriel_log.txt>
[16:01] Error: LOLODGen_SSE_Tamriel_log.txtDGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)

by the way, thanks for helping!

Read what I wrote in this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-131/?do=findComment&comment=273244