DynDOLOD 3.00 Alpha 182

[mostwanted11]

what does checking the large box between tree and ultra in advanced mode do? also the upgrade and downgrade boxes? are there any videos demonstrating the visual/performance difference?

[sheson]

6 hours ago, mostwanted11 said:

what does checking the large box between tree and ultra in advanced mode do? also the upgrade and downgrade boxes? are there any videos demonstrating the visual/performance difference?

https://dyndolod.info/Help/Advanced-Mode#Tree-Lod
Check Large to make the full model trees large references - if they are added by ESM flagged plugins. Requires DynDOLOD DLL NG and Scripts, which includes the large reference bugs workarounds. The TreeLargeRefSize setting in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini controls the size threshold, e.g. if smaller trees should be large references, lower the value. Also, references that are overwritten by non ESM flagged plugins, have enable parents or are initially disabled are skipped. In case the tree base records have locational swaps, like cells, locations or regions, they are skipped.

https://dyndolod.info/Help/Advanced-Mode#Upgrade-NearGrid-Large-References-to-FarGrid
Unchecked - large references that would have dynamic LOD in the NearGrid are ignored. They will not have LOD beyond the large reference distance setting. Better performance.
Checked - large references that would have dynamic LOD in the NearGrid are added to the FarGrid. They will have LOD beyond the large reference distance setting. Better visuals.
As a rule of thumb, check the box "Upgrade NearGrid Large Refs" in case the large reference system is not used - uLargeRefLODGridSize = uGridsToLoad (default 5) - to make sure all references receive dynamic LOD as intended. The result would be LOD working the same as it did in Skyrim. Vice versa, do not check this option in case the large referene system is used - uLargeRefLODGridSize > uGridsToLoad >= 5. Upgrading large references that were intended for NearGrid means more resource usage in case the large reference system is used. References that are intended for NearGrid are typically smaller and it generally makes not much sense to show them beyond the large reference grid.

https://dyndolod.info/Help/Advanced-Mode#Downgrade-FarGrid-References-to-NearGrid
Unchecked - non large references are added to the NearGrid or the FarGrid accordingly to their mesh rules. Better visuals.
Checked - non large references are always added to the NearGrid even if the of their mesh rules set FarGrid. Better performance.

If you want to know the visual and performance difference for your setup and load order generate 2 outputs and compare them.

Typically making trees large references will have the biggest performance impact depending on the amount of trees, their complexity and the large reference distance setting.

[mostwanted11]

17 minutes ago, sheson said:

https://dyndolod.info/Help/Advanced-Mode#Tree-Lod
Check Large to make the full model trees large references - if they are added by ESM flagged plugins. Requires DynDOLOD DLL NG and Scripts, which includes the large reference bugs workarounds. The TreeLargeRefSize setting in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini controls the size threshold, e.g. if smaller trees should be large references, lower the value. Also, references that are overwritten by non ESM flagged plugins, have enable parents or are initially disabled are skipped. In case the tree base records have locational swaps, like cells, locations or regions, they are skipped.

https://dyndolod.info/Help/Advanced-Mode#Upgrade-NearGrid-Large-References-to-FarGrid
Unchecked - large references that would have dynamic LOD in the NearGrid are ignored. They will not have LOD beyond the large reference distance setting. Better performance.
Checked - large references that would have dynamic LOD in the NearGrid are added to the FarGrid. They will have LOD beyond the large reference distance setting. Better visuals.
As a rule of thumb, check the box "Upgrade NearGrid Large Refs" in case the large reference system is not used - uLargeRefLODGridSize = uGridsToLoad (default 5) - to make sure all references receive dynamic LOD as intended. The result would be LOD working the same as it did in Skyrim. Vice versa, do not check this option in case the large referene system is used - uLargeRefLODGridSize > uGridsToLoad >= 5. Upgrading large references that were intended for NearGrid means more resource usage in case the large reference system is used. References that are intended for NearGrid are typically smaller and it generally makes not much sense to show them beyond the large reference grid.

https://dyndolod.info/Help/Advanced-Mode#Downgrade-FarGrid-References-to-NearGrid
Unchecked - non large references are added to the NearGrid or the FarGrid accordingly to their mesh rules. Better visuals.
Checked - non large references are always added to the NearGrid even if the of their mesh rules set FarGrid. Better performance.

