Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: April 07, 2015, 12:43:15 PM »

I am working on making this menu obsolete.
Posted by: Galactygon
« on: April 05, 2015, 02:43:46 AM »

The "problem" is that WeiDU lists available game languages in alphabetical order which places German (de_DE) on first position. Many times people unconsciously press "0" if they want to select english. I've almost fallen for this as well when I tested my mod with one of the WeiDU betas.

One possible solution might be to fetch the game language from the baldur.ini (or use english by default if this entry doesn't exist) and put it on first position in the game language selection.


I have had this issue as well (with v238) that I press 0 by reflex when the language dialogue comes up, so I had to manually modify the wiedu.conf file as I was getting strange <invalid reference>s when installing mods.

Another possible solution is to switch to using letters (ie "e" for english, "d" for german, etc.) instead to force the user to read through the text.
Posted by: Wisp
« on: February 14, 2015, 11:04:27 AM »

Next WeiDU will output DLGs as monotonically increasing structures, which satisfies both NI's assumptions as well as backward compatibility.
Posted by: Argent77
« on: February 13, 2015, 07:44:00 AM »

It looks like all of the affected DLG files contain one or more script structures (i.e. state trigger, transition trigger or action table structures) with their "Length" field set to 0. The DLG format definition in IESDP is open to interpretation in this matter, so I'm not sure if these are valid structures or not.
Near Infinity is treating these cases as invalid and I haven't found a DLG file affected by this issue in any unmodded game yet. On the other hand, the games don't seem to crash or behave unusual when triggering the affected dialogs. I can try to add a fix or work-around in Near Infinity, but I don't know if or when I'll be successful as it touches a fundamental design aspect of NI. Maybe WeiDU's dialog compiler can be changed to preserve empty script structures by adding a single newline or space character.
Posted by: Wisp
« on: February 11, 2015, 03:47:13 PM »

Actually, I'll get back to you. The DLG produced by WeiDU is structurally valid. This can equally well be a false positive by NI, but it's bed time now. Edit: the issue remains ridiculous. regardless.
Posted by: Mad Mate
« on: February 11, 2015, 03:20:46 PM »

Thanks Wisp!
Posted by: Wisp
« on: February 11, 2015, 03:10:38 PM »

It's harmless, as demonstrated by the fact it's existed since forever (the empty action DO bug). But I'll fix it all the same, because it's a ridiculous.
Posted by: Mad Mate
« on: February 11, 2015, 09:59:06 AM »

There is problem with corrupted DLG files with latest XPmod. Angel says that it is Weidu's fault.
Bug report with logs is here:
http://forums.pocketplane.net/index.php/topic,29333.msg336456.html#msg336456
Thanks!
Posted by: Wisp
« on: January 14, 2015, 02:45:46 PM »

Well, I suppose it is possible Debian Wheezy runs with a non-standard value. However, that system is sitting on my shelf at this time and I have no particular plans on hooking the drive back up (so I won't be checking). It's also the same system all 64-bit binaries in recent memory have been compiled on. FWIW, my current workstation (Fedora 21) uses the standard value.
Posted by: koteko
« on: January 13, 2015, 01:41:31 PM »

On Linux Mint 17.1 (equal to Ubuntu Trusty 14.04) I can confirm the amd64 binary returns is killed by SIGKILL immediately.

On all the binaries, that's the only one to fail. Using i386 is fine. *Might* have been caused by the fact that the PC it was compiled on had the following kernel value set to a non-default value:

http://cateee.net/lkddb/web-lkddb/DEFAULT_MMAP_MIN_ADDR.html

Can be checked easily:

Code: [Select]
$ cat /proc/sys/vm/mmap_min_addr
65536

That's the most common value I think. Might be worth to give it a try, Wisp (if it's you to compile the Linux version). But I'm just guessing.
Posted by: Wisp
« on: December 20, 2014, 05:17:53 AM »

The amd64 build of weinstall doesn't even run (apparently a segfault).
Which version of what distribution are you using?

The i386 build runs, but curiously reports its version as 23600
That'd be because the 32-bit version you are using is v236. I have verified that the 32-bit build being distributed in the 237 package is actually v237, so kindly make sure you haven't made a mistake on your end. (As you may or may not know, IWD: EE is only properly supported by 237 and greater).
Posted by: CrevsDaak
« on: December 18, 2014, 05:48:29 PM »

UPDATE: I managed to compile it from source, so now I have a 64bit weinstall that doesn't segfault and that reports its version as "23700". However, it still can't find the dialog.tlk, even when running weidu directly:

Code: [Select]
$ weidu --use-lang en_US bg2_tweaks/setup-bg2_tweaks.tp2
[weidu] WeiDU version 23700
[./chitin.key] 165 BIFFs, 37105 resources

ERROR: Unable to find DIALOG.TLK in:
        ./^dialog\.tlk$

Please run this program in your Infinity Engine game directory.

FATAL ERROR: Failure("Unable to find DIALOG.TLK")

I can't get it to work with IWD:EE on 64bit Linux...

The amd64 build of weinstall doesn't even run (apparently a segfault).

The i386 build runs, but curiously reports its version as 23600 and doesn't find the game's dialog.tk file:

Code: [Select]
$ weinstall bg2_tweaks
weidu --log setup-bg2_tweaks.debug  bg2_tweaks.tp2 setup-bg2_tweaks.tp2 bg2_tweaks/bg2_tweaks.tp2 bg2_tweaks/setup-bg2_tweaks.tp2
[weidu] WeiDU version 23600

ERROR: Unable to find DIALOG.TLK in:
        ./^dialog\.tlk$

Please run this program in your Infinity Engine game directory.

FATAL ERROR: Failure("Unable to find DIALOG.TLK")

And explicitly specifying it does not seem to work either:

Code: [Select]
$ weinstall --use-lang en_US bg2_tweaks
weidu --log setup---use-lang.debug  --use-lang.tp2 setup---use-lang.tp2 --use-lang/--use-lang.tp2 --use-lang/setup---use-lang.tp2  en_US  bg2_tweaks
[weidu] WeiDU version 23600
weidu: unknown option `--use-lang.tp2'.
                WeiDU (version 23600: "Your daily WTF")

usage: WeiDU [options] BAF,BCS,D,DLG,TRA,TP,TP2-files
...

$ weinstall --tlkin ./lang/en_US/dialog.tlk bg2_tweaks
weidu --log setup---tlkin.debug  --tlkin.tp2 setup---tlkin.tp2 --tlkin/--tlkin.tp2 --tlkin/setup---tlkin.tp2  ./lang/en_US/dialog.tlk  bg2_tweaks
[weidu] WeiDU version 23600
weidu: unknown option `--tlkin.tp2'.
                WeiDU (version 23600: "Your daily WTF")

usage: WeiDU [options] BAF,BCS,D,DLG,TRA,TP,TP2-files
...
Actually you're misplacing the options on weinstall without having specified a path for the .tlk. And when you ran WeiDU to set the language don't add any other parameters, because it won't make the --use-lang work that way. Also be sure you're in the path the contain the CHITIN.KEY file.
I would recommend doing this:
Code: [Select]
$ weidu --use-lang en_US
$ weinstall bg2_tweaks.tp2
Posted by: In.eth
« on: December 16, 2014, 10:26:02 PM »

UPDATE: I managed to compile it from source, so now I have a 64bit weinstall that doesn't segfault and that reports its version as "23700". However, it still can't find the dialog.tlk, even when running weidu directly:

Code: [Select]
$ weidu --use-lang en_US bg2_tweaks/setup-bg2_tweaks.tp2
[weidu] WeiDU version 23700
[./chitin.key] 165 BIFFs, 37105 resources

ERROR: Unable to find DIALOG.TLK in:
        ./^dialog\.tlk$

Please run this program in your Infinity Engine game directory.

FATAL ERROR: Failure("Unable to find DIALOG.TLK")
Posted by: In.eth
« on: December 16, 2014, 09:40:01 PM »

I can't get it to work with IWD:EE on 64bit Linux...

The amd64 build of weinstall doesn't even run (apparently a segfault).

The i386 build runs, but curiously reports its version as 23600 and doesn't find the game's dialog.tk file:

Code: [Select]
$ weinstall bg2_tweaks
weidu --log setup-bg2_tweaks.debug  bg2_tweaks.tp2 setup-bg2_tweaks.tp2 bg2_tweaks/bg2_tweaks.tp2 bg2_tweaks/setup-bg2_tweaks.tp2
[weidu] WeiDU version 23600

ERROR: Unable to find DIALOG.TLK in:
        ./^dialog\.tlk$

Please run this program in your Infinity Engine game directory.

FATAL ERROR: Failure("Unable to find DIALOG.TLK")

And explicitly specifying it does not seem to work either:

Code: [Select]
$ weinstall --use-lang en_US bg2_tweaks
weidu --log setup---use-lang.debug  --use-lang.tp2 setup---use-lang.tp2 --use-lang/--use-lang.tp2 --use-lang/setup---use-lang.tp2  en_US  bg2_tweaks
[weidu] WeiDU version 23600
weidu: unknown option `--use-lang.tp2'.
                WeiDU (version 23600: "Your daily WTF")

usage: WeiDU [options] BAF,BCS,D,DLG,TRA,TP,TP2-files
...

$ weinstall --tlkin ./lang/en_US/dialog.tlk bg2_tweaks
weidu --log setup---tlkin.debug  --tlkin.tp2 setup---tlkin.tp2 --tlkin/--tlkin.tp2 --tlkin/setup---tlkin.tp2  ./lang/en_US/dialog.tlk  bg2_tweaks
[weidu] WeiDU version 23600
weidu: unknown option `--tlkin.tp2'.
                WeiDU (version 23600: "Your daily WTF")

usage: WeiDU [options] BAF,BCS,D,DLG,TRA,TP,TP2-files
...
Posted by: khelban12
« on: December 14, 2014, 03:28:55 PM »

All I can suggest is that you try compiling from source. However, bitness makes no practical difference for weinstall, so if the 32-bit version works, you may just as well use that.

Yes i use the 32bit binary now and it works fine that is why i didn't try to compile it from source. I will keep the 32bit binary (and tolower from 236) and upgrade everything to 238 when it is released.

Thank you.