DynDOLOD 3.00 Alpha 198

[sheson]

57 minutes ago, wizkaliffa said:

Reporting back that a BIOS update did solve the issue. For anyone else running an MSI MAG Tomahawk Z790 and updating BIOS to ver H.E0 (09/26/2024) fixed all errors

Great! Thanks for letting us know.

[xcal68]

More of a feature request: Would it be possible to make it so all the swap errors are found at once, instead of stopping the entire process when it finds one?  Run the program... stops on a circular swap... run the program... stops on a circular swap and over and over.  I have tons of _swap.ini.

[sheson]

13 minutes ago, xcal68 said:

More of a feature request: Would it be possible to make it so all the swap errors are found at once, instead of stopping the entire process when it finds one?  Run the program... stops on a circular swap... run the program... stops on a circular swap and over and over.  I have tons of _swap.ini.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

Just one example session that shows such an error, so I can determine the source for it.

[xcal68]

It's the error that tells you there's a circular reference in a _swap.ini file and to "permanently" remove all references to Dyndolod.  I don't actually need troubleshooting help.  Did you still need logs?  I can consider it when I'm home, if you do.

[Yomi]

Hi. I got an error on new version 183
Access violation at address 00000000013CD0A9 in module dyndolodx64.exe (offset CED0A9) Read of address 0000000000000000.

bugreport.txt DynDOLOD_SSE_Debug_log.7z

[sheson]

4 hours ago, xcal68 said:

It's the error that tells you there's a circular reference in a _swap.ini file and to "permanently" remove all references to Dyndolod.  I don't actually need troubleshooting help.  Did you still need logs?  I can consider it when I'm home, if you do.

The check exists to make sure there is nothing bad happening when updating existing DynDOLOD output. You are asking for a feature for a check that should not really report more than one file in the first place. So my guess is, it is because of mod(s). Which means somebody tries to patch an automatic patch, which is really not how any of this is supposed to work.

The log would tell me the filename of the INI. It would help me understand the actual cause of issue that prompts your request.

Try this test version https://mega.nz/file/RdYVzZLa#v4pkdc0g1swy2wedljhMb3lP-yZ0QPebSJ3e1pnXhYU

[sheson]

42 minutes ago, Yomi said:

Hi. I got an error on new version 183
Access violation at address 00000000013CD0A9 in module dyndolodx64.exe (offset CED0A9) Read of address 0000000000000000.

bugreport.txt 51.63 kB · 1 download DynDOLOD_SSE_Debug_log.7z 3.71 MB · 1 download

For future reference, also upload the normal DynDOLOD log in addition to the debug log.

Is this exact error repeatable? It seems a bit random, like there might be hardware issues, like unstable CPU or memory, BIOS settings for example. Test PC with prime95/OCCT.

Delete old bugreport.txt, old logs and run the test version from this post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419 and upload new log, debug log and bugreport.txt if it still happens.

[Yomi]

24 minutes ago, sheson said:

For future reference, also upload the normal DynDOLOD log in addition to the debug log.

Is this exact error repeatable? It seems a bit random, like there might be hardware issues, like unstable CPU or memory, BIOS settings for example. Test PC with prime95/OCCT.

Delete old bugreport.txt, old logs and run the test version from this post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419 and upload new log, debug log and bugreport.txt if it still happens.

Now new error: Access violation at address 0000000001A7D219 (CED219)

bugreport.txt DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.7z

Edited February 10, 2025 by Yomi

[MisterMorden]

Not reporting a bug, just wanted to ask about the update/changelog...I was wondering if the issue about the white river water lod mentioned in the following post was fixed (I didn't see it listed in the changelog)?

https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/674/#findComment-283570

Thanks!

[sheson]

9 minutes ago, MisterMorden said:

Not reporting a bug, just wanted to ask about the update/changelog...I was wondering if the issue about the white river water lod mentioned in the following post was fixed (I didn't see it listed in the changelog)?

https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/674/#findComment-283570

Thanks!

Yes. It should. If not, make a bug report.

[sheson]

1 hour ago, Yomi said:

Now new error: Access violation at address 0000000001A7D219 (CED219)

bugreport.txt 47.47 kB · 1 download DynDOLOD_SSE_log.txt 156.26 kB · 1 download DynDOLOD_SSE_Debug_log.7z 3.7 MB · 1 download

I updated the test version in this  post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419

Same as before, delete old logs, bugreport.txt, upload new ones.

[S-Matrix]

Hi! Getting an error running DynDOLOD for alpha-183; attaching logs along with line describing error details:

Error: Access violation at address 00000000011AD0A9 in module 'DynDOLODx64.exe' (offset CED0A9). Read of address 0000000000000000.

Also, in trying to attach the debug log directly, I realized the text file is 144MB in size - would that indicate something like a system problem right off the bat? Let me know if there's a preferred place to host the large text file, as for now I'm using a file.io/limewire link. I'm gonna give it another run in the meantime and see if the exact error is repeatable. 

bugreport.txt DynDOLOD_SSE_log.txt

Edited February 10, 2025 by S-Matrix

[sheson]

7 minutes ago, S-Matrix said:

Hi! Getting an error running DynDOLOD for alpha-183; attaching logs along with line describing error details:

Error: Access violation at address 00000000011AD0A9 in module 'DynDOLODx64.exe' (offset CED0A9). Read of address 0000000000000000.

Also, in trying to attach the debug log directly, I realized the text file is 144MB in size - would that indicate something like a system problem right off the bat? Let me know if there's a preferred place to host the large text file, as for now I'm using a file.io/limewire link. I'm gonna give it another run in the meantime and see if the exact error is repeatable. 

bugreport.txt 52.77 kB · 1 download DynDOLOD_SSE_log.txt 671.35 kB · 1 download

See posts above. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

Delete old logs, get and run the mentioned test version from https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419, upload new logs.

[WinterishClover]

Long time user - first time poster. I am also getting Access Violation right before dyndolod completes on new version. I also tried the version linked. Trying to upload logs but not sure how.

[Yomi]

12 minutes ago, sheson said:

I updated the test version in this  post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419

Same as before, delete old logs, bugreport.txt, upload new ones.

With new exe bugreport.txt is not created.
New error: no vmad for skyrimse.exe dyndolod_fistbornactivator "thoushaltbowtomaster" [acti:00000902]

DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.7z