If you want to know the visual and performance difference for your setup and load order generate 2 outputs and compare them.

Typically making trees large references will have the biggest performance impact depending on the amount of trees, their complexity and the large reference distance setting.

Great, i think a good way to prevent dumbasses like me spamming you with questions about stuff already explained is to put links on each feature in dyndolod if it does have a corresponding explanation in the site or a ? button next to the X button top right that opens up a link to the explanation of the feature if clicked with it on

Edited October 22 by mostwanted11

[sheson]

34 minutes ago, mostwanted11 said:

Great, i think a good way to prevent dumbasses like me spamming you with questions about stuff already explained is to put links on each feature in dyndolod if it does have a corresponding explanation in the site or a ? button next to the X button top right that opens up a link to the explanation of the feature if clicked with it on

That is what the hover hints are for.
The Help button is supposed to open https://dyndolod.info/Help/Advanced-Mode but nobody ever reports it not properly working, so nobody uses it anyways.

[mostwanted11]

Yup, as soon as I start using the latest version, a ctd on reload. The version I was using and got blocked from using was working perfectly fine, I don't need the latest version I just want to play the game man.

https://ufile.io/5pyxndnj

These are the logs because I still want to help you, but I will just revert to my old Output of the old version since this dyndolod DLL NG thing, its been nothing but CTDs on reload it's honestly very frustrating, I just changed 2 tree models and wanted to rerun it after months of playing with it with no issues at all, but I got cockblocked by the update prompt. So very frustrating, I wish you'd just tell me how to bypass it

[sheson]

5 hours ago, mostwanted11 said:

Yup, as soon as I start using the latest version, a ctd on reload. The version I was using and got blocked from using was working perfectly fine, I don't need the latest version I just want to play the game man.

https://ufile.io/5pyxndnj

These are the logs because I still want to help you, but I will just revert to my old Output of the old version since this dyndolod DLL NG thing, its been nothing but CTDs on reload it's honestly very frustrating, I just changed 2 tree models and wanted to rerun it after months of playing with it with no issues at all, but I got cockblocked by the update prompt. So very frustrating, I wish you'd just tell me how to bypass it

Unfortunately the DynDOLOD debug log does not show a generation session anymore since the tool was started again and then closed.

https://dyndolod.info/
The tools are shared for free with the specific requirement to use the latest version, to provide feedback and to report any problems including logs and other requested information to the official DynDOLOD support forum in order to advance their improve and advance their development for all users.

You are not entitled to my work or time. On the contrary, if you participate in the alpha test you are required to use the latest version and to help troubleshoot problems. If you have no intention to help troubleshoot the issue in your load order for everyones benefit, then you do not meet the requirements to particpate in the DynDOLOD 3 alpha test and should use it.

In case you actually want to help troubleshoot the problem for everyone's benefit, report if there is any difference using any of the older versions of DynDOLOD DLL NG and Scripts available at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds. Also test without any DynDOLOD DLL (while ignoring any error messages in game from DynDOLOD about it missing etc.)

Upload all crash logs collected while testing the 2 older versions.
Report the steps required to reproduce the CTD.

[mostwanted11]

2 hours ago, sheson said:

Unfortunately the DynDOLOD debug log does not show a generation session anymore since the tool was started again and then closed.

https://dyndolod.info/
The tools are shared for free with the specific requirement to use the latest version, to provide feedback and to report any problems including logs and other requested information to the official DynDOLOD support forum in order to advance their improve and advance their development for all users.

You are not entitled to my work or time. On the contrary, if you participate in the alpha test you are required to use the latest version and to help troubleshoot problems. If you have no intention to help troubleshoot the issue in your load order for everyones benefit, then you do not meet the requirements to particpate in the DynDOLOD 3 alpha test and should use it.

In case you actually want to help troubleshoot the problem for evryones benefit, report if there is any difference using any of the older versions of DynDOLOD DLL NG and Scripts available at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

Upload all crash logs collected while testing the 2 older versions.
Report the steps required to reproduce the CTD.

