DynDOLOD 3.00 Alpha 182

[DankTemplar]

46 minutes ago, sheson said:

I am simply stating a fact. if the OS freezes or has BSOD because it told a program it can not have any more memory, then there is a problem with the OS or the system.

DynDOLOD wanting to use as much memory and CPU as possible to speed up things is how it is programmed. Grass LOD creates huge BTO files. Reading many large BTO files at the same time requires lots of memory. Nothing unusual about it. The INI setting to limit number of threads exists for this very reason.

Read the first post which entire log of the session of interest, entire debug log and bugreport.txt (if it exists) to upload when making posts.

Typically operations are aborted when user clicks X top right of window to close the program.

No BSOD, just an unresponsive Dyndolod and OS until Dyndolod errors out then sometimes I can spam X to close the program, other times I have to end task it. After my computer is fine again.

Why on earth would it be Windows problem if a program misbehaves by trying to grab more resources than the OS can grant? Windows is the baseline. Everything has to work with or around it. If a program has a strange reaction to an instruction set from Windows wouldn't that be on the misbehaving program? Bar a janky Windows update or something which I imagine you'd be aware of since I wouldn't be the only one reporting the problem if that was the case.

Tried running lodxgen. I ended up with a new error.

Quote

 

[Window Title]
TexGen

[Main Instruction]
Texconv error 8007000E.

[Content]
textures\architecture\windhelm\WHroughground.dds

"C:\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -f R8G8B8A8_UNORM -o "C:\Users\XXXX\AppData\Local\Temp\TexGen_SSE" "C:\Users\XXXX\AppData\Local\Temp\TexGen_SSE\51EE864F427C45AEA309E59754C50868.dds"

Click on this link for additional explanations and help for this message

[Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

It seems it's a memory-related error.

I think I'm going to give up on making Northern Grass + NGiO + Dyndolod working together and try a different grass mod with a new cache file. I feel like I've run into this issue in the past before, this situation is giving me a huge sense of dejavu and I think I solved the issue last time by not using Northern Grass.

I'll provide the log files once the setup is complete and a report on if that fixes it (I think it might) It'll likely be 2 or 3 hours.

Thanks for the help.

 

Edited March 11, 2022 by DankTemplar

[sheson]

On 3/11/2022 at 11:17 PM, DankTemplar said:

No BSOD, just an unresponsive Dyndolod and OS until Dyndolod errors out then sometimes I can spam X to close the program, other times I have to end task it. After my computer is fine again.

Why on earth would it be Windows problem if a program misbehaves by trying to grab more resources than the OS can grant? Windows is the baseline. Everything has to work with or around it. If a program has a strange reaction to an instruction set from Windows wouldn't that be on the misbehaving program? Bar a janky Windows update or something which I imagine you'd be aware of since I wouldn't be the only one reporting the problem if that was the case.

Tried running lodxgen. I ended up with a new error.

It seems it's a memory-related error.

I think I'm going to give up on making Northern Grass + NGiO + Dyndolod working together and try a different grass mod with a new cache file. I feel like I've run into this issue in the past before, this situation is giving me a huge sense of dejavu and I think I solved the issue last time by not using Northern Grass.

I'll provide the log files once the setup is complete and a report on if that fixes it (I think it might) It'll likely be 2 or 3 hours.

Thanks for the help.

 

 The OS is what controls resources. A simple program requests a resource from the OS, it may grant or deny it. Then the simple program deals with it. In this case DynDOLOD prints a error message and stops. If the OS freezes while doing its job, it has some kind of problem or is not a very well programmed OS.

Texconv also ran out of memory. Same thing: a simple program requests memory from the OS. OS says no. Program chooses to stop with error message.

Without logs I can not really make further suggestions that could help to reduce memory usage of the tools.

It is possible there are huge grass cache files or some other problem with one causing LODGen to consume a lot of memory. Maybe its log provides clues (setting Verbose=1 for more info could help). Setting LODGenThreadSplit= to same number as virtual cores might help.

[xcal68]

Speaking of logs heh...

 

Was 79 released twice?  Wondering the difference between the two, as I currently am creating LODs with the first one.

[sheson]

11 minutes ago, xcal68 said:

Speaking of logs heh...

Was 79 released twice?  Wondering the difference between the two, as I currently am creating LODs with the first one.

Replaced references in the DynDOLOD INI to the old html docs with URLs.

[xcal68]

Ah cool, thanks.  So nothing for me to be concerned with, which I'm guessing is why no log haha...I'm probably 1 of only a couple who noticed. 

[Roastlawyer]

3 hours ago, sheson said:

Run this test version, see if it works any better. Check for bugreport.txt in case it doesn't and upload with debug log.

I'm still getting access violation issues, but using that test version I got a bugreport.txt

Spoiler

 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000001252F45 in module 'DynDOLODx64.exe'.

[Content]
Read of address 0000000000000000.

Click on this link for additional explanations and help for this message

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

 

Debug Log: https://drive.google.com/drive/folders/1jTDOvaYZLJpcSiQje3GURhqyvCdqd2cM?usp=sharing

bugreport.txt DynDOLOD_SSE_log.txt

[gamingsrc]

Is it normal the log give these errors?

Error: File not found textures\clutter\common\ruground02_n.dds

I installed both RUGNAROK and RaiserFX Detailed Rugs and none has this normal texture. I think the system don't use it in the nif files but rather another normal texture.

 

Also DynDOLOD suggest to clean Skyrim Masters.

File Updates.esm come from Bethesda and is a low-level game system file and claiming to clean it with a tool like xEdit has no academic documentation.

[labdoge]

Got the OpenGL: Source framebuffer incomplete attachment error when running dyndolod on generating Tamriel LODs. The log is as attachment. Please help.

PS. the debug log is too big so I link it from my cloud storage: 
https://drive.google.com/file/d/1Je3xYdCnS-GZ-GmtyRYMXNMx0-zEJdGk/view?usp=sharing

DynDOLOD_SSE_log.txt

[DankTemplar]

16 hours ago, sheson said:

 The OS is what controls resources. A simple program requests a resource from the OS, it may grant or deny it. Then the simple program deals with it. In this case DynDOLOD prints a error message and stops. If the OS freezes while doing its job, it has some kind of problem or is not a very well programmed OS.

8007000E Texconv ran out of memory. Same thing: a simple program requests memory from the OS. OS says no. Program chooses to stop with error message.

Without logs I can not really make further suggestions that could help to reduce memory usage of the tools.

It is possible there are huge grass cache files or some other problem with one causing LODGen to consume a lot of memory. Maybe its log provides clues (setting Verbose=1 for more info could help). Setting LODGenThreadSplit= to same number as virtual cores might help.

Ahhh, I see. This is why I'm not into computer sciences lol. I know just enough to be misinformed.

I'm still running into the issue but I've a theory...I'm doing this on an M.2 drive...it's nowhere near as good as ram but for generation purposes, what if I change my page file size to something silly? Fake it until you make it? lol. It's worth the experiment at least!

 

EDIT: Northern Grass just isn't working with Dyndolod 3.0 for me, with NGiO gass cache, tried other grass mods and they did. I may try an experiment later today because I had enabled Occlusion while generating Dyndolod for Open Cities in step 1 which is a variable I haven't accounted for. 

Editing the pagefile didn't help. Changing LODGenThreadSplit= didn't help either in this instance.

Edited March 12, 2022 by DankTemplar

[wWeo]

Hey Sheson,

Always when running the DynDOLOD64.exe tool, I always get the "Item Not Found" error with no discernable cause. Just wondering what I need to do to fix this error. 

bugreport.txt: https://paste.ee/p/4Z8lU

DynDOLOD_SSE_Debug_log.txt: https://paste.ee/p/2VVTk

DynDOLOD_SSE_log.txt: https://paste.ee/p/QjZjx

[z929669]

Alpha 79 ... It's so fast on my system, I'm suspicious and requesting a quick review of my logs.

16.5 minutes with hi quality occlusion, underside, grass and all (see screen). Down from about 25-40 minutes in alpha 64-ish. TexGen took 1.5 minutes (down from about 15 minutes). xLODGen beta 90 took 8.5 minutes (down from about 14 minutes ... in beta 83?).

It looks legit, and if so, there must be some key programmatic and/or mesh-rule optimizations in this alpha. Stupendous.

https://mega.nz/file/iZNUiDJL#l5vU2bRrGpebGrClYEgCBtwVW6Ow6GlTrucMZDlWnSw

EDIT: I ran subsequently with occlusion quality 1 and all else remaining same, and it only took 11.5 minutes.

EDIT2: Well, something's up, because the output generated with this run doesn't behave as expected. Started a new game, and no DynDOLOD successfully initialized message after loading exterior cell. MCM is active, and DynDOLOD active toggle wasn't checked (that's a first), so I went back into Breezehome and checked it. Went back outdoors and still no loaded message and no LOD. I disabled my alpha 79 output and reenabled my alpha 78 output, loaded up as described, and all worked as expected, so it's an issue with the alpha 79 output.

