DynDOLOD 3.00 Alpha 190

[sheson]

  On 1/13/2023 at 9:05 PM, MinhazMurks said:

Thanks a lot for your reply!

Oops wrong links sorry: 

https://drive.google.com/file/d/19vEvF3V1EAIdSOBBKRP2EefYMwF_Xtz1/view?usp=share_link

https://drive.google.com/file/d/1bydob-ATzpbQNQq8uJOtQpFch1aTdqFb/view?usp=share_link

I did read the part about the memory, and I'm ok with high memory usage and waiting. Usually memory usage is about max for me (90%+) but the cpu usage usually is under 15% which is what I'm confused about a little bit. It seems to me that something is preventing it from running as fast as it could, is this cpu usage normal? And do you have any other suggestions for what I could try? 

 

  DynDOLOD_SSE.ini 20.88 kB · 0 downloads DynDOLOD.ini

Expand  

There is most likely memory trashing. You have too many LODGens with too many threads and not enough memory for them all.

That is why you need to limit the amount of concurrent LODGens and most likely more importantly should change the threadsplit.

Keep in mind, you are generating grass LOD with LOD density 100% (and whatever full grass density), ultra tree LOD etc. times 5 for the different seasons. It will take a "while".

[MinhazMurks]

Ok great, I will change these settings, thanks again for getting back to me! I am willing to wait long, I'm ok with leaving it for even multiple days if necessary I just want to make sure it's doing it optimally

[PhxFuryKnight]

Helloooooo! 
Does anyone know any workarounds for generating LOD through DynDOLOD with the new 7900XT graphics card? 
As suggested, AMD Adrenalin Driver 22.5.1 is unsupported for this specific GPU, as it will not even install. I continually receive the OpenGL Invalid Operation error with this graphics card, but it did work when I had a Strix 3080. 

[sheson]

  On 1/14/2023 at 6:25 AM, PhxFuryKnight said:

Helloooooo! 
Does anyone know any workarounds for generating LOD through DynDOLOD with the new 7900XT graphics card? 
As suggested, AMD Adrenalin Driver 22.5.1 is unsupported for this specific GPU, as it will not even install. I continually receive the OpenGL Invalid Operation error with this graphics card, but it did work when I had a Strix 3080. 

Expand  

Read the first post which log, debug log and bugreport.txt to upload when making posts.

https://dyndolod.info/Messages/Exceptions#OpenGL-invalid-operation, https://dyndolod.info/Official-DynDOLOD-Support-Forum

[PhxFuryKnight]

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

Read the first post which log, debug log and bugreport.txt to upload when making posts.

https://dyndolod.info/Messages/Exceptions#OpenGL-invalid-operation, https://dyndolod.info/Official-DynDOLOD-Support-Forum

Expand  

You already solved my problem when someone else made a post with the same error on a 7900XTX. 

You uploaded a stitched.frag file which I used to successfully use Dyndolod on the latest Adrenalin driver. 

[sheson]

  On 1/15/2023 at 9:28 AM, PhxFuryKnight said:

You already solved my problem when someone else made a post with the same error on a 7900XTX. 

You uploaded a stitched.frag file which I used to successfully use Dyndolod on the latest Adrenalin driver. 

Expand  

Read the first post which log and debug log to upload when making posts.

As explained on the first post, always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions.

https://dyndolod.info/Official-DynDOLOD-Support-Forum
Always use the latest DynDOLOD Standalone and DynDOLOD Resources version. Bugs and other problems may already be fixed or addressed.

https://dyndolod.info/Changelog
Version 3.00 Alpha 107
TexGen.exe - fixed stitched.frag compile error

Because you are refusing to upload the log and debug log, it is unclear what version you are using. It sounds like you are probably still using a long outdated version with other bugs and only updated the stitched.frag. If you are using the latest version and still needed that file, then something else might be wrong.

[MinhazMurks]

Hello Sheson!

I am getting this error: 

LODGenx64Win.exe returned C0000005

LODGenx64Win.exe failed to generate object LOD for one or more worlds

I saw that this error may be associated with c++ redistributable but i already downloaded the required ones and even repaired them. I also downloaded .net runtime 6.0. It's weird because it got past this point in a previous run but now it's getting stuck. One thing to note, I did debloat my nvidia drivers (uninstalled geforce experience but i have the latest GeForce Game Ready Driver 528.02 2023.1.5). Let me know if you need anything else.

Here are my log files: https://drive.google.com/file/d/1Pivtg1mWVJlWjI1CAOBemTqIjV6RDyEk/view?usp=share_link

 

Edited January 15, 2023 by MinhazMurks

[sheson]

  On 1/15/2023 at 3:30 PM, MinhazMurks said:

Hello Sheson!

I am getting this error: 

LODGenx64Win.exe returned C0000005

LODGenx64Win.exe failed to generate object LOD for one or more worlds

I saw that this error may be associated with c++ redistributable but i already downloaded the required ones and even repaired them. I also downloaded .net runtime 6.0. It's weird because it got past this point in a previous run but now it's getting stuck. One thing to note, I did debloat my nvidia drivers (uninstalled geforce experience but i have the latest GeForce Game Ready Driver 528.02 2023.1.5). Let me know if you need anything else.

Here are my log files: https://drive.google.com/file/d/1Pivtg1mWVJlWjI1CAOBemTqIjV6RDyEk/view?usp=share_link

Expand  

https://dyndolod.info/Help/LODGen
If happening randomly can be a sign of hardware issues like CPU or memory being unstable.

