Jump to content

DynDOLOD 3.00 Alpha 182


sheson

Recommended Posts

First of all I would like to apologize for any rudeness in my wording as I use DeepL.


Perhaps the load order checking method has changed since Alpha109, but I am getting errors in profiles where no problems were detected in 108.
I would like to try to correct it to the correct load order, but where should I look in the log?

Link to comment
Share on other sites

8 hours ago, TZV4344 said:

First of all I would like to apologize for any rudeness in my wording as I use DeepL.


Perhaps the load order checking method has changed since Alpha109, but I am getting errors in profiles where no problems were detected in 108.
I would like to try to correct it to the correct load order, but where should I look in the log?

Read the first post which log, debug log and bugreport.txt (if it exists) to upload when making posts.

As explained of the first post, if there are error messages prompts, read the entire message carefully and click the link "Click on this link for additional explanations and help for this message" or read https://dyndolod.info/Messages or https://dyndolod.info/Help for the associated help topics yourself.

If help with a message is required, use the "Copy this message to clipboard" link and past the text.

Link to comment
Share on other sites

6 hours ago, Jake0233 said:

It seems that the latest update to DynDOLOD produced an error when I have the mod "Teldryn Seros" installed. An error occurred when this mod is installed including its Lux Patch. 

Here are the logs when I attempted to build the LODs:

https://ufile.io/ro63bf07
https://ufile.io/y6j2vpat
https://ufile.io/2vxljsp1

It looks like the new alpha version was not installed into a new and empty folder.

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\.

It seems you started DynDOLOD one more time after the issue, thus the debug log that shows the problem has been replaced.

Please run DynDOLOD again to get new debug log and bugreport and upload them.

https://dyndolod.info/Messages/Can-Not-Copy-Record
Check the mentioned cell record xx0D7D2F in Lux - Teldryn Serious.esp in xEdit if you can spot a problem and the entire plugin for errors.
Double-check what is the last plugin to overwrite the cell record. Test if it works without the batched patch.

Link to comment
Share on other sites

Greetings. 

Long time supporter / user - first time posting in these forums. 

I have just upgraded to Alpha 109 from Alpha 106 and reran my LOD generation. No issues on 106 but I have encountered a repeatable error on 109. 

[Main Instruction]
Can not copy [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:641102F4]) from DBM_HelgenReborn_Patch.esp into DynDOLOD.esp.

[Content]
Access violation at address 000000000105A903 in module 'DynDOLODx64.exe'. Read of address 0000000000000000 Helgen Reborn.esp [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:631102F4])

Logs/Files here -> https://drive.google.com/file/d/1LPvitPttV2X0MF0tydgEYtRBBUdbacDG/view?usp=sharing

The only change I have made external to upgrading to Alpha 109 is to update Far Object LOD Improvement Project SSE.

Link to comment
Share on other sites

54 minutes ago, sheson said:

It looks like the new alpha version was not installed into a new and empty folder.

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\.

It seems you started DynDOLOD one more time after the issue, thus the debug log that shows the problem has been replaced.

Please run DynDOLOD again to get new debug log and bugreport and upload them.

https://dyndolod.info/Messages/Can-Not-Copy-Record
Check the mentioned cell record xx0D7D2F in Lux - Teldryn Serious.esp in xEdit if you can spot a problem and the entire plugin for errors.
Double-check what is the last plugin to overwrite the cell record. Test if it works without the batched patch.

I did what you asked and its still producing the same error.

Here are the logs:

https://ufile.io/foq80jxa = Bug Report

https://ufile.io/z77kdxrb = Debug_Log

I also tried to run it without the Lux Patch but it still produced an error at the same cell record from the original mod this time.

There were also no errors between the patch and its master.  I tried also running without the Bashed Patch earlier but still no avail.

Edit: the lux patch came from the official patches in the Lux page

Edited by Jake0233
Link to comment
Share on other sites

8 hours ago, SirLach said:

Greetings. 

Long time supporter / user - first time posting in these forums. 

I have just upgraded to Alpha 109 from Alpha 106 and reran my LOD generation. No issues on 106 but I have encountered a repeatable error on 109. 

[Main Instruction]
Can not copy [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:641102F4]) from DBM_HelgenReborn_Patch.esp into DynDOLOD.esp.