I never said I am entitled to anything, I already said I am willing to help to an extent as long as it doesn't come at the cost of my convenience (which is selfish brat behavior i know). BUT i have already reported it before that dll ng ctds my game on reload from time to time and I have already uploaded logs before on multiple occasions. Those past couple months I have NEVER Ctd'd on reload at least not when its a free of stress area and on a new level save and I mean NEVER. It is not a coincidence that it happened again like it used to back when I was using the ng dll thing in May (which was resolved when i reverted to dll SE) and I did report it and it probably got dismissed because its a difficult issue to track and hammer down, but it is widely known Dyndolod causes ctd on reload and a lot of modlist authors know it. My dyndolod generation says Dll: not Ng and "using papyrus scripts" when generating and i will continue to play with the version that does not CTD because it is common sense. I will test the ng version output from time to time when free and i will post crashlogs here but i am not sure if its going to be of much help because dyndolod dll is never mentioned in the logs but you're the one who knows his stuff in the end not me.

[sheson]

29 minutes ago, mostwanted11 said:

I never said I am entitled to anything, I already said I am willing to help to an extent as long as it doesn't come at the cost of my convenience (which is selfish brat behavior i know). BUT i have already reported it before that dll ng ctds my game on reload from time to time and I have already uploaded logs before on multiple occasions. Those past couple months I have NEVER Ctd'd on reload at least not when its a free of stress area and on a new level save and I mean NEVER. It is not a coincidence that it happened again like it used to back when I was using the ng dll thing in May (which was resolved when i reverted to dll SE) and I did report it and it probably got dismissed because its a difficult issue to track and hammer down, but it is widely known Dyndolod causes ctd on reload and a lot of modlist authors know it. My dyndolod generation says Dll: not Ng and "using papyrus scripts" when generating and i will continue to play with the version that does not CTD because it is common sense. I will test the ng version output from time to time when free and i will post crashlogs here but i am not sure if its going to be of much help because dyndolod dll is never mentioned in the logs but you're the one who knows his stuff in the end not me.

Common sense would be to first troubleshoot if this crash is actually caused by DynDOLOD and not by another mod or DLL.
Common sense of an alpha test is to troubleshoot the actual problem so it can be fixed.
There are zero similar crash reports here in months while the DynDOLOD DLL is being used by tens of thousands of people.

I suggested what to do test next, if a crash is rare, so what?

[m1sf1t711]

21 hours ago, sheson said:

By hiding I mean something like moving it out of the folder or renaming it to LODGenx64Win.bak for example.

Make sure antivir is not interfering by temporality disabling or adding exceptions.
Reinstall or repair .NET6

If neither works, upload the files mentioned from the last event log entry, e.g.
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b742fef1-151c-4b46-8353-6e3f9a08266a.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0820b4dd-3d78-4c5a-b818-0e6721cbf5f0.tmp.WERInternalMetadata.xml
etc.

Hi

Apologies for the slow retest but sleep and work rudely interrupted my modding endeavours lol

 

The attached zip includes a copy/paste of the error logs for my attempt this evening, having followed all the instructions above first. I've also attached the two Windows Report logs which I think was what you wanted. Let me know if I've misunderstood that part and you need anything else.

 

And again thank you so much for your help. Your generosity with your time is really appreciated.

 

Logs.7z

[sheson]

26 minutes ago, m1sf1t711 said:

Hi

Apologies for the slow retest but sleep and work rudely interrupted my modding endeavours lol

 

The attached zip includes a copy/paste of the error logs for my attempt this evening, having followed all the instructions above first. I've also attached the two Windows Report logs which I think was what you wanted. Let me know if I've misunderstood that part and you need anything else.

 

And again thank you so much for your help. Your generosity with your time is really appreciated.

 

Logs.7z 37.49 kB · 1 download

Can you check/upload whatever files you have in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_1e33ab8d-94fe-4a05-ba29-d611e7a20939
or here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_d2f3d1fc-8356-4a4a-9082-6fc9c1dd1b74

Especially files ending in *.dmp
Might be here: 
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f8f9708a-1428-4aa2-b32e-e61c619ff101.tmp.dmp
or here:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6d9ab25-2747-482b-8c01-2bd34348a1a1.tmp.dmp

Did you do change any settings about virtual memory/page file?

[m1sf1t711]

3 minutes ago, sheson said:

Can you check/upload whatever files you have in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_1e33ab8d-94fe-4a05-ba29-d611e7a20939
or here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_d2f3d1fc-8356-4a4a-9082-6fc9c1dd1b74

Especially files ending in *.dmp
Might be here: 
 C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f8f9708a-1428-4aa2-b32e-e61c619ff101.tmp.dmp
