Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Anprionsa[Ooze's Lounge] COPY_EXISTING AR0400.wed fails on BG2:EE / EET — WED files don't exis
#8
(03-25-2026, 07:27 PM)CamDawg Wrote:
(03-25-2026, 05:36 PM)Anprionsa Wrote: The EE engine appears to handle area layout/rendering through a different mechanism than classic BG2, where WED files were stored in the BIF/KEY structure and accessible via COPY_EXISTING.

FWIW, EE Fixpack uses COPY_EXISTING on multiple WED files without issue.

Hmmm, must be something else I'm missing then.

Thanks for taking the time to test it clean, Lava. And CamDawg, good to know EE Fixpack uses COPY_EXISTING on WEDs without trouble — that narrows it down.

I'm fairly confident now it's on my end. I tracked down a file caching issue in the installer where copied files weren't being properly flushed to disk before WeiDU tried to read them. That would explain why the KEY file lookup fails intermittently — the data just wasn't fully there yet. I've patched the copy routine so it should be resolved on the next install run. I'll report back either way.
  


Messages In This Thread
RE: [Ooze's Lounge] COPY_EXISTING AR0400.wed fails on BG2:EE / EET — WED files don't exis - by Anprionsa - 03-25-2026, 07:52 PM

Forum Jump:


Users browsing this thread:
2 Guest(s)

[Ooze's Lounge] COPY_EXISTING AR0400.wed fails on BG2:EE / EET — WED files don't exis00