[Content]
Access violation at address 000000000105A903 in module 'DynDOLODx64.exe'. Read of address 0000000000000000 Helgen Reborn.esp [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:631102F4])

Logs/Files here -> https://drive.google.com/file/d/1LPvitPttV2X0MF0tydgEYtRBBUdbacDG/view?usp=sharing

The only change I have made external to upgrading to Alpha 109 is to update Far Object LOD Improvement Project SSE.

7 hours ago, Jake0233 said:

I did what you asked and its still producing the same error.

Here are the logs:

https://ufile.io/foq80jxa = Bug Report

https://ufile.io/z77kdxrb = Debug_Log

I also tried to run it without the Lux Patch but it still produced an error at the same cell record from the original mod this time.

There were also no errors between the patch and its master.  I tried also running without the Bashed Patch earlier but still no avail.

Edit: the lux patch came from the official patches in the Lux page

Thanks. Same problem. Will be fixed next version.

Edit: Should be fixed in Alpha-110

Link to comment
Share on other sites

9 hours ago, sheson said:

Read the first post which log, debug log and bugreport.txt (if it exists) to upload when making posts.

As explained of the first post, if there are error messages prompts, read the entire message carefully and click the link "Click on this link for additional explanations and help for this message" or read https://dyndolod.info/Messages or https://dyndolod.info/Help for the associated help topics yourself.

If help with a message is required, use the "Copy this message to clipboard" link and past the text.

I was going to post the log when I got home, but it seemed to be exactly the problem that was fixed in alpha-110.
Thanks for the update.

Link to comment
Share on other sites

[Window Title]
DynDOLOD

[Main Instruction]
Can not copy [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110]) from CollegeOfWinterholdImmersive.esp into DynDOLOD.esp.

[Content]
Access violation at address 000000000105A76B in module 'DynDOLODx64.exe'. Read of address 0000000000000000 CollegeOfWinterholdImmersive.esp [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110])

 

Link to comment
Share on other sites

1 hour ago, Ultivek said:

[Window Title]
DynDOLOD

[Main Instruction]
Can not copy [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110]) from CollegeOfWinterholdImmersive.esp into DynDOLOD.esp.

[Content]
Access violation at address 000000000105A76B in module 'DynDOLODx64.exe'. Read of address 0000000000000000 CollegeOfWinterholdImmersive.esp [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110])

 

I'm encountering this as well with version 6.2 of Immersive College Of Winterhold

Link to comment
Share on other sites

34 minutes ago, z929669 said:

See the sticky post at the top of this forum. It's probably your AV.

Thank you for the quick response.

I seem to have fixed my issue. I had downloaded the updated versions of DynDOLOD 3 and DynDOLOD Resources but had somehow missed the step of actually installing DynDOLOD 3. Rookie mistake... bleh!

Anyways, I will definitely add an exception within my AV just in case.

Link to comment
Share on other sites

8 hours ago, Ultivek said:

[Window Title]
DynDOLOD

[Main Instruction]
Can not copy [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110]) from CollegeOfWinterholdImmersive.esp into DynDOLOD.esp.

[Content]
Access violation at address 000000000105A76B in module 'DynDOLODx64.exe'. Read of address 0000000000000000 CollegeOfWinterholdImmersive.esp [CELL:9E37F34D] (in CWILustratoriumWorld "Lustratorium" [WRLD:9D37F110])

Moved to the DynDOLOD 3 Alpha thread. Read the first post which log, debug log and bugreport.txt (if it exists) to upload when makin posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum

Always use the latest versions as explained on the first post. https://dyndolod.info/Changelog This looks like the bug that was already reported and fixed in Alpha 110

As explained on the first post, click the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Messages/Can-Not-Copy-Record for more explanations and help.

Search this thread for similar posts and answer as epxlained on the first post. https://stepmodifications.org/forum/search/?&q="can not copy [CELL"&type=forums_topic&quick=1&item=17510

Link to comment
Share on other sites

On 1/7/2023 at 12:31 AM, sheson said:

Test with this version of DynDOLOD DLL NG https://mega.nz/file/JIxxWLyR#WQ5Da9xkK-jRVANdI31lmYA1BTngNKrkUB7OxgJBn9U

If the issue does not happen and if there are no other weird side effects, this is an actual fix.

Simple tested, the bug won't happen and Dyndolod installed successfully. I think it is fixed !

Link to comment
Share on other sites

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.