DynDOLOD 3.00 Alpha 182

[sheson]

29 minutes ago, BrotherShamus said:

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.

Since you report an issue with LODGen.exeLODGenx64.exe, see what happen if you use the version included in the latest xLODGen terrain LOD beta.

It would be better to actually provide information about the error so whatever the problem can be fixed.

46 minutes ago, jkp993 said:

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?

Read the first post which log, debug log and bugreport.txt if it exists to upload.

Read https://dyndolod.info/Help/Occlusion-Data#Out-of-Memory-while-Generating-Occlusion-Data first.

[Thaumatarge]

 

28 minutes ago, sheson said:

Since you report an issue with LODGen.exeLODGenx64.exe, see what happen if you use the version included in the latest xLODGen terrain LOD beta.

It would be better to actually provide information about the error so whatever the problem can be fixed.

Read the first post which log, debug log and bugreport.txt if it exists to upload.

Read https://dyndolod.info/Help/Occlusion-Data#Out-of-Memory-while-Generating-Occlusion-Data first.

I am having pretty much the same issue as jkp993, this cannot be a random issue I am having, I run the program, it works just fine, then while generating Tamriel LODs it gets stuck, and only a moment ago I noticed my computer COMPLETELY FROZE and I had to forcefully restart it, thus I cannot provide any meaningful logs. 

The fix you have given me made it work slightly smoother, with the LODGEN not jumping around when generating Level 4 lods to generating Level 8 lods randomly (the logs I have already provided show that).

But what I have noticed in my testing is the fact that LODGEN allocates a lot of memory and uses none of it, sometimes having bursts of sudden memory usage but in general not using any memory. I used the Performance Tracker program that's in windows to track this, it's more detailed for this stuff than Task Manager. I would provide a printscreen screenshot, but sadly, printscreen doesn't work when my computer is completely frozen. Under the "Confirmed" memory, which summarizes all the allocated memory, all 5 windows allocate more than 3GB of RAM eventually, with some going as high as 9GB of RAM, but only using around 1 to 100 MB of it in random bursts. The allocated memory always exceeds actual memory available.

[jkp993]

36 minutes ago, sheson said:

Since you report an issue with LODGen.exeLODGenx64.exe, see what happen if you use the version included in the latest xLODGen terrain LOD beta.

It would be better to actually provide information about the error so whatever the problem can be fixed.

Read the first post which log, debug log and bugreport.txt if it exists to upload.

Read https://dyndolod.info/Help/Occlusion-Data#Out-of-Memory-while-Generating-Occlusion-Data first.

Thank you for the reply. The dyndolod logs are from a previous run only. In the ini do I also have to change OcclusionMaxThreadsTerrainLOD to 1? Right now it is -1. I'm confused since the file related to the error is in meshes\terrain\Tamriel\objects

[sheson]

25 minutes ago, Thaumatarge said:

 

I am having pretty much the same issue as jkp993, this cannot be a random issue I am having, I run the program, it works just fine, then while generating Tamriel LODs it gets stuck, and only a moment ago I noticed my computer COMPLETELY FROZE and I had to forcefully restart it, thus I cannot provide any meaningful logs. 

The fix you have given me made it work slightly smoother, with the LODGEN not jumping around when generating Level 4 lods to generating Level 8 lods randomly (the logs I have already provided show that).

But what I have noticed in my testing is the fact that LODGEN allocates a lot of memory and uses none of it, sometimes having bursts of sudden memory usage but in general not using any memory. I used the Performance Tracker program that's in windows to track this, it's more detailed for this stuff than Task Manager. I would provide a printscreen screenshot, but sadly, printscreen doesn't work when my computer is completely frozen. Under the "Confirmed" memory, which summarizes all the allocated memory, all 5 windows allocate more than 3GB of RAM eventually, with some going as high as 9GB of RAM, but only using around 1 to 100 MB of it in random bursts. The allocated memory always exceeds actual memory available.

You do not have pretty much the same issue as jkp993 as is clear by the log you uploaded. Since you kill the LODGen processes, the process never gets to read the object LOD bto meshes for the occlusion generation because it is aborted.

Multi-threaded parallel execution of code has no guaranteed execution order. There is no guarantee which LOD quad/level is generated next.

