Jump to content

Recommended Posts

Posted
  On 2/2/2023 at 1:30 PM, Rozen said:

Run 1 got a crash again

Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dbb506
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000374
Fault offset: 0x000000000010c249
Faulting process id: 0x0xF4E0
Faulting application start time: 0x0x1D93709074E78FA
Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4322bd91-7999-4200-9a0c-8a1fbafd6b49
Faulting package full name: 
Faulting package-relative application ID: 

Want to put the real time logging back on?

Expand  

Yes.

Posted

I am still doing the run but i was thinking, would it be that your program is on a SSD and my Skyrim is on one of my HDD? maybe the program is trying to go faster than my HDD can go making it error, just asking sense it seems to work fine with no crash every time I turn on real time logging making it go slower.

Posted
  On 2/2/2023 at 3:11 PM, Rozen said:

I am still doing the run but i was thinking, would it be that your program is on a SSD and my Skyrim is on one of my HDD? maybe the program is trying to go faster than my HDD can go making it error, just asking sense it seems to work fine with no crash every time I turn on real time logging making it go slower.

Expand  

No. Read/Write functions do not care how long it takes. They either return an error or are successful when they are done.

Posted
  On 2/2/2023 at 3:15 PM, 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.

Expand  

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
  On 2/2/2023 at 8:06 AM, 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.

Expand  

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
  On 2/3/2023 at 1:06 AM, 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. 

Expand  

I thought the current problem was that it crashed?

Upload the log and debug log.

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.txtFetching info...

TexGen_SSE_log.txtFetching info...

 

 

image.thumb.jpeg.d7a9c8316eb4039651edb6b0354bc362.jpeg

 

Edited by Kattmandu
Posted
  On 2/3/2023 at 2:48 PM, 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

Expand  

Read the first post which DynDOLOD log and debug log to upload when making 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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

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