EDIT3: This may have been related to an improperly sorted LO. The new LOOT version wasn't translating the sorted LO to MO all of the sudden (and no 'apply' button in LOOT). So I may have generated with a bad LO. I seemed to have fixed it by forcing LOOT to run as admin for all users. This forced me to have to launch MO with admin (which I don't like to do for various reasons). Then I sorted and got the 'apply' button again finally and it translated to MO. I then deactivated admin on LOOT.exe and ran MO normally, and everything is normal again. I am generating all LOD again from scratch. When I loaded up xLODGen after all of this tinkering, I got a launch error relating to the Steam launcher needing to be run (as in after a Steam update). Did that and running xLODGen and the works after that. Will report back when finished.

EDIT4: well, that wasn't the problem. Alpha 79 isn't generating useable LOD for me. Same behavior as described above. Plugins and data seem fine, but I can provide whatever else is needed. Updated logs follow, but i suspect they are same as previous.

https://mega.nz/file/3cVXXIya#S1Kjkr4jU0C1FZ6Q9IqnvDjSegp-iHLrtwH4zmRrAWA

EDIT5: I reenabled my Alpha 78 folder and ran with the exact same preset. All good. You may be able to compare the logs from this one against the last to possibly find the difference. Nothing changed between these runs besides the alpha version

https://mega.nz/file/GMUB2ApR#GKUl124zzScOGfCkdC8t8ZBGJL7xflvDNxZkfd181fU

[nolbear]

On 3/10/2022 at 3:21 PM, sheson said:

What happened when you follow the second instructions for the error code "See https://www.admin-enclave.com/en/articles/windows/306" and follow what the website says?
That is what solved the problem for 2 people in the past couple days - as you must know after doing the search. 

Screenshots can not be searched.

If error persist after following the suggestion from  the website https://www.admin-enclave.com/en/articles/windows/306 linked from the help page https://dyndolod.info/Help/LODGen for the error code E0434352, execute the command from the error message:

"C:\DynDOLOD\DynDOLOD\Edit Scripts\LODGenx64.exe" --inputfile "C:\DynDOLOD\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Test.txt" --logfile "C:\DynDOLOD\DynDOLOD\Logs\LODGen_SSE_Test_log.txt"

from a command prompt window to see if it shows more information. Copy and paste the text from the command prompt window in that case.

If it fails because the LODGen_SSE_Test.txt is missing let me know.