or here:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6d9ab25-2747-482b-8c01-2bd34348a1a1.tmp.dmp

Hi

 

In the first two locations I only have the .wer files which I sent.

I can't find the other files at all. In the Temp folder I only have the two files attached.

files.7z

[sheson]

1 hour ago, m1sf1t711 said:

Hi

 

In the first two locations I only have the .wer files which I sent.

I can't find the other files at all. In the Temp folder I only have the two files attached.

files.7z 207 B · 1 download

Did you do change any settings about virtual memory/page file?

Create a new registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps to enable minidumps.
https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

No need to add any of the settings, the defaults should suffice. Then reproduce the crash and hopefully find the file to upload in %LOCALAPPDATA%\CrashDumps

[m1sf1t711]

1 hour ago, sheson said:

Did you do change any settings about virtual memory/page file?

Create a new registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps to enable minidumps.
https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

No need to add any of the settings, the defaults should suffice. Then reproduce the crash and hopefully find the file to upload in %LOCALAPPDATA%\CrashDumps

 

Hi

 

"Did you do change any settings about virtual memory/page file?" - No I wouldn't know how to lol

So I think I set up the registry keys correctly (never done that before) and here's a link to the logs that I found in %LOCALAPPDATA%\CrashDumps after reproducing the crash.

https://drive.google.com/file/d/1v_Y69za19KwIXW73kyiVPURB3BXHGAYC/view?usp=sharing

[D1Z4STR]

On 10/15/2024 at 5:24 AM, sheson said:

What is the "exact" location?

You seem to be reporting that close up the waterfall is static and when moving away it becomes animated?

The waterfall 0001CCDA should have these states:
The full model fxwaterfallbodyslope.nif defined by the base record 000FC85F in the active 5x5 cells and the large reference area around them.
Beyond the large reference distance in the LOD area there should be an animated LOD model. It has a reference and base record in the DynDOLOD plugins and uses fxwaterfallbodyslope_AA06506B_dyndolod_lod.nif. It can be disabled/enabled via console. Typically the dynamic LOD model is active to the edge of the Far Grid.
Underneath the dynamic LOD model should be the static LOD model, which uses fxwaterfallbodyslope_AA06506Bpassthru_lod.nif for all static LOD levels. It can be toggled with all LOD with the tll command in console.

You should replace the files with the same filenames in their respective folders in the DynDOLOD Resources with the ones I uploaded.

The reference and base record that are shown in the screenshot with more informative console uses fxwaterfallbodyslope.nif for the full model.
There typically is no fxwaterfallbody.nif but there are also fxwaterfallbodytall.nif and fxwaterfallbodytall02.nif

Static LOD does not support animation and transparency, so using the full model for LOD is not going to have good visual results. That is why a dedicated dynamic LOD model and a dedicated static LOD model exist and should be used usually.

The reference 0001CCDA is a large reference.

The vanilla game shows the full model waterfalls to the edge of the large reference grid and then switches them to static LOD. That is why the dynamic LOD with the Near and Far Grid exists; to show the animated LOD further than the vanilla game does. If you see an animated waterfall for the reference 0001CCDA further than the large reference distance, then something that is not vanilla/default is causing that change.

Finally got around to regenerating with the 2 meshes as requested and it made no difference when checking in game. I am just going to make this easy and regenerate LOD again sometime and remove the dynamic flag from waterfalls and change LOD levels to 'None' minus LOD 32. That will look and work better for what I am looking for since dynamic LOD is not working.

[sheson]

8 hours ago, m1sf1t711 said:

Hi

"Did you do change any settings about virtual memory/page file?" - No I wouldn't know how to lol

So I think I set up the registry keys correctly (never done that before) and here's a link to the logs that I found in %LOCALAPPDATA%\CrashDumps after reproducing the crash.

https://drive.google.com/file/d/1v_Y69za19KwIXW73kyiVPURB3BXHGAYC/view?usp=sharing

So far so good. Delete all old dmp.
Replace LODGenx64.exe in Edit Scripts with this version https://mega.nz/file/wMhQkbYK#txe4unb3FlDtjlAaaIoVuOUohMoGqUNNA6oH4AABulY
Start DynDOLOD in expert mode and Execute LODGen for whatever worldspace and season with the problem.
Upload new dmp file(s).