A few things I've noticed.
#1
Posted 26 February 2003 - 05:36 PM
- Using --bif-get will /only/ retrieve files from the bifs, ignoring anything that may happen to be in the override. (This is probably intentional, but thought I should mention it).
- Polymorph(I:AnimationType*Animate) is invalid when compiling a .baf in IWD, even though everything is in order with the .ids files.
- In IWD, any Alignment(O:Object*,I:Alignment*Align) checks cause the .baf compiler to choke. This is because IWD lacks an "alignment.ids" file. It has an "align.ids" and an "alignmen.ids" file. This is not a WeiDU error, it's an error in the .ids files. Solution: rename align/alignmen.ids to "alignment.ids" or change the "trigger.ids" entry. Just wanting to make note here.
#2
Posted 27 February 2003 - 02:40 PM
Hmm this is strange, Alignment*Align means the game expects an Align.ids file. This should WeiDU do as well.- In IWD, any Alignment(O:Object*,I:Alignment*Align) checks cause the .baf compiler to choke. This is because IWD lacks an "alignment.ids" file. It has an "align.ids" and an "alignmen.ids" file. This is not a WeiDU error, it's an error in the .ids files. Solution: rename align/alignmen.ids to "alignment.ids" or change the "trigger.ids" entry. Just wanting to make note here.
The string after * sets the name of the ids file not the string before it!
#3
Posted 27 February 2003 - 03:50 PM
0x400A Alignment(O:Object*,I:Alignment*Alignment)
but no Alignment.IDS file (only a Alignmen.IDS). In BG2 for example itīs
0x400A Alignment(O:Object*,I:Alignment*Align)
I guess WeiDU should read only the first 8 characters. However there are IDS files with more than 8 characters in BG2 (MUSICLIST.IDS for example).
#4
Posted 27 February 2003 - 07:41 PM
Sorry, Dyara's trigger is more accurate for IWD. I was using the BG2 trigger out of habit.
#5
Posted 01 March 2003 - 11:46 PM
#6
Posted 02 March 2003 - 02:56 AM
[D:\Programme\Black Isle\BGII - RtW\Setup-RTW.exe] WeiDU version 110 Choose your language: 0 [English (International)] 1 [English (American)] 2 [Deutsch] 0 Using Language [English (International)] Install Component [Return To Windspear Beta 3.1.2] [R]e-Install, [N]o Change or [U]ninstall or [Q]uit?
I have to admit that Iīve used WeiDU 110 to install. Maybe itīs a problem to uninstall mods that are installed with an older version of WeiDU?
#7
Posted 02 March 2003 - 03:44 AM
weidu --game f:\bg1 --tlkout dialog.tlk --ftlkout dialogf.tlk --log bg1npcp\bg1npcp.debug bg1npcp\bg1npcp.tp2
Okay. Just checked. If I install from the command line with 110, I can't uninstall. However, if I install using a renamed WeiDU.exe (setup-whatever.exe), I can uninstall normally.
Nothing's changed in my mod setup or .tp2 and I can install/uninstall with 109 from the command line.
Is this a new thing in 110 or a bug with the command line .tp2 install?
EDIT: On an unrelated note...is RtW really going to have distinct English (int.) and English (US) translations? Someone is going to go through the trouble of adding the Us to color, honor, etc.? Heh.
#8
Posted 02 March 2003 - 04:36 AM
#9
Posted 02 March 2003 - 12:25 PM
#10
Posted 02 March 2003 - 01:13 PM
When I type Setup-RTW (without .exe) at command-line WeiDU doesnīt install but displays its usage:
D:\Programme\Black Isle\BGII - RtW>setup-rtw [SETUP-RtW] WeiDU version 110 WeiDU (version 110: "lovely bugfixes") usage: WeiDU [options] BAF,BCS,D,DLG,TRA,TP,TP2-files General Input Options: --game X set main game directory to X --nogame do not load any default game files --search X look in X for input files (cumulative) --tlkin X use X as DIALOG.TLK --ftlkin X use X as DIALOGF.TLK --tlkmerge X merge X into loaded DIALOG.TLK --yes answer all TP2 questions with 'Yes' --uninstall answer all TP2 questions with 'Uninstall' General Output Options: ...
setup-rtw.exe installs as usual.
#11
Posted 02 March 2003 - 07:11 PM
#12
Posted 03 March 2003 - 04:47 PM
Incoming.Blucher, can you send me the file WeiDU.log from when you do the command-line install and from when you do the renamed install? The difference will allow me to fix this bug.
#13
Posted 09 March 2003 - 02:03 PM
#14
Posted 09 March 2003 - 02:09 PM
Command line installation of a tp2 (with or without the .tp2 in the main dir) is still not working.






