Jump to content
  • 0
Sign in to follow this  
Dodskrigare

Error: Can not copy [REFR:0F16904C]

Question

I keep getting this message

 

Exception in unit prepare line 579: Can not copy [REFR:0F16904C] (places SPatioWall01 [sTAT:00057A17] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -14,24) from LegacyoftheDragonborn.esm into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 13936)
 
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.
 
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/
 
Error: Can not copy [REFR:0F16904C] (places SPatioWall01 [sTAT:00057A17] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -14,24) from LegacyoftheDragonborn.esm into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 13936)
 
Not sure what to do to resolve the issue. Using 2.65 for SSE.

Share this post


Link to post
Share on other sites

10 answers to this question

Recommended Posts

  • 0

Check log lines above the exception for additional hints. Check the FAQ and search official forum

 

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. 
 
Edited by sheson

Share this post


Link to post
Share on other sites
  • 0

Disabling my bashed patch fixed it it seems.

 

Does it not like the developer versions of Wrye Bash? I rebuilt my bashed patch just to make sure about things and it still gave me that error.

Share this post


Link to post
Share on other sites
  • 0

Disabling a plugin is not a fix, but a troubleshooting step to determine the cause of a problem. xEdit/xLODGen/DynDOLOD like plugins that are not corrupt.

 

You used version 307.201905311918 from the dropbox?

Share this post


Link to post
Share on other sites
  • 0

Using 307.201904161810. It's been working so I haven't checked to see if they updated it. I'll get the newer version and see if that helps.

 

Never had problems with DynDOLOD before, not sure what about it is giving me a problem this time.

Share this post


Link to post
Share on other sites
  • 0

Even with the other version of Wrye Bash, it still gives me the error about Legacy. And I checked it for errors in xEdit and it came up clean.

Share this post


Link to post
Share on other sites
  • 0

xEdit checks for errors. Wrye Bash gets data assignments wrong. E.g. A while back it flipped x/y values and that time adds the permanent cell into the temporary group.

 

You did read this thread, https://forum.step-project.com/topic/14127-can-not-copy-refr0c16904c-places-spatiowall01-stat00057a17-in-grup-cell-persistent-children-of-cell00000d74

 

Check if 00000D74 in the Bashed Patch is a direct child of the Worldspace 0000003C. 

It should not be inside Block 0,0 / Sub-Block 0,0 for temporary cells.

Edited by sheson

Share this post


Link to post
Share on other sites
  • 0

You can even see the same form id being listed twice, once correctly as a child of the worldspace 0000003C and once as a temporary cell in the temporary Blocks. 

Share this post


Link to post
Share on other sites
  • 0

So will removing it from Block 0,0 / Sub-block 0,0 fix the problem? It doesn't seem to matter what I do, the bashed patch builds that way.

Share this post


Link to post
Share on other sites
  • 0

As you already noted, xEdit error check does not detect this problem. There may be others. I suggest to delete corrupt plugins.

 

Best to report and discuss the issue with the Wrye Bash devs.

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
Sign in to follow this  

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