Gamma_Metroid Posted August 23 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.
nt5raham Posted August 24 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!
sheson Posted August 24 Author 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.
Greg Posted August 24 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?
aljoxo Posted August 24 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
sheson Posted August 25 Author 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.
aljoxo Posted August 25 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
Rodocastiza Posted August 25 Posted August 25 Hello, I have the same problem, Dyndolod is stuck at "exporting terrain height data". Eventually, it moves on, but it takes more than 30 min to advance in each worldspace. This time has taken 8.15h. I'm running the last version, resources, DLL NG, I can run xLodGen for the terrain without problems, also TexGen. Both generate output. I've tried the test version you posted before Sheson, but with the same results. I haven't tried the new test yet. Will do now. Here is my log. DynDOLOD_SSE_log
sheson Posted August 25 Author Posted August 25 52 minutes ago, aljoxo said: 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 1.83 MB · 1 download That's great! Thanks for letting us know.
sheson Posted August 25 Author Posted August 25 18 minutes ago, Rodocastiza said: Hello, I have the same problem, Dyndolod is stuck at "exporting terrain height data". Eventually, it moves on, but it takes more than 30 min to advance in each worldspace. This time has taken 8.15h. I'm running the last version, resources, DLL NG, I can run xLodGen for the terrain without problems, also TexGen. Both generate output. I've tried the test version you posted before Sheson, but with the same results. I haven't tried the new test yet. Will do now. Here is my log. DynDOLOD_SSE_log Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD debug log to also upload when making posts. Do not wait 8 hours... when there is obviously a problem. https://dyndolod.info/Official-DynDOLOD-Support-Forum If it takes time to first gather information, logs etc. it is fine to just take it and then post when ready.
Rodocastiza Posted August 25 Posted August 25 I thought pausing it alone wouldn't generate a log, ouch, and I forgot the debug one. The last test version seems to be fully working, thank you!
sheson Posted August 25 Author Posted August 25 11 minutes ago, Rodocastiza said: I thought pausing it alone wouldn't generate a log, ouch, and I forgot the debug one. The last test version seems to be fully working, thank you! That's great! Thanks for letting us know.
Kattmandu Posted August 25 Posted August 25 (edited) Hmm, I re-ran TexGen and it's saying "Error: Cannot create file "F:\Games\Steam\steamapps\common\Skyrim Special Edition\DynDOLOD\DynDOLOD_SSE_TexGen_noalpha_updateesm_pbr.txt". The system cannot find the path specified." Rebooted my computer and tried it a second time to see if it would happen again. it did. Running TexGen within MO2. bugreport.txt TexGen_SSE_log.txt TexGen_SSE_Debug_log.txt Edited August 25 by Kattmandu
sheson Posted August 25 Author Posted August 25 9 minutes ago, Kattmandu said: Hmm, I re-ran TexGen and it's saying "Error: Cannot create file "F:\Games\Steam\steamapps\common\Skyrim Special Edition\DynDOLOD\DynDOLOD_SSE_TexGen_noalpha_updateesm_pbr.txt". The system cannot find the path specified." Rebooted my computer and tried it a second time to see if it would happen again. it did. Running TexGen within MO2. bugreport.txt 239.82 kB · 0 downloads TexGen_SSE_log.txt 50.27 kB · 0 downloads Will be fixed next Alpha version I am going to release shortly. 1
Kattmandu Posted August 25 Posted August 25 28 minutes ago, sheson said: Will be fixed next Alpha version I am going to release shortly. Version 180 is working without error. Thanks!
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