DynDOLOD 3.00 Alpha 182

[Rozen]

I am still testing with the setting in the ini but it has not crashed yet so still doing runs when I can it just takes a long time with the real time log on.

It like your program is got a mind of its own lol.

Also, tomorrow I am getting a new video card in, going from a RX 580 to a RX 6650 XT sense i have had this 580 for years now.

[sheson]

41 minutes ago, Rozen said:

I am still testing with the setting in the ini but it has not crashed yet so still doing runs when I can it just takes a long time with the real time log on.

It like your program is got a mind of its own lol.

Also, tomorrow I am getting a new video card in, going from a RX 580 to a RX 6650 XT sense i have had this 580 for years now.

It is that your setup for some reason sometimes fails with the OpenGL command to generate mipmaps, even on textures for which it worked fine earlier in the same process.

The heap crash is most likely caused by not properly recovering from that error in order to keep going instead of stopping the process. This test version should do it without heap crash now https://mega.nz/file/ZJ4VWDLb#SGyHh8rgHYORc1WqdwzvrjJWnihDonkJMwL6AuHDKIM

Test with default INIs.

[Rozen]

6 minutes ago, sheson said:

It is that your setup for some reason sometimes fails with the OpenGL command to generate mipmaps, even on textures for which it worked fine earlier in the same process.

The heap crash is most likely caused by not properly recovering from that error in order to keep going instead of stopping the process. This test version should do it without heap crash now https://mega.nz/file/ZJ4VWDLb#SGyHh8rgHYORc1WqdwzvrjJWnihDonkJMwL6AuHDKIM

Test with default INIs.

Okay going to test now.

[Rozen]

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?

[sheson]

6 minutes ago, 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?

Yes.

[Rozen]

4 minutes ago, sheson said:

Yes.

Will do.

[Rozen]

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.

[sheson]

7 minutes ago, 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.

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

[Rozen]

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]

just got done with the new run and no crash, i will test more tomorrow after I get my new video card installed.

[LordIceWolf]

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]

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]

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]

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]

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