DynDOLOD 3.00 Alpha 182

[sheson]

15 minutes ago, Thaumatarge said:

I would post bugreport.txt if there was any, I do not want to risk running the software again when it causes my computer to freeze up and my screen to go black despite the fact it has never done that when I used Alpha 74 and prior. The "Quality" is the Tile size, which when reduced is supposed to use less resources, and it took longer for it to reach the point where the screen goes black and applications crash in the background, so I genuinely believe there is something going on with the memory usage of the software where it leaks! I have 16GB of RAM, I don't think that's not enough, especially when again, any version prior to the latest one (Alpha 77) hasn't caused me any trouble like this! If you insist that I post logs for a problem like this, then I will try to run the software again until it spits out an error of some kind, but I am scared of the prospect that it will somehow harm my computer in the process!

EDIT: I also use the 64 bit version of the software, didn't try the other one as I have 64 bit Windows and more than 4GB of RAM.

BSOD or anything similar are hardware, BIOS Setting, OS or driver problems.

Have you actually tracked main or video memory usage?

[Thaumatarge]

24 minutes ago, sheson said:

BSOD or anything similar are hardware, BIOS Setting, OS or driver problems.

Have you actually tracked main or video memory usage?

I have tried to track memory, but I have not looked in to video stuff, I will do some tests later, but what is surprising to me is that it is only happening in the more recent version... Is Alpha 74 compatible with resources alpha 22?

Edit: The main RAM usage just has the software eat ALL of the RAM really really quicky.

Edited March 7, 2022 by Thaumatarge
more info

[sheson]

39 minutes ago, Thaumatarge said:

I have tried to track memory, but I have not looked in to video stuff, I will do some tests later, but what is surprising to me is that it is only happening in the more recent version... Is Alpha 74 compatible with resources alpha 22?

Edit: The main RAM usage just has the software eat ALL of the RAM really really quicky.

TexGenx64 from Alpha-77 peaks at 2GB main memory with all generation options checked and default 256 resolution settings.

Do you have any 4k, 8k or 16k full textures for anything?

Upload the log from the last session, the entire debug log and bugreport.txt if it exists.

TexGen does not uses or require DynDOLOD Resources.

People reported problems caused by 3rd party crapware that installs in addition to graphics drivers before.

[Thaumatarge]

47 minutes ago, sheson said:

TexGenx64 from Alpha-77 peaks at 2GB main memory with all generation options checked and default 256 resolution settings.

Do you have any 4k, 8k or 16k full textures for anything?

Upload the log from the last session, the entire debug log and bugreport.txt if it exists.

TexGen does not uses or require DynDOLOD Resources.

People reported problems caused by 3rd party crapware that installs in addition to graphics drivers before.

TexGen isn't giving me issues, it's when I run DynDOLOD. I will have to try to generate stuff again because loading the software to check what I meant by quality cleared the debug log.

[sheson]

10 minutes ago, Thaumatarge said:

TexGen isn't giving me issues, it's when I run DynDOLOD. I will have to try to generate stuff again because loading the software to check what I meant by quality cleared the debug log.

Upload the entire log from the last session of interest, the entire debug log and bugreport.txt if it exists so I do not have make assumptions.

[Thaumatarge]

Here are all logs that are in the logs folder.

Logs.rar

[sheson]

12 minutes ago, Thaumatarge said:

Here are all logs that are in the logs folder.

Logs.rar 656.66 kB · 0 downloads

I would need the debug log from a session that had the problem.

[Thaumatarge]

11 minutes ago, sheson said:

I would need the debug log from a session that had the problem.

Right, and since it has happened to me every time I tried to generate it, I can just try generating stuff again to get a new log with the same problem.

[Thaumatarge]

https://ufile.io/d4pp7pb8 Here you go, logs from a session that once again almost killed my computer. Here is also a picture of when I decided to manually stop all the Tamriel LODGENs because they crashed explorer.exe and didn't let it restart because there was no memory free to actually do anything. I could run it again and post a picture of the Task Mangager, but I am honestly starting to lose hope of being able to explain my problem.

[sheson]

35 minutes ago, Thaumatarge said:

https://ufile.io/d4pp7pb8 Here you go, logs from a session that once again almost killed my computer. Here is also a picture of when I decided to manually stop all the Tamriel LODGENs because they crashed explorer.exe and didn't let it restart because there was no memory free to actually do anything. I could run it again and post a picture of the Task Mangager, but I am honestly starting to lose hope of being able to explain my problem.

Your first post was about an "OpenGL: Out of Memory". LODGen does not use the GPU and can not report OpenGL errors. I had to request uploading of logs 3 times.

