Jump to content
  • 0
Laptoprocker

Can not copy [REFR:0D083B46] (places CYRFarmhouseDoor01 "Door" [DOOR:0D07EC12]

Question

Whenever I try to run DynDOLOD on High I get the following error:

 

[00:00:10.371] Exception in unit prepare line 581: Can not copy [REFR:0D083B46] (places CYRFarmhouseDoor01 "Door" [DOOR:0D07EC12] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -1,-1) from BSHeartland.esm into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 14062)
[00:00:10.371]
[00:00:10.371] Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors.
[00:00:10.371]
[00:00:10.371] If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/
[00:00:10.373] Error: Can not copy [REFR:0D083B46] (places CYRFarmhouseDoor01 "Door" [DOOR:0D07EC12] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -1,-1) from BSHeartland.esm into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 14062)
 
It is obviously related to Beyond Skyrim Bruma, but I don't know what went wrong (I even tried to replace the .esm file just to make sure I didn't corrupt or edit it in any way.) What gives?

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

Follow the suggestions made in the log messages.
 
Check log lines above the exception for additional hints. Check the FAQ and search official forum for those errors.
 
Checking the FAQ finds this answer:
 
FAQ: DynDOLOD.exe: Can not copy xxxx from xxxx.esp into xxx.esp
A: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option. 
A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.
 
If removing the bashed patch lets the process run through, it means that the bashed patch is broken and needs to be generated again with a newer version of Wrye Bash
 

Searching the forum for the "Can not copy" error message finds these related thread:
 
https://forum.step-project.com/topic/14514-can-not-copy
https://forum.step-project.com/topic/14301-can-not-copy
https://forum.step-project.com/topic/14127-can-not-copy
https://forum.step-project.com/topic/14136-can-not-copy
https://forum.step-project.com/topic/14025-can-not-copy
https://forum.step-project.com/topic/14140-can-not-copy
https://forum.step-project.com/topic/14205-can-not-copy
https://forum.step-project.com/topic/14256-can-not-copy
 
It seems you kind of went with the third suggestions first, but did not post the entire bugreport and log as requested:

If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum

Edited by sheson

Share this post


Link to post
Share on other sites
  • 0

Thanks for the quick reply! I regenerated the Wrye Bash patch (I am using the latest build) and the problem still persists, however if I disable the bashed patch before running DynDOLOD then it works. Do I need to have the bashed patch enabled for DynDOLOD or should I be good to go if I just run it with the bashed patch disabled?

Share this post


Link to post
Share on other sites
  • 0

If removing the bashed patch (or any plugin causing a similar error) lets the process run through, it means that the bashed patch is broken.

 

With "latest build" you mean Wrye Bash 307 Beta 5 released yesterday?

Share this post


Link to post
Share on other sites
  • 0

The Bashed patch seems fine, all the entries are there takes the same amount of time to run as usual. Tested with four different Wrye Bash versions. DynDOLOD still taps out at BS_Heartland.esm

Share this post


Link to post
Share on other sites
  • 0

Upload the broken bashed patch to a file service and I will have a look.

Share this post


Link to post
Share on other sites
  • 0

Ok so the Wrye Bash team pushed out a hotfix, so the tool is now at 5.1 beta officially. That version now generates a proper Bashed Patch (they fixed that bug) but DynDOLOD still refuses to load with it enabled sadly :I Any other ideas?

Share this post


Link to post
Share on other sites
  • 0

"DynDOLOD still refuses to load with it enabled" is not a proper problem description.

 

If removing a plugin lets the process run through, it means that the plugin is broken and needs to be fixed. The xEdit code handling records is very mature.

Upload or paste the entire log to pastebin that shows the problem. Upload the plugin to a file service if you can not find out what the problem in the plugin is.

 

I am happy to find out what went wrong in order to have Wrye Bash (or xEdit for that matter) fixed like we did several time in the past already.

Edited by sheson

Share this post


Link to post
Share on other sites
  • 0

Have a pretty similar problem (the damn door).

 

Here's my log:

https://pastebin.com/EFz8Whum

 

I'm using the last Wyre Bash release and yes, it's probably due to the broken Bashed_patch since it works by disabling.

That said I tried to rebuild the bashed patch several time and clean all LOOT message possible but didn't work.

Share this post


Link to post
Share on other sites
  • 0

I've tried to run Wrye Bash with the last build but unfortunately it doesn't work with mo2 (show the game selection menu but crash just after that).

Currently I'm using the last update from the Nexus page, I think is the 307.2020.0108.1351 beta and works with mo2.

If you think will be useful I'm uploading my bashed patch.

https://www.mediafire.com/file/ni9vejq7j6qn4vt/Bashed_Patch%2C_0.esp/file

Share this post


Link to post
Share on other sites
  • 0

Tried with the discord version, didn't work either.

 

Following the topic linked by sheson I try looking for the mod causing the issue in the batched patch and it was caused by Interesting NPC, I disabled in Wrye Bash importing cell and it works fine.

Share this post


Link to post
Share on other sites
  • 0

Based on current discord discussions, the plugin triggering this will be more or less random.

 

Until there is an update to Wrye Bash that addresses this issue, I suggest to not check the "Import Cells" option.

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.