Beta 236.04

[Wisp]

Beta location.

New since last beta:

• Document WeiDU's script-handling abilities.
• Check validity of EE TLKs against the right directory.
• Translatable strings are provided for the BGEE languages Russian and Ukrainian.
• Document MOVE's behaviour when toFile already exists.
• If WeiDU fails to restore a MOVEd file during uninstallation, a warning is printed and the uninstallation continues.

Plus some things that have not made it into the change log because they are just documentation tweaks or stuff that would fall under another item already present in the log (like HANDLE_CHARSETS now recursing over directories in tra_path/%LANGUAGE%).

If all goes well, let's pencil in 237 for a timely and very expedient release in about 2 weeks.

[Isaya]

(like HANDLE_CHARSETS now recursing over directories in tra_path/%LANGUAGE%).

Thank you for that. I was wondering how to integrate our translation into Dark Horizons, where all dialog tra files are indeed in a subdirectory.

[Almateria]

Uh, have we figured out whether the big cat os x versions work across mavericks/yosemite? Because if they don't, then I compiled a thing. https://www.mediafire.com/?2ld12fv1p9sju52

[K4thos]

nothing new to report. Previous bug with EE TLK is indeed fixed. Thanks.

[CrevsDaak]

Uh, have we figured out whether the big cat os x versions work across mavericks/yosemite? Because if they don't, then I compiled a thing. https://www.mediafire.com/?2ld12fv1p9sju52

I tested with my 10.7 builds of WeiDU on 10.8, 10.9 and 10.10 and they worked fine. No idea about 10.6 nor 10.5.

[Wisp]

Uh, have we figured out whether the big cat os x versions work across mavericks/yosemite? Because if they don't, then I compiled a thing. https://www.mediafire.com/?2ld12fv1p9sju52

I tested with my 10.7 builds of WeiDU on 10.8, 10.9 and 10.10 and they worked fine. No idea about 10.6 nor 10.5.

I'm pretty sure 10.7 is backward compatible with 10.5. At least, IIRC, WeiDU has been built on 10.7 in the past and there were never any complaints. So presumably the only people not served by a 10.7 build are the ones who need 32-bit or PPC, but they would need different builds anyway.

[Wisp]

OS X version has been uploaded. Sorry about taking so long.

I will update the archive with "big cat" compiles when they are available.

[CrevsDaak]

OS X version has been uploaded. Sorry about taking so long.

I will update the archive with "big cat" compiles when they are available.

OK, here's the archive.

You might need to update/adjust WeiDU's script compiler for IWD:EE (some things are from BG:EE, but most stuff is new).
http://forums.gibberlings3.net/index.php?showtopic=26806
http://forums.gibberlings3.net/index.php?showtopic=26807
http://forums.gibberlings3.net/index.php?showtopic=26808

[Mad Mate]

Hi!
I just tested new weidu beta with lot of mods, and almost all went without problems. No new parse errors, warnings compared to last stable Weidu.
Only 2 mods can't install.
Jarls BGT Adventure Pack (http://kerzenburg.baldurs-gate.eu/downloads.php?do=downloadlatest&id=35) breaks in main component with this error:

Code: [Select]

[./override/AR6800.are] loaded, 14972 bytes
ERROR: cannot convert ab_RT_Itxt or %ab_RT_Itxt% to an integer
ERROR: [AR6800.are] -> [override] Patching Failed (COPY) (Not_found)
Stopping installation because of error.Jarls BGT Tweak Pack (http://kerzenburg.baldurs-gate.eu/downloads.php?do=downloadlatest&id=29) breaks in General fixes (same error as above) & in Special NPC Items with:

Code: [Select]

ERROR: illegal 4-byte read from offset 4924 of 4924-byte file AR8701.ARE
ERROR: [AR8701.ARE] -> [override] Patching Failed (COPY) (Failure("AR8701.ARE: read out of bounds"))
Stopping installation because of error.
Both are using Area Modding Tool by Qwinn (http://www.shsforums.net/topic/33231-area-modding-tool-tutorial-by-qwinn/) and install went without problems in Weidu 236.
Weidu.log and debug files are here: https://www.dropbox.com/s/29wdx0ltrbizbm0/Weidu%2023604%20debug.rar?dl=0
Hope this helps on the way to 237.

[Wisp]

Code: [Select]

[./override/AR6800.are] loaded, 14972 bytes
ERROR: cannot convert ab_RT_Itxt or %ab_RT_Itxt% to an integer
ERROR: [AR6800.are] -> [override] Patching Failed (COPY) (Not_found)
Stopping installation because of error.

Fixed. The old code wasn't using the variable, so it did not matter that it was not initialised.

Code: [Select]

ERROR: illegal 4-byte read from offset 4924 of 4924-byte file AR8701.ARE
ERROR: [AR8701.ARE] -> [override] Patching Failed (COPY) (Failure("AR8701.ARE: read out of bounds"))
Stopping installation because of error.


Can reproduce. It's a pretty bog-standard fj_are_structure on a standard BGT area, so I dunno what could be going wrong, but I'll look into it.

[The Imp]

Hi!
I just tested new weidu beta with lot of mods, and almost all went without problems. No new parse errors, warnings compared to last stable Weidu.
Only 2 mods can't install.
Jarls BGT Adventure Pack ...

Were these clean installs from the start up ... probably not, it could be that the mod itself is not doing anything wrong, it just can't read the data cause something else already broke the files to be edited... I would assume that --change-logging will be able to help a little... and then looking the files via Near Infinity for integrity check ...but really, I have no idea.

[Wisp]

Code: [Select]

ERROR: illegal 4-byte read from offset 4924 of 4924-byte file AR8701.ARE
ERROR: [AR8701.ARE] -> [override] Patching Failed (COPY) (Failure("AR8701.ARE: read out of bounds"))
Stopping installation because of error.


Can reproduce. It's a pretty bog-standard fj_are_structure on a standard BGT area, so I dunno what could be going wrong, but I'll look into it.

Okay, it's a simple bug in fj_are_structure (in the container substructure, number of vertices is a word and not a dword). Fixed. Plug for the new constants for GET_OFFSET_ARRAY(2). Don't use the raw offsets.

[Mad Mate]

Thank you, Wisp!
It is not that important mods for me, but some other mods that somebody else use, might have same problems.
All other mods from my weidu.log go without a glitch. So I don't have anything more to report.
Hope for 237, soon. 
Thanks again!
Terrific job!