Jump to content

Recommended Posts

Posted
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.

Posted
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

Posted

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. 

 

Posted
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.

Posted
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

 

Posted (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-LALI 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

 

 

image.thumb.jpeg.d7a9c8316eb4039651edb6b0354bc362.jpeg

 

Edited by Kattmandu
Posted
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-LALI 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.

image.thumb.jpeg.0f2bccd2551ab8d8c438ccc1650c2c4f.jpeg

Read the first post which DynDOLOD log and debug log to upload when making posts.

Posted
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.

Posted
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\

Posted (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.

image.thumb.jpeg.0032f899b2e499c1571d7113f3d7e4e4.jpeg

Edited by Kattmandu
Posted
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.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.