Jump to content

Recommended Posts

Posted

Getting this Error code on the back end of generating DynDLOD

 

Load order FileID [7E] can not be mapped to file FileID for file "DynDOLOD.esm"
[1:17:04] 00000000 ???                                           
00fde228 DynDOLODx64.exe DynDOLODResourceStrings   848 dynMessageDialog
00fd5579 DynDOLODx64.exe xeMainForm              21210 TLODGenThread.Execute
005dda30 DynDOLODx64.exe System.Classes                ThreadProc
0042a465 DynDOLODx64.exe BrainMM                  2540 BrainMMThreadProxy
0041214a DynDOLODx64.exe System                        ThreadWrapper
005116b9 DynDOLODx64.exe madExcept                     ThreadExceptFrame
7ffc19eb KERNEL32.DLL                                  BaseThreadInitThunk
7ffc1a2a ntdll.dll                                     RtlUserThreadStart
[1:17:04] [TMessageDialog.Dialog] <Debug: Creating TTaskDialog>
[1:17:04] [TMessageDialog.Dialog] <Debug: [TMessageDialog.Dialog] Executing TTaskDialog>
Error: Load order FileID [7E] can not be mapped to file FileID for file "DynDOLOD.esm"
[1:21:26] [TMessageDialog.Dialog] <Debug: Gathering>
User says "Exit DynDOLOD"

 

Can someone help me understand this so i can fix this. This error code popped after i updated the DynDLOD, DynDLOD Resources 3, and all associated files

Posted
9 hours ago, P1r0th34 said:

Getting this Error code on the back end of generating DynDLOD

Load order FileID [7E] can not be mapped to file FileID for file "DynDOLOD.esm"
[1:17:04] 00000000 ???                                           
00fde228 DynDOLODx64.exe DynDOLODResourceStrings   848 dynMessageDialog
00fd5579 DynDOLODx64.exe xeMainForm              21210 TLODGenThread.Execute
005dda30 DynDOLODx64.exe System.Classes                ThreadProc
0042a465 DynDOLODx64.exe BrainMM                  2540 BrainMMThreadProxy
0041214a DynDOLODx64.exe System                        ThreadWrapper
005116b9 DynDOLODx64.exe madExcept                     ThreadExceptFrame
7ffc19eb KERNEL32.DLL                                  BaseThreadInitThunk
7ffc1a2a ntdll.dll                                     RtlUserThreadStart
[1:17:04] [TMessageDialog.Dialog] <Debug: Creating TTaskDialog>
[1:17:04] [TMessageDialog.Dialog] <Debug: [TMessageDialog.Dialog] Executing TTaskDialog>
Error: Load order FileID [7E] can not be mapped to file FileID for file "DynDOLOD.esm"
[1:21:26] [TMessageDialog.Dialog] <Debug: Gathering>
User says "Exit DynDOLOD"

Can someone help me understand this so i can fix this. This error code popped after i updated the DynDLOD, DynDLOD Resources 3, and all associated files

Moved to the DynDOLOD 3 Alpha thread. Read the first post which log, debug log and bugreport.txt to upload when making posts.

https://dyndolod.info/Installation-Instructions
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

You can not update existing DynDOLOD plugins made with older versions. Generate from scratch. https://dyndolod.info/Updating#New-DynDOLOD-Version

Posted
19 hours ago, blueetenicolet said:

So my temporary way to fix it is use NG DLL scripts to generate, and use final test DLL to overwrite after generate, and enter game. Seems the LOD working well.

Please test with version 1 (rename from *.1dll to just .dll), I expect the issue to still happen.

Then test with version 2 (rename from *.2dll to dll), I expect the issue not to happen. This is just a test, not really a fix just yet.

Post a list of all other DLL plugins that are installed.

Posted
50 minutes ago, sheson said:

Please test with version 1 (rename from *.1dll to just .dll), I expect the issue to still happen.

Then test with version 2 (rename from *.2dll to dll), I expect the issue not to happen. This is just a test, not really a fix just yet.

Post a list of all other DLL plugins that are installed.

You mean generate LOD with version1/2 or just test the bug with them?

Posted
3 minutes ago, blueetenicolet said:

You mean generate LOD with version1/2 or just test the bug with them?

No need to generate LOD, just drop-in the different DLLs into a load order that has the issue to test.

Posted (edited)
11 minutes ago, sheson said:

No need to generate LOD, just drop-in the different DLLs into a load order that has the issue to test.

OK

The LOD is generate with NG DLL and WorshipperACTI=0.

use version1 (SE DLL) to test, still happens.

use version2, not happen.

And here's a new .Net crash log (the crash is caused by somthing other but not DynDOLOD i think), it contains the plugin informations(sorry i don't know other way to post the dll list XD)

Crash_2023_1_3_20-13-26.txt

Edited by blueetenicolet
Posted (edited)

I have tried read the "damaged" save with version 2 DLL, the quest target pointer still not displayed, so i think the bug is happend when save the game.

Edited by blueetenicolet
Posted
13 minutes ago, blueetenicolet said:

OK

The LOD is generate with NG DLL and WorshipperACTI=0.

use version1 (SE DLL) to test, still happens.

use version2, not happen.

And here's a new .Net crash log (the crash is caused by somthing other but not DynDOLOD i think), it contains the plugin informations(sorry i don't know other way to post the dll list XD)

Crash_2023_1_3_20-13-26.txt 46.76 kB · 0 downloads

In MO2 right windows data tab, right click any folder and select "Save tree to text file" and upload that.

The crash logs like a problem with the WeaponMace NIF for the Weapon xx013780 in DIS_Armor_Fractions.esp.

Posted (edited)

@sheson@blueetenicolet I also ran the new DyndoLOD alpha with large reference fixes against my load order. If there's anything I can do to test to try and reproduce the bug of if you need me to check something else, please let me know.

Looks like I won't be starting my next playthrough before this is getting fixed anyways (in the process of moving between homes) :)

 

EDIT: Apart from the alias bug, the new NG with large reference bug workarounds enabled seems to do it's job quite nicely.

Edited by Trademark
Posted

So I fixed it. I found gamerpoets video on youtube and did a clean uninstall.  Wiping out all folders, even one under appdata which I was unaware of.  Reinstalled and he is there.  Just in case anyone else has this issue.  So NG dll works.  Sorry.  Keep up the good work.

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
×
×
  • Create New...

Important Information

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