Hi Sheson, do you happen to have any advice for someone who has tried the above fix and is still getting the performance counters error during DynDOLOD startup? I've tried solution 01 from the page you linked 3 times now and I'm still getting the error. I don't understand solution 02 so I haven't been able to do that. I see the ini file they're referring to but I don't understand what I'm supposed to do with it. Any help would be much appreciated. I'm currently stuck on Alpha 75 while I try to sort this out.

[sheson]

10 hours ago, gamingsrc said:

Is it normal the log give these errors?

Error: File not found textures\clutter\common\ruground02_n.dds

I installed both RUGNAROK and RaiserFX Detailed Rugs and none has this normal texture. I think the system don't use it in the nif files but rather another normal texture.

 

Also DynDOLOD suggest to clean Skyrim Masters.

File Updates.esm come from Bethesda and is a low-level game system file and claiming to clean it with a tool like xEdit has no academic documentation.

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

Read the explanations for the message https://dyndolod.info/Messages/File-Not-Found-Textures
The message should list the NIF that uses the texture and the record that use the NIF.

https://dyndolod.info/Messages/Deleted-Reference
There can be plugins in the load order that where made before the current version of Updates.esm. The foundation of a load order should be as stable and error free  as possible. I suggest to read the xEdit documentation and/or use its Discord for questions regarding the use of xEdit.
Undeleting records in dirty plugins is established modding practice to avoid CTD caused by them. DynDOLOD simply reports the problem, similar to LOOT. Clean every plugin that LOOT reports. Clean dirty plugins that have deleted records. It will be one of the first troubleshooting steps in case of CTD or other problems in the load order anyways. Reporting such issues in mods/plugins is to help users to better understand, identify and fix problems in their load orders instead of assuming issues happen because of the last tool they used or mod they added

[sheson]

1 hour ago, nolbear said:

Hi Sheson, do you happen to have any advice for someone who has tried the above fix and is still getting the performance counters error during DynDOLOD startup? I've tried solution 01 from the page you linked 3 times now and I'm still getting the error. I don't understand solution 02 so I haven't been able to do that. I see the ini file they're referring to but I don't understand what I'm supposed to do with it. Any help would be much appreciated. I'm currently stuck on Alpha 75 while I try to sort this out.

Check/Upload the LODGen_SSE_Test_log.txt file and check the event log.

[sheson]

10 hours ago, labdoge said:

Got the OpenGL: Source framebuffer incomplete attachment error when running dyndolod on generating Tamriel LODs. The log is as attachment. Please help.

PS. the debug log is too big so I link it from my cloud storage: 
https://drive.google.com/file/d/1Je3xYdCnS-GZ-GmtyRYMXNMx0-zEJdGk/view?usp=sharing

DynDOLOD_SSE_log.txt 1005.21 kB · 2 downloads

This might be fixed next version. If not upload new log, debug log and bugreport.txt if it exists.

5 hours ago, wWeo said:

Hey Sheson,

Always when running the DynDOLOD64.exe tool, I always get the "Item Not Found" error with no discernable cause. Just wondering what I need to do to fix this error. 

bugreport.txt: https://paste.ee/p/4Z8lU

DynDOLOD_SSE_Debug_log.txt: https://paste.ee/p/2VVTk

DynDOLOD_SSE_log.txt: https://paste.ee/p/QjZjx

This should be fixed in the next version. If not upload new log, debug log and bugreport.txt if it exists.

10 hours ago, Roastlawyer said:

I'm still getting access violation issues, but using that test version I got a bugreport.txt

  Reveal hidden contents

 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000001252F45 in module 'DynDOLODx64.exe'.

[Content]
Read of address 0000000000000000.

Click on this link for additional explanations and help for this message

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

 

Debug Log: https://drive.google.com/drive/folders/1jTDOvaYZLJpcSiQje3GURhqyvCdqd2cM?usp=sharing

bugreport.txt 38.61 kB · 1 download DynDOLOD_SSE_log.txt 34.81 kB · 0 downloads

Test with the next version. Should be fixed. If it still happens upload all new logs and bugreport.txt.