mostwanted11 Posted October 22 Posted October 22 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 Posted October 22 Author Posted October 22 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 Posted October 22 Posted October 22 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 Posted October 22 Author Posted October 22 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 Posted October 22 Posted October 22 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 Posted October 22 Author Posted October 22 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 Posted October 22 Posted October 22 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 Posted October 22 Posted October 22 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 Posted October 23 Author Posted October 23 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).
sheson Posted October 23 Author Posted October 23 8 hours ago, D1Z4STR said: 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. No logs or screenshots were provided for the new generation. That is not really a satisfactory solution or seems logical. Didn't you report that you see the animated dynamic LOD reference added by DynDOLOD plugins beyond the large reference distance in the LOD area once you if you disabled all LOD with tll? Why would the static LOD model that should be a bit lower and smaller than the animated dynamic LOD model cover it? If anything either only uncheck Dynamic and leave everything else as is, or just set LOD Level 4 to None and leave everything else as is.
m1sf1t711 Posted October 23 Posted October 23 CrashDump2.7z 1 hour ago, sheson said: 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). Thanks Just tried that but DynDOLOD wouldn't start and I got error code E0434352 I still have LODGENx64Win hidden. Should I have put that back? I have run the repair tool again for .NET Desktop Runtime 6 but a second attempt had the same result. I've attached the CrashDump files CrashDump2.7z
sheson Posted October 23 Author Posted October 23 35 minutes ago, m1sf1t711 said: CrashDump2.7z 1.78 MB · 1 download Thanks Just tried that but DynDOLOD wouldn't start and I got error code E0434352 I still have LODGENx64Win hidden. Should I have put that back? I have run the repair tool again for .NET Desktop Runtime 6 but a second attempt had the same result. I've attached the CrashDump files CrashDump2.7z 1.78 MB · 1 download Leave LODGenx64Win.exe hidden. We will continue with the Framework 4.8 version. If you like you can try updating/uninstalling/reinstalling/repairing the latest Framework version. On a windows command prompt you can try running C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force You can also try a sfc /scannow https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca Reboot after each. I doubt though that this is going to make a difference, since both Framework and .NET have the crash that is typically cause by CPU/memory issues. I have another test version. Replace the LODGenx64.exe with the one in this archive https://mega.nz/file/4RIzHSQZ#aTjH9RtZRcigS_RxmE3ZNbkglSvj6dIVmE1bhJRILPs Also put the same LODGenx64.pdb next to it. Delete old dmp files, and Execute LODGen in expert mode for a single worldspace and season so it only starts one processes. Upload dmp file(s).
m1sf1t711 Posted October 23 Posted October 23 15 minutes ago, sheson said: Leave LODGenx64Win.exe hidden. We will continue with the Framework 4.8 version. If you like you can try updating/uninstalling/reinstalling/repairing the latest Framework version. On a windows command prompt you can try running C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force You can also try a sfc /scannow https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca Reboot after each. I doubt though that this is going to make a difference, since both Framework and .NET have the crash that is typically cause by CPU/memory issues. I have another test version. Replace the LODGenx64.exe with the one in this archive https://mega.nz/file/4RIzHSQZ#aTjH9RtZRcigS_RxmE3ZNbkglSvj6dIVmE1bhJRILPs Also put the same LODGenx64.pdb next to it. Delete old dmp files, and Execute LODGen in expert mode for a single worldspace and season so it only starts one processes. Upload dmp file(s). Windows Defender is blocking the download saying a virus has been detected?
sheson Posted October 23 Author Posted October 23 55 minutes ago, m1sf1t711 said: Windows Defender is blocking the download saying a virus has been detected? https://dyndolod.info/FAQ#Virus https://www.virustotal.com/gui/file/2a9ec9170c35f28b765d5f87f834c81d7ac722076f384ff40f4f01ed41748745
m1sf1t711 Posted October 23 Posted October 23 1 hour ago, sheson said: https://dyndolod.info/FAQ#Virus https://www.virustotal.com/gui/file/2a9ec9170c35f28b765d5f87f834c81d7ac722076f384ff40f4f01ed41748745 Thank you! And sorry I should have checked and found that information myself. I knew it must be a false positive. I've rerun in Expert for just Tamriel Seasons using the new LODGenx64.exe and the LODGenx64.pdb and attached the crash logs CrashDump3.7z
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now