You can use expert mode and just rerun by usingt he button "Execute LODGen" for the Tamriel worldspace. See https://dyndolod.info/Help/LODGen,

Keep an eye on memory usage of the LODGenx64Win.exe in task manager. It may be because you set LODGenThreadSplit=24 in the DynDOLOD_SSE.INI. Try 0, 2, 4 or 8. Maybe 12. If you use expert mode and "Execute LODGen", set ThreadSplit= in ..\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_Tamriel.txt directly.

Test if it works when using LODGenx64.exe. To do that simply hide LODGenx64Win.exe. When you start DynDOLOD it should show that it uses the fallback as explained at top of https://dyndolod.info/Help/LODGen

[MinhazMurks]

Thanks again for your reply! I will lower the LODGenThreadSplit to 8.

  On 1/15/2023 at 4:13 PM, sheson said:

Test if it works when using LODGenx64.exe.

Expand  

Ok I will hide LODGen64Win.exe but I could've swore it was already using LODGenx64.exe based on the cmd window title... But I may be remembering wrong so I will try this. I'll let you know what happens!

Edited January 15, 2023 by MinhazMurks

[Zierry]

Just reporting i have also problem with "out of memory" error. One would expect 32GB ram is enough. Apparently not.

[Zierry]

  On 1/15/2023 at 7:44 PM, sheson said:

24 threads each requiring 2 GB or more = 48 GB.

Do I need to repeat the links to the explanations how to control the number of concurrent LODGen processes and their threads?

Expand  

That would be nice because searching weren't very useful so far. So it's by default set to 24 threads? That's a lot. As for log i am generating fresh one right now. It takes some time. 

[sheson]

  On 1/15/2023 at 8:08 PM, Zierry said:

That would be nice because searching weren't very useful so far. So it's by default set to 24 threads? That's a lot. As for log i am generating fresh one right now. It takes some time. 

Expand  

Read the first post which log, debug and LODGen log to upload when making posts.

You wrote "i have also problem ...", without providing any information, so the assumption was made you actually followed the two recent discussions about LODGen problems.

The default is not 24 threads. That number of cores or threads showed up in those discussions. The default number of main threads is number of cores.

So let me repeat from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-111/?do=findComment&comment=267693

Read https://dyndolod.info/FAQ "Long running time or output several GB in file size" and "High memory usage / Out of memory", especially these:
If too many concurrent LODGen processes running at the same time consume all available memory while generating seasons, limit their number per worldspace by changing the MaxLODGenPerWorldspace setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI.
If too many concurrent LODGen processes running at the same time consume all available memory, limit their total number by changing the MaxLODGen setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI.
If a single LODGen process uses a lot of memory, set LODGenThreadSplit in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI to a higher number. Set to the number of virtual cores for lowest possible memory usage. Since terrain LOD meshes are used to optimize object LOD, consider not enabling high resolution terrain LOD meshes (so it uses vanilla terrain meshes) while generating object LOD.

Also read the similar/related explanations at https://dyndolod.info/Help/Seasons#Out-of-Memory-errors and https://dyndolod.info/Help/LODGen#Out-of-Memory

[Zierry]

  On 1/15/2023 at 8:22 PM, sheson said:

Read the first post which log, debug and LODGen log to upload when making posts.

You wrote "i have also problem ...", without providing any information, so the assumption was made you actually followed the two recent discussions about LODGen problems.

The default is not 24 threads. That number of cores or threads showed up in those discussions. The default number of main threads is number of cores.

So let me repeat from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-111/?do=findComment&comment=267693

Read https://dyndolod.info/FAQ "Long running time or output several GB in file size" and "High memory usage / Out of memory", especially these:
If too many concurrent LODGen processes running at the same time consume all available memory while generating seasons, limit their number per worldspace by changing the MaxLODGenPerWorldspace setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI.
If too many concurrent LODGen processes running at the same time consume all available memory, limit their total number by changing the MaxLODGen setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI.
If a single LODGen process uses a lot of memory, set LODGenThreadSplit in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI to a higher number. Set to the number of virtual cores for lowest possible memory usage. Since terrain LOD meshes are used to optimize object LOD, consider not enabling high resolution terrain LOD meshes (so it uses vanilla terrain meshes) while generating object LOD.

Also read the similar/related explanations at https://dyndolod.info/Help/Seasons#Out-of-Memory-errors and https://dyndolod.info/Help/LODGen#Out-of-Memory

Expand  

https://ufile.io/po37t12r

https://pastebin.com/zwxBzM30

Here you go. Found only these two.  Is that normal debug file is so big? 

 

[sheson]

  On 1/15/2023 at 10:11 PM, Zierry said:

https://ufile.io/po37t12r

https://pastebin.com/zwxBzM30

Here you go. Found only these two.  Is that normal debug file is so big? 

Expand  

If there is a debug log for DynDOLOD there should be the normal log for DynDOLOD as well. If LODGen has been running, there should be a LODGen log, which will tell you the current threadsplit.

Read https://dyndolod.info/FAQ "High memory usage / Out of memory" 
If DynDOLOD runs out of memory while generating occlusion, see Out of Memory while Generating Occlusion Data.

https://dyndolod.info/Help/Occlusion-Data#Out-of-Memory-while-Generating-Occlusion-Data
Set OcclusionMaxThreadsObjectLOD=1 in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini in case the parallel reading of large object LOD meshes consumes too much memory.

[KlausNoxix]

Hello! I keep getting the following error: "DynDOLOD Resources SE core files are outdated." Even though im using the latest files from nexus.