If you find a c# .net memory allocation / garbage collector not working or whatever, i suggest to make a report to its developer.

If the OS, PC can not handle x64 programs using CPU and memory at the same time, then do not generate all seasons all at the same time. You can temporarily halt a LODGen window execution by marking text in the command prompt window, then once another LODGen finished, hit enter key on that halted command prompt window.

Let the OS handle virtual memory settings.

19 minutes ago, jkp993 said:

Thank you for the reply. The dyndolod logs are from a previous run only. In the ini do I also have to change OcclusionMaxThreadsTerrainLOD to 1? Right now it is -1. I'm confused since the file related to the error is in meshes\terrain\Tamriel\objects

As you can see by the folder name and the *.BTO suffix the file is an object LOD mesh. By the time the process reads them it already read the terrain LOD meshes.

You are generating grass LOD, right?

[Thaumatarge]

10 minutes ago, sheson said:

You do not have pretty much the same issue as jkp993 as is clear by the log you uploaded. Since you kill the LODGen processes, the process never gets to read the object LOD bto meshes for the occlusion generation because it is aborted.

Multi-threaded parallel execution of code has no guaranteed execution order. There is no guarantee which LOD quad/level is generated next.

If you find a c# .net memory allocation / garbage collector not working or whatever, i suggest to make a report do its developer.

If you OS, PC can not handle x64 programs using CPU and memory at the same time, then do not generate all seasons all at the same time. You can temporarily halt a LODgen window execution by marking text in the command prompt window, then once a another LODGen finished, hint enter on that command prompt window.

Let the OS handle virtual memory settings.

I will give that a try, but I have been struggling with this for hours and nothing so far has worked. I cannot provide logs if the program cannot either crash to give an error, or finish to give a finished log, because the computer just freezes.

[jkp993]

12 minutes ago, sheson said:

You do not have pretty much the same issue as jkp993 as is clear by the log you uploaded. Since you kill the LODGen processes, the process never gets to read the object LOD bto meshes for the occlusion generation because it is aborted.

Multi-threaded parallel execution of code has no guaranteed execution order. There is no guarantee which LOD quad/level is generated next.

If you find a c# .net memory allocation / garbage collector not working or whatever, i suggest to make a report do its developer.

If you OS, PC can not handle x64 programs using CPU and memory at the same time, then do not generate all seasons all at the same time. You can temporarily halt a LODgen window execution by marking text in the command prompt window, then once a another LODGen finished, hint enter on that command prompt window.

Let the OS handle virtual memory settings.

As you can see by the folder name and the *.BTO suffix the file is an object LOD mesh. By the time the process reads them it already read the terrain LOD meshes.

Thanks a lot! I will try this and update you.

[BrotherShamus]

39 minutes ago, sheson said:

Since you report an issue with LODGen.exeLODGenx64.exe, see what happen if you use the version included in the latest xLODGen terrain LOD beta.

It would be better to actually provide information about the error so whatever the problem can be fixed.

It's the same issue I was having yesteday (I'm re-posting the links to the required logs https://ufile.io/f/do0q2 https://ufile.io/5lcjens0 ).  Where would I find the Beta?  The 'download' page directs me to the Alpha 77 file.

[sheson]

11 minutes ago, Thaumatarge said:

I will give that a try, but I have been struggling with this for hours and nothing so far has worked. I cannot provide logs if the program cannot either crash to give an error, or finish to give a finished log, because the computer just freezes.

Sounds like the hardware or OS is not properly setup.

[Thaumatarge]

9 minutes ago, sheson said:

Sounds like the hardware or OS is not properly setup.

I haven't had these issues in Alpha 74 and prior to that. I only recently updated to Alpha 77 when I noticed that the Resources updated.

[sheson]

19 minutes ago, BrotherShamus said:

It's the same issue I was having yesteday (I'm re-posting the links to the required logs https://ufile.io/f/do0q2 https://ufile.io/5lcjens0 ).  Where would I find the Beta?  The 'download' page directs me to the Alpha 77 file.

You refused to upload/post the event log entry. The log does not show the error.

The latest xLODGen terrain LOD beta can be found at
https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-90-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/

17 minutes ago, Thaumatarge said:

I haven't had these issues in Alpha 74 and prior to that. I only recently updated to Alpha 77 when I noticed that the Resources updated.

