DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[CVSickle]

  On 2/7/2020 at 1:18 PM, sheson said:

If the error still happens at "Processing 5 patches from DynDOLOD\DynDOLOD_SSE_cuttingroomflooresp_tamriel.patch", check the plugin is at the load order hex number that is mentioned in the error message.

If that does not help check the last plugin to overwrites 0001A280 or 0001A26F.

 

xEdit checks for some typical logical errors made by CK and people. Patchers, tools can create wrong data when saving/creating plugins which only trigger checks in xEdit or cause problems if records are accessed for copying.

Let me check to make sure I understand what you're saying... The error does consistently happen at "Processing 5 patches from DynDOLOD\DynDOLOD_SSE_cuttingroomflooresp_tamriel.patch" when I have the conflict resolution plugin enabled, so I need to verify that the audio patches merged plugin is at load order index [90]? I've definitely verified that Audio Patches Merged.esp is at index [90].

 

Here's a question about the load order index... the log indicates load order index [90] is causing the problem, but the bug report mentions load order index [94]. Does that seem weird?

 

And I will definitely check on 0001A280 and 0001A26F as you mentioned, but what am I looking for there? I'll be home later this evening and I'll be able to look into this more then.

 

Thanks again for the help!

[combatfun]

i got no bugs or problems. just wanted to let you a big thanks here! dyndolod is meanwhile well known and the results are, especially together with sselodgen terrain, outstanding. 

[sheson]

  On 2/7/2020 at 1:33 PM, CVSickle said:

Let me check to make sure I understand what you're saying... The error does consistently happen at "Processing 5 patches from DynDOLOD\DynDOLOD_SSE_cuttingroomflooresp_tamriel.patch" when I have the conflict resolution plugin enabled, so I need to verify that the audio patches merged plugin is at load order index [90]? I've definitely verified that Audio Patches Merged.esp is at index [90].

 

Here's a question about the load order index... the log indicates load order index [90] is causing the problem, but the bug report mentions load order index [94]. Does that seem weird?

 

And I will definitely check on 0001A280 and 0001A26F as you mentioned, but what am I looking for there? I'll be home later this evening and I'll be able to look into this more then.

 

Thanks again for the help!

The other way around. The error message "Load order FileID [xx] can not be mapped to file FileID for file xxx.esp" gives a hint wich plugin to check for error first.

e.g. the plugin that is listed at load order xx hex at the beginning of  the log for that same generation.

 

Both the log and the bugreport are being appeneded to, so if you see different numbers, it means they are not from the same generation attempt, just scroll down/up to he next run. Best to delete both files before testing  a new run to not get confused by older reports and log entries.

  On 2/7/2020 at 3:23 PM, combatfun said:

i got no bugs or problems. just wanted to let you a big thanks here! dyndolod is meanwhile well known and the results are, especially together with sselodgen terrain, outstanding. 

You are welcome.

[CVSickle]

  On 2/7/2020 at 4:50 PM, sheson said:

Both the log and the bugreport are being appeneded to, so if you see different numbers, it means they are not from the same generation attempt, just scroll down/up to he next run. Best to delete both files before testing  a new run to not get confused by older reports and log entries.

I definitely deleted the bugreport file before doing the run that created these files, because like you said I was confused why those hex indexes were different.  Both the bug report and the log files have exactly the same time on them, which tells me they're from the same run.  You can verify that by clicking the information button on the OneDrive links to the files (top-right of the page, the little (i) symbol). The modified date is when they were created on my PC, and the created date is when I uploaded them to OneDrive.

 

The DynDOLOD log has always pointed to the Audio Patches Merged plugin when I have this error, which has always been at index [90].  The bug report seems to be pointing at [94] which is the Realistic Water 2 plugin.

[sheson]

  On 2/7/2020 at 5:20 PM, CVSickle said:

I definitely deleted the bugreport file before doing the run that created these files, because like you said I was confused why those hex indexes were different.  Both the bug report and the log files have exactly the same time on them, which tells me they're from the same run.  You can verify that by clicking the information button on the OneDrive links to the files (top-right of the page, the little (i) symbol). The modified date is when they were created on my PC, and the created date is when I uploaded them to OneDrive.

 

The DynDOLOD log has always pointed to the Audio Patches Merged plugin when I have this error, which has always been at index [90].  The bug report seems to be pointing at [94] which is the Realistic Water 2 plugin.

