Rozen Posted February 2, 2023 Posted February 2, 2023 15 minutes ago, sheson said: No. Read/Write functions do not care how long it takes. They either return an error or are successful when they are done. Okay that run got done with no crash, i will do one more but it takes almost 2 hrs each time with real time logging on.
Rozen Posted February 2, 2023 Posted February 2, 2023 just got done with the new run and no crash, i will test more tomorrow after I get my new video card installed.
LordIceWolf Posted February 2, 2023 Posted February 2, 2023 11 hours ago, sheson said: Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions. Go through every step of the No Grass LOD Check List and not only mention the outcome/result of a couple. I did but I will post a more detailed list with pertinent information as soon as I have time. Thanks
Rozen Posted February 3, 2023 Posted February 3, 2023 Here you go I did one more run for the night and made a video showing it with no ini change, it did not crash but got stuck.
sheson Posted February 3, 2023 Author Posted February 3, 2023 5 hours ago, Rozen said: Here you go I did one more run for the night and made a video showing it with no ini change, it did not crash but got stuck. I thought the current problem was that it crashed? Upload the log and debug log.
Rozen Posted February 3, 2023 Posted February 3, 2023 6 hours ago, sheson said: I thought the current problem was that it crashed? Upload the log and debug log. it is still crashing randomly but it also started getting stuck again like that and it might be related but don't know. Here are the logs from that run from the video> https://ufile.io/f/wa1hn
sheson Posted February 3, 2023 Author Posted February 3, 2023 2 hours ago, Rozen said: it is still crashing randomly but it also started getting stuck again like that and it might be related but don't know. Here are the logs from that run from the video> https://ufile.io/f/wa1hn Let me know what happens with this test version https://mega.nz/file/UdRFDRBD#jeSA6FBQyzoJKPmfvMHU_IrOF_wV34kXKsIocBdfguQ
Kattmandu Posted February 3, 2023 Posted February 3, 2023 (edited) Not quite sure where to post this. Please point me to the correct thread if this is not it. After starting a new game using "I own property in one of the holds" in AS-LAL, I noticed a horse stable (just outside of the Hearthfire home I was spawned into) was flickering and blurry. The vertical posts on the horse stable become blurry and flicker as soon as the "DynDOLOD successfully initialized" message pops up on the screen after exiting the Hearthfire home for the first time. Before the DynDOLOD message appears, they look fine. LOOT shows no files requiring cleaning. And uGridsToLoad is 5 and uLargeRefLODGridSize is 11. So I re-ran DynDOLD setup and started another new game. Same thing happened. DynDOLOD.log DynDOLOD_SSE_log.txt TexGen_SSE_log.txt Edited February 3, 2023 by Kattmandu
sheson Posted February 3, 2023 Author Posted February 3, 2023 9 minutes ago, Kattmandu said: Not quite sure where to post this. Please point me to the correct thread if this is not it. After starting a new game using "I own property in one of the holds" in AS-LAL, I noticed a horse stable (just outside of the Hearthfire home I was spawned into) was flickering and blurry. The vertical posts on the horse stable become blurry and flicker as soon as the "DynDOLOD successfully initialized" message pops up on the screen after exiting the Hearthfire home for the first time. Before the DynDOLOD message appears, they look fine. LOOT shows no files requiring cleaning. And uGridsToLoad is 5 and uLargeRefLODGridSize is 11. So I re-ran DynDOLD setup and started another new game. Same thing happened. Read the first post which DynDOLOD log and debug log to upload when making posts.
Rozen Posted February 3, 2023 Posted February 3, 2023 1 hour ago, sheson said: Let me know what happens with this test version https://mega.nz/file/UdRFDRBD#jeSA6FBQyzoJKPmfvMHU_IrOF_wV34kXKsIocBdfguQ No getting stuck or locking up on run 1, here is the logs> https://ufile.io/f/xdm39 Also just letting you know, i do not have my new video card in yet, so still on the same one.
Kattmandu Posted February 3, 2023 Posted February 3, 2023 1 hour ago, sheson said: Read the first post which DynDOLOD log and debug log to upload when making posts. I think I've got the correct log files added to my post now. Sorry, new to all this.
sheson Posted February 3, 2023 Author Posted February 3, 2023 1 hour ago, Kattmandu said: I think I've got the correct log files added to my post now. Sorry, new to all this. Read the first post which DynDOLOD debug log to also upload when making posts. However, judging by the DynDOLOD log, you started DynDOLOD and quit it again with generating LOD, which will have replaced the debug from the generation in question, which is unfortunate. Install the latest version of DynDOLOD NG and scripts from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds If problem persists, also enable and check/upload papyrus log and all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\
sheson Posted February 3, 2023 Author Posted February 3, 2023 1 hour ago, Rozen said: No getting stuck or locking up on run 1, here is the logs> https://ufile.io/f/xdm39 Also just letting you know, i do not have my new video card in yet, so still on the same one. Random success or not is the question...
Kattmandu Posted February 3, 2023 Posted February 3, 2023 (edited) 39 minutes ago, sheson said: Read the first post which DynDOLOD debug log to also upload when making posts. However, judging by the DynDOLOD log, you started DynDOLOD and quit it again with generating LOD, which will have replaced the debug from the generation in question, which is unfortunate. Install the latest version of DynDOLOD NG and scripts from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds If problem persists, also enable and check/upload papyrus log and all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\ Ah, so that's why I couldn't find the debug log. I did run the DynDOLOD program to confirm the following line was appearing... Large reference bugs workarounds: enabled (DynDOLOD.DLL: NG, Scripts: NG, Deleted references: no) I'll regenerate my DynDOLOD with the setting below (as per the Step guide) and post the debug log. Edited February 3, 2023 by Kattmandu
Rozen Posted February 3, 2023 Posted February 3, 2023 21 minutes ago, sheson said: Random success or not is the question... I will run again sense i am still waiting on my video card.
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