You reported the OS has issues with running 4 x64 programs at the same time. Let the OS handle virtual memory settings.

You doing grass LOD, ultra Tree LOD, full models for LOD + seasons at the same time? It seems it is just too much to compute at the time for the setup.

The LODGGensplit at same as virtual cores number is the best it can do at the moment in terms of reducing memory for performance sake.

[Thaumatarge]

14 minutes ago, sheson said:

You refused to upload/post the event log entry. The log does not show the error.

The latest xLODGen terrain LOD beta can be found at
https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-90-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/

You reported the OS has issues with running 4 x64 programs at the same time. Let the OS handle virtual memory settings.

You doing grass LOD, ultra Tree LOD + seasons at the same time? It seems it is just too much to compute at the time for the setup.

Oh no, not ultra tree lod and grass lod, I haven't got Grass LOD enabled as an option at all, and Ultra Tree LOD fails to generate lods for trees outside Riften so I haven't used it! But it seems the "select text to pause the LODGEN" method is working so far. I am only reporting this issue now because again, I have not experienced this issue in Alpha 74, and I had the same set up for generation.

[sheson]

12 minutes ago, Thaumatarge said:

Oh no, not ultra tree lod and grass lod, I haven't got Grass LOD enabled as an option at all, and Ultra Tree LOD fails to generate lods for trees outside Riften so I haven't used it! But it seems the "select text to pause the LODGEN" method is working so far. I am only reporting this issue now because again, I have not experienced this issue in Alpha 74, and I had the same set up for generation.

"Ultra Tree LOD fails to generate lods for trees outside Riften" what does that mean?
Ultra LOD = LOD for trees is done in object LOD. There are no trees outside Riften? Make sure billboards are generated by TexGen and/or 3D tree LOD models are installed. https://dyndolod.info/Help/Ultra-Tree-LOD
Check the ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt

[BrotherShamus]

21 minutes ago, sheson said:

You refused to upload/post the event log entry. The log does not show the error.

The latest xLODGen terrain LOD beta can be found at
https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-90-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse/

You reported the OS has issues with running 4 x64 programs at the same time. Let the OS handle virtual memory settings.

You doing grass LOD, ultra Tree LOD, full models for LOD + seasons at the same time? It seems it is just too much to compute at the time for the setup.

The LODGGensplit at same as virtual cores number is the best it can do at the moment in terms of reducing memory for performance sake.

Oh, you mean the Windows Event log entry?  I didn't think you would want to see that as it didn't seem to be related to Dyndolod.  I'll re-run it and post the log here then.

[Thaumatarge]

10 minutes ago, sheson said:

"Ultra Tree LOD fails to generate lods for trees outside Riften" what does that mean?
Ultra LOD = LOD for trees is done in object LOD. There are no trees outside Riften? Make sure billboards are generated by TexGen and/or 3D tree LOD models are installed. https://dyndolod.info/Help/Ultra-Tree-LOD
Check the ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt

I will try generating the Ultra Tree LODs and post a picture of what outside of riften looks like. it might be a Turn of the Seasons issue, because I did generate billboards using TexGen, and have DynDOLOD Resources installed. However, right now, I am glad the "pause the Tamriel seasons generation" method is working out, there is no problems so far! I still don't know why Alpha 74 had no issues, and Alpha 77 has these issues for me.

[BrotherShamus]

Here are the logs returned with the Windows Event Veiwer:

"Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code."

"Unable to open the job object \BaseNamedObjects\WmiProviderSubSystemHostJob for query access. The calling process may not have permission to open this job. The first four bytes (DWORD) of the Data section contains the status code."

"The Open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed with error code The device is not ready.. Performance data for this service will not be available."

These were all logged simultaneously which is why I was unsure which log to post.  Having Googled them and taken (to the best of my limited knowledge) all steps to mitigate the issue, there's no change.

edit: anyone else who has this issue... the solution can be found here.  At least it worked for me.  Crisis averted...

https://www.admin-enclave.com/en/articles/windows/306-resolved-the-open-procedure-for-service-bits-in-dll-c-windows-system32-bitsperf-dll-failed-performance-data-for-this-service-will-not-be-available-the-first-four-bytes-dword-of-the-data-section-contains-the-error-code.html

Edited March 7, 2022 by BrotherShamus