It means there are at least two errors happening. It's only a hint anyways.

[GadenKerensky]

I received this error when performing TexGen, and even running DynDOLOD after doesn't seem to complete as it should. Can anyone tell me what this error is, and then once it's fixed, or if it's not a problem, I'll run DynDOLOD and see if I get the same issue?

[CVSickle]

  On 2/7/2020 at 6:22 PM, sheson said:

It means there are at least two errors happening. It's only a hint anyways.

So, I have absolutely no idea why, but the Dreams and Nightmares Music Mod plugin that I merged into the Audio Patches merge was the source of the problem. It changes the music type of many cells to make them more unique, and I had forwarded that change into my conflict resolution patch. I realized this when I reverted the music in the Whiterun Worldspace record to vanilla, which I only thought to try because you suggested I look at that record. DynDOLOD made it past the error until the solitude worldspace did something similar.

 

First thing I tried was obviously removing the plugin from the merge, thinking that the compacting of records caused some inconsistency, but that did nothing to get rid of the error.  Then, I tried several versions of the mod (none of which have any errors according to xEdit), and none of those worked either. I even tried saving the mod in the CK in case something weird was going on.

 

I ended up just removing the CELL and Worldspace records from the plugin and put it back into the merge. DynDOLOD can complete now, so I'm just going to live without the region-unique music.  I've already put too much time into this.

 

It's frustrating though, because I've ran DynDOLOD previously with Dreams and Nightmares' cell and worldspace music changes forwarded to a conflict resolution patch. As best I can tell, that was using DynDOLOD version 2.74. Has anything changed in DynDOLOD that would cause this error from the music type values to start popping up?

 

Either way, thank you for pointing me in the right direction so I could get this sorted out. You've been a great help and I appreciate it.

[sheson]

  On 2/7/2020 at 11:24 PM, GadenKerensky said:

I received this error when performing TexGen, and even running DynDOLOD after doesn't seem to complete as it should. Can anyone tell me what this error is, and then once it's fixed, or if it's not a problem, I'll run DynDOLOD and see if I get the same issue?

Check the log for error messages. Search for them on this forum.

[sheson]

  On 2/8/2020 at 2:03 AM, CVSickle said:

So, I have absolutely no idea why, but the Dreams and Nightmares Music Mod plugin that I merged into the Audio Patches merge was the source of the problem. It changes the music type of many cells to make them more unique, and I had forwarded that change into my conflict resolution patch. I realized this when I reverted the music in the Whiterun Worldspace record to vanilla, which I only thought to try because you suggested I look at that record. DynDOLOD made it past the error until the solitude worldspace did something similar.

 

First thing I tried was obviously removing the plugin from the merge, thinking that the compacting of records caused some inconsistency, but that did nothing to get rid of the error.  Then, I tried several versions of the mod (none of which have any errors according to xEdit), and none of those worked either. I even tried saving the mod in the CK in case something weird was going on.

 

I ended up just removing the CELL and Worldspace records from the plugin and put it back into the merge. DynDOLOD can complete now, so I'm just going to live without the region-unique music.  I've already put too much time into this.

 

It's frustrating though, because I've ran DynDOLOD previously with Dreams and Nightmares' cell and worldspace music changes forwarded to a conflict resolution patch. As best I can tell, that was using DynDOLOD version 2.74. Has anything changed in DynDOLOD that would cause this error from the music type values to start popping up?

 

Either way, thank you for pointing me in the right direction so I could get this sorted out. You've been a great help and I appreciate it.

DynDOLOD is a modified xEdit. It is xEdit code that reads and writes plugin data and it is its checks and messages you are seeing.

 

I would need the broken plugin in order to check what is wrong with it.

[GadenKerensky]

I'm still having that error. I'm new to this, so I don't really know where I should be looking; there's a lot of information there. What exactly am I looking for? Can I have a walkthrough on how to get through this?

[sheson]

  On 2/9/2020 at 3:58 AM, GadenKerensky said:

I'm still having that error. I'm new to this, so I don't really know where I should be looking; there's a lot of information there. What exactly am I looking for? Can I have a walkthrough on how to get through this?

TexGen/DynDOLOD has a Messages window with the log. The log contains information what it is doing. Search it for error messages. When the programs are closed the message log is saved to DynDOLOD\Logs\TexGen_SSE_log.txt so it can be open in notepad.

 

