aljoxo Posted August 22 Share Posted August 22 Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process. I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it. Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing DynDOLOD_SSE_log.txt DynDOLOD_SSE_log.txt Link to comment Share on other sites More sharing options...
sheson Posted August 22 Author Share Posted August 22 1 hour ago, aljoxo said: Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process. I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it. Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing DynDOLOD_SSE_log.txt 1.44 MB · 1 download DynDOLOD_SSE_log.txt 735.37 kB · 1 download Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds Upload new DynDOLOD log and debug log if issue persists. Link to comment Share on other sites More sharing options...
aljoxo Posted August 22 Share Posted August 22 (edited) 6 hours ago, sheson said: Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds Upload new DynDOLOD log and debug log if issue persists. Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well). Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing DynDOLOD_SSE_log.txt Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173. Edit 2: alpha 173 blue screened my PC Edit 3: successfully generated LODs on alpha 177 Edited August 23 by aljoxo added information regarding running a test on alpha173 and alpha177 Link to comment Share on other sites More sharing options...
Gamma_Metroid Posted August 23 Share Posted August 23 I am having some trouble getting the material names config file to work in the latest version. The check for lod models containing the "sw-moss" string only seems to be happening when the full model doesn't have a corresponding lod model supplied by vanilla skyrim or DynDOLOD. I tried reverting to the test version that worked before but had the same problem, which would seem to indicate that it's something on my end, but I can't figure out what is wrong. Here are my logs: https://ufile.io/ydz5b5n7 For example, 05101261 has the material shader applied but is not being checked for the "sw-moss" variant lod model. Link to comment Share on other sites More sharing options...
z929669 Posted August 23 Share Posted August 23 Warning: File not found textures\effects\fxwhitewater02_falls_n.dds. Used by meshes\lod\waterfalls\fxwaterfallbodytall02passthru_lod.nif Skyrim.esm FXWaterfallBodyTall02_static [STAT:001091F0] This happened with Alpha 177 and now 178. DynDOLOD Resources alpha-51 seems to provide this model, so I assume the normal is missing from DynDOLOD Resources or the TexGen output, since it's not provided by the game as far as I can see. Logs Link to comment Share on other sites More sharing options...
sheson Posted August 23 Author Share Posted August 23 9 hours ago, aljoxo said: Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well). Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing DynDOLOD_SSE_log.txt 735.56 kB · 1 download Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173. Edit 2: alpha 173 blue screened my PC Edit 3: successfully generated LODs on alpha 177 The logs show that it is stuck on something it does after exporting terrain height. I am really just interested in problems with the latest alpha and the requested tests and their results, so there is no need to run older versions. https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death BSOD are a hardware, BIOS setting, OS or driver problem. For example, problems with overclocking, memory timings, cooling, unstable power supply etc. Searching the Internet for the BSOD code should help troubleshooting. Delete old logs, run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c and upload new log and debug log if issues persists. Link to comment Share on other sites More sharing options...
sheson Posted August 23 Author Share Posted August 23 5 hours ago, Gamma_Metroid said: I am having some trouble getting the material names config file to work in the latest version. The check for lod models containing the "sw-moss" string only seems to be happening when the full model doesn't have a corresponding lod model supplied by vanilla skyrim or DynDOLOD. I tried reverting to the test version that worked before but had the same problem, which would seem to indicate that it's something on my end, but I can't figure out what is wrong. Here are my logs: https://ufile.io/ydz5b5n7 For example, 05101261 has the material shader applied but is not being checked for the "sw-moss" variant lod model. Run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c If there is still a problem, upload new logs and a screenshot of that STAT base record in xEdit. Link to comment Share on other sites More sharing options...
sheson Posted August 23 Author Share Posted August 23 3 hours ago, z929669 said: Warning: File not found textures\effects\fxwhitewater02_falls_n.dds. Used by meshes\lod\waterfalls\fxwaterfallbodytall02passthru_lod.nif Skyrim.esm FXWaterfallBodyTall02_static [STAT:001091F0] This happened with Alpha 177 and now 178. DynDOLOD Resources alpha-51 seems to provide this model, so I assume the normal is missing from DynDOLOD Resources or the TexGen output, since it's not provided by the game as far as I can see. Logs Verify your assumptions by checking the NIF yourself. This is a result of automatic texture replacements based on changed full models. You are using a waterfall mod (probably Realistic Water Two 5.7.1) that was recently updated for which updated LOD assets have not been created/released yet. Next DynDOLOD Resources SE should contain the updated LOD assets. See https://dyndolod.info/Mods/Waterfalls 1 1 Link to comment Share on other sites More sharing options...
Gamma_Metroid Posted August 23 Share Posted August 23 37 minutes ago, sheson said: Run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c If there is still a problem, upload new logs and a screenshot of that STAT base record in xEdit. Turns out the problem was I had an ITM override on one of the MATO forms defined in the materials config file, which was preventing it from being picked up. Link to comment Share on other sites More sharing options...
nt5raham Posted August 24 Share Posted August 24 Hi, not sure what happened but I posted a question here several hours ago and now it has disappeared. I've been using DynDOLOD for years, including the MCM menu, but this time it has me stumped. The question was, if the MCM is missing, how can I tell for certain that DynDOLOD is running in the game? I don't know much about Papyrus and scripts. Thanks! Link to comment Share on other sites More sharing options...
sheson Posted August 24 Author Share Posted August 24 2 hours ago, nt5raham said: Hi, not sure what happened but I posted a question here several hours ago and now it has disappeared. I've been using DynDOLOD for years, including the MCM menu, but this time it has me stumped. The question was, if the MCM is missing, how can I tell for certain that DynDOLOD is running in the game? I don't know much about Papyrus and scripts. Thanks! It was moved to the appropriate thread. Check your post history. Link to comment Share on other sites More sharing options...
Greg Posted August 24 Share Posted August 24 2 hours ago, nt5raham said: Hi, not sure what happened but I posted a question here several hours ago and now it has disappeared. I've been using DynDOLOD for years, including the MCM menu, but this time it has me stumped. The question was, if the MCM is missing, how can I tell for certain that DynDOLOD is running in the game? I don't know much about Papyrus and scripts. Thanks! I think this is the post you are looking for? Link to comment Share on other sites More sharing options...
aljoxo Posted August 24 Share Posted August 24 On 8/23/2024 at 1:27 AM, sheson said: The logs show that it is stuck on something it does after exporting terrain height. I am really just interested in problems with the latest alpha and the requested tests and their results, so there is no need to run older versions. https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death BSOD are a hardware, BIOS setting, OS or driver problem. For example, problems with overclocking, memory timings, cooling, unstable power supply etc. Searching the Internet for the BSOD code should help troubleshooting. Delete old logs, run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c and upload new log and debug log if issues persists. Hey sheson, was busy yesterday so I was unable to test. I only included the edits regarding the older versions of DynDOLOD because I had them to test and figured that there was no harm in sharing the information. The BSOD was likely unrelated to DynDOLOD anyways, I was just documenting it. For the record the mega file's exe was named DynDOLOD.64.exe instead of DynDOLOD64.exe This new test version of Alpha179 log: attached debug log: https://drive.google.com/file/d/1m_jy_eiBPvGc9IdVvL28XKbIFzxEpatw/view?usp=sharing DynDOLOD_SSE_log.txt Link to comment Share on other sites More sharing options...
sheson Posted August 25 Author Share Posted August 25 9 hours ago, aljoxo said: Hey sheson, was busy yesterday so I was unable to test. I only included the edits regarding the older versions of DynDOLOD because I had them to test and figured that there was no harm in sharing the information. The BSOD was likely unrelated to DynDOLOD anyways, I was just documenting it. For the record the mega file's exe was named DynDOLOD.64.exe instead of DynDOLOD64.exe This new test version of Alpha179 log: attached debug log: https://drive.google.com/file/d/1m_jy_eiBPvGc9IdVvL28XKbIFzxEpatw/view?usp=sharing DynDOLOD_SSE_log.txt 735.97 kB · 1 download Thanks. Delete old logs, then run this test version https://mega.nz/file/VVISVLwZ#BUNV8tCRdhURTDrThZWpePgGxACYOHivoCkBV8SYC9k Upload new logs if the issue persists. Link to comment Share on other sites More sharing options...
aljoxo Posted August 25 Share Posted August 25 11 hours ago, sheson said: Thanks. Delete old logs, then run this test version https://mega.nz/file/VVISVLwZ#BUNV8tCRdhURTDrThZWpePgGxACYOHivoCkBV8SYC9k Upload new logs if the issue persists. I was able to successfully generate LOD on this version. Thank you sheson. here are the logs and debug logs in case they are of any use. Debug Log DynDOLOD_SSE_log.txt Link to comment Share on other sites More sharing options...
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