4 replies to this topic

[josh_clue]

this is the same post on the latter part of my "parse error" post. maybe it'll
get more responses by being placed in a new thread.

i used the COPY command on weidu to install some of the new files for a mod that i am making for BG:TotSC. the dialogues compile, the new creatures are copied over and given names, BUT the custom .2DA, .BAM, and .STO files end up corrupted. i tried simply copying the .2DA .BAM and .STO files to the override directory and they work fine (although the stores lose their name since i didn't COPY and SAY). is there a different command for copying files onto the override directory?

jcompton and japheth have been helping me work out this problem but we still havn't reached a solution. this was my last post:

i tried doing the directory copying stuff you (jcompton) showed me but it didn't solve my problem.

i tried using earlier versions of weidu to see if anything would happen but nothing did. my 2da, bam, and sto files still end up "corrupted"

thing is, i tried to open one of the 2da files after weidu copied them over and compared them with the 2da file in my source directory
and here is what i saw:

***** from SOURCE directory, backstab.2da
2DA V1.0
1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
THIEF 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
*****

***** from weidu copied OVERRIDE directory, backstab.2da

2DA V1.0E00E000 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
THIEF 1 2 2 2 2 3 3 3 3 4 4 4 4 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
*****
did you see that? that "E00E000" inserted onto the weidu copied file? WHOA!

i started thinking that was causing the "corruption". i then delete the "E00E000" segment and guess what? the files work again. it had the same effect as if i had MANUALLY copied over the 2da files.

this would be no problem if all the files i were distributing were 2da files which are readily and easily copied over onto the override directory. but what of my "corrupted" bam and sto files? plus, this makes it a problem to distribute my mod

another oddity about this is that near infinity can still open the "corrupted" bam and sto files, but BG:TotSC just crashes when it creates the item or enters the store!

i'm thinking the files are still openable and are either IWD, BG2:ToB, PS:T, and IWD2 compatible BUT NO LONGER BG and BG:TotSC compatible.

help!

[japheth]

Josh: Can you zip up your distribution and sent it to japheth@spellholdstudios.net?

At least this way we can determine if it's a WeiDU problem, or a problem with your computer.

[weimer]

I had a spare second to look at this while doing laundry today. The problem is with Josh's TP2 file, which includes the line:

COPY  ~vault/2da~               ~override~    
  ~vault/cre/aasim.cre~           ~override/aasim.cre~    
          SAY NAME1 ~Aasim~
          SAY NAME2 ~Aasim~

It should not be too surprising to the studio audience that this ends up putting "random junk" at offset 8 in the resulting 2DA files. :-)

Josh, the SAY patch command applies to every file mentioned in the same COPY block. You only want to be naming the CRE files. Move them and the SAY to a separate COPY block and it should work fine.

[japheth]

Ah, nice catch Wes.

[josh_clue]

oh... wow. i never thought about it that way. geez, this is great!

nice catch indeed!

thanks, wes!

amazing... who'd thunk it?

wow.

now i'm happy.

thanks again!