DynDOLOD 3.00 Alpha 190

[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.txtFetching info... DynDOLOD_SSE_Debug_log.7zFetching info...

[sheson]

  On 2/10/2025 at 2:29 PM, 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.

Expand  

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]

  On 2/10/2025 at 3:11 PM, 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

Expand  

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]

  On 2/10/2025 at 3:53 PM, 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.

Expand  

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

bugreport.txtFetching info... DynDOLOD_SSE_log.txtFetching info... DynDOLOD_SSE_Debug_log.7zFetching info...

Edited February 10 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]

  On 2/10/2025 at 5:03 PM, 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!

Expand  

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

[sheson]

  On 2/10/2025 at 4:13 PM, 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

Expand  

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

Edited February 10 by S-Matrix

[sheson]

  On 2/10/2025 at 5:26 PM, 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

Expand  

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]

  On 2/10/2025 at 5:21 PM, 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.

Expand  

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

DynDOLOD_SSE_log.txtFetching info... DynDOLOD_SSE_Debug_log.7zFetching info...

[sheson]

  On 2/10/2025 at 5:33 PM, WinterishClover said:

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.

Expand  

Logs are text files.  They can be opened in notepad and their content posted to pastebin for example.
Or the files can be attached when posting (there is field to drag and drop) or uploaded to a free file service. Zip first them if they are large.
Also see my signature or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

[sheson]

  On 2/10/2025 at 5:36 PM, Yomi said:

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

DynDOLOD_SSE_log.txt 156.21 kB · 1 download DynDOLOD_SSE_Debug_log.7z 3.7 MB · 1 download

Expand  

Can you load the entire load order into xEdit and check if you can find a record with form ID 0x902?

Typically there shouldn't be one. In case there is one, report plugin / mod.

[xcal68]

  On 2/10/2025 at 3:40 PM, sheson said:

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/cYhCHYSL#mRbMXlvAgAprtXtaTMw1LIL7d0VsQ0lFnVJ2Atyui-k

Expand  

That fixed my issue.  Multiple files were reported in the console, but only interrupted generation one time.  Thanks.  I'll report the issues to the mod authors.

Edited February 10 by xcal68

[Yomi]

  On 2/10/2025 at 5:41 PM, sheson said:

Can you load the entire load order into xEdit and check if you can find a record with form ID 0x902?

Typically there shouldn't be one. In case there is one, report plugin / mod.

Expand  

00000902 not found
only fe000902 at ccQDRSSE001-SurvivalMode.esl