If you need help with deciphering the log, upload or paste entire log to a file service or pastebin.

 

See this post that is probably related:

https://forum.step-project.com/topic/14518-executing-texconv-returned-error-c0000135-vruntime140dll-or-vcruntime140-1dll-was-not-found/page-2?do=findComment&comment=239038

Edited February 9, 2020 by sheson

[TheDude]

Hi, I'm really loving Dyndolod but cant seem to get the latest version to work...? It generates a lot of error which I've never encountered before and the previous version I used (v 2.74) worked flawlessly, so thats why Im pretty confused right now...  Anyway, Im posting my log files here hoping someone can help me fix these problems. Otherwise I can just rollback to version 2.74, but still, would be really interesting to know what is causing these errors... 

Texgen log: https://1drv.ms/t/s!Av3hnni9at-Cg-VRFOLQ_xhJiPEMVg?e=j2plOh

Dyndolod log: https://1drv.ms/t/s!Av3hnni9at-Cg-VQKnjfuT6Fp6LMCQ?e=P2YegI

All the best!

[sheson]

  On 2/18/2020 at 5:40 PM, TheDude said:

Hi, I'm really loving Dyndolod but cant seem to get the latest version to work...? It generates a lot of error which I've never encountered before and the previous version I used (v 2.74) worked flawlessly, so thats why Im pretty confused right now...  Anyway, Im posting my log files here hoping someone can help me fix these problems. Otherwise I can just rollback to version 2.74, but still, would be really interesting to know what is causing these errors... 

Texgen log: https://1drv.ms/t/s!Av3hnni9at-Cg-VRFOLQ_xhJiPEMVg?e=j2plOh

Dyndolod log: https://1drv.ms/t/s!Av3hnni9at-Cg-VQKnjfuT6Fp6LMCQ?e=P2YegI

All the best!

All you have to do is to actually read the logs, then search for the error message.

 

From the TexGen log:

Executing TexConv returned error C0000135: "E:\Spel\Vortex\Skyrim SE\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha  -f BC7_UNORM -bcquick -o "E:\Spel\Vortex\Skyrim 

 

 

From the DynDOLOD log:

Executing TexConv returned error C0000135: "E:\Spel\Vortex\Skyrim SE\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -m 1 -f R8G8B8A8_UNORM -o "C:\Users\Team Bökarn\AppData\Local\Temp\SSEEdit" "C:\Users\Team Bökarn\AppData\Local\Temp\SSEEdit\048759FDFE36456CAD8C33237F95D17C.dds">

 

 

Searching finds this:

https://forum.step-project.com/topic/14518-executing-texconv-returned-error-c0000135-vruntime140dll-or-vcruntime140-1dll-or-thatch03snowdds-was-not-found/

[TheDude]

  On 2/18/2020 at 6:19 PM, sheson said:

All you have to do is to actually read the logs, then search for the error message.

 

From the TexGen log:

Executing TexConv returned error C0000135: "E:\Spel\Vortex\Skyrim SE\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha  -f BC7_UNORM -bcquick -o "E:\Spel\Vortex\Skyrim 

 

 

From the DynDOLOD log:

<Error preparing texture textures\terrain\lodgen\skyrim.esm\srg_treepineforest01_0001306d.dds for atlas: Error loading textures\terrain\lodgen\skyrim.esm\srg_treepineforest01_0001306d.dds: Executing TexConv returned error C0000135: "E:\Spel\Vortex\Skyrim SE\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -m 1 -f R8G8B8A8_UNORM -o "C:\Users\Team Bökarn\AppData\Local\Temp\SSEEdit" "C:\Users\Team Bökarn\AppData\Local\Temp\SSEEdit\048759FDFE36456CAD8C33237F95D17C.dds">

 

 

Searching finds this:

https://forum.step-project.com/topic/14518-executing-texconv-returned-error-c0000135-vruntime140dll-or-vcruntime140-1dll-or-thatch03snowdds-was-not-found/

Hi Sheson and thanks a lot for your support! Yes, I saw the errors but couldnt figure out what was causing them, especially since everything works in v 2.74 (I just rerun that version without a single error...). But thanks, Ill read the forum! Cheers!

[TheDude]

It worked like a charm, thanks a lot!