Now that I have a debug log from DynDOLOD all I can see that in the last session there is no OpenGL error and DynDOLOD ran without error to the part where the LODGen processes for Tamriel were ended by the user. It seems the "problem" is that DynDOLOD starts 5  (and then later some more) separate LODGen processes to generate season LODs for Tamriel.

If the PC/OS can not handle the CPU and memory being used by several different programs at the same time, set the number of virtual CPU cores (12 in this case I believe) for LODGenThreadSplit in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini That should reduce the number of threads each LODGen creates which should reduce memory requirements.

Let the OS handle virtual memory settings automatically.

Use print screen key to make screenshots.

[cajeffreys]

Alright, taking a few steps back to get some clarification since I'm going through this mostly for Season's of Skyrim.  xLODGen: should I have generated default files in addition to spring, summer, autumn and winter? If I do need this can I just run xLODGen for it and add the output to my existing output?  xLODGen: Do I need to rerun xLODGen if I change a city texture pack or does that make any difference?  TextGen: Should the files output from xLODGen be activated when running it?

I'm going to leave the textures I copied out where they are while running TextGen from MO2, maybe that will solve my issue.

Edited March 7, 2022 by cajeffreys
more questions

[Thaumatarge]

10 minutes ago, sheson said:

Your first post was about an "OpenGL: Out of Memory". LODGen does not use the GPU and can not report OpenGL errors. I had to request uploading of logs 3 times.

Now that I have a debug log from DynDOLOD all I can see that in the last session there is no OpenGL error and DynDOLOD ran without error to the part where the LODGen processes for Tamriel were ended by the user. It seems the "problem" is that DynDOLOD starts 5  (and then later some more) separate LODGen processes to generate season LODs for Tamriel.

If the PC/OS can not handle the CPU, GPU, memory being used by several different programs at the same time, set the number of virtual CPU cores (12 in this I believe) for LODGenThreadSplit in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

Let the OS handle virtual memory settings automatically.

Use print screen key to make screenshots.

I will try that. I couldn't use printscreen because I would have no way to actually save a screenshot of it because, again, the processes ate up all of the RAM and it crashed most of my programs, including explorer.exe

The OpenGL: Out Of Memory happened once and I lost the log where it happened, but every time I tried to generate stuff it just froze up my computer and I had to either restart it or manually shut everything down.

[sheson]

32 minutes ago, cajeffreys said:

Alright, taking a few steps back to get some clarification since I'm going through this mostly for Season's of Skyrim.  xLODGen: should I have generated default files in addition to spring, summer, autumn and winter? If I do need this can I just run xLODGen for it and add the output to my existing output?  xLODGen: Do I need to rerun xLODGen if I change a city texture pack or does that make any difference?  TextGen: Should the files output from xLODGen be activated when running it?

I'm going to leave the textures I copied out where they are while running TextGen from MO2, maybe that will solve my issue.

Terrain LOD texture generation uses landscape full textures. The only connection between terrain LOD and DynDOLOD is when LODGen is generating object LOD meshes it uses the terrain LOD meshes to optimize the object LOD meshes. See https://dyndolod.info/Generation-Instructions#Prerequisites

TexGen generates object LOD textures and tree/grass LOD billboards which are used by DynDOLOD for object LOD (grass LOD) and tree LOD generation. https://dyndolod.info/Help/TexGen

Which seasons require terrain LOD generated for depends on the available swap data and po3_SeasonsOfSkyrim.ini settings.
https://stepmodifications.org/forum/topic/16730-xlodgen-with-seasons-of-skyrim-tots/

[jkp993]

Hi sheson,

I'm trying to run dyndolod but my RAM (16GB) and disk (1TB SSD) are at 100%. Dyndolod log when it was running showed this error:

<Warning: Error when loading "meshes\terrain\Tamriel\objects\Tamriel.4.-20.-20.bto": Error reading NIF block 83 BSSubIndexTriShape: Out of memory>

There was no progress for >20 mins. My PC became very slow, like very slow response of cursor etc.

I ended up terminating through task manager. Please help.

Which logs/files do I attach here?

Edited March 7, 2022 by jkp993

[BrotherShamus]

Is there any way for me to get the older versions of Dyndolod 3 and Dyndolod 3 resources so I can test the issue I'm having?  I'm currently using Resources Alpha 22 and Dyndolod Alpha 77.  I've exhausted every troubleshooting step I can find (re-install, repair ,Net Framework 3.5 and 4.8) and the problem persists.  I was able to successfully generate LOD with the previous versions hours before I downloaded the new versions and just want to make sure I'm not having some strange interaction.  My only other option as far as I can tell is to format my hard drive.