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: Turambar90
« on: September 30, 2013, 03:58:05 AM »

does the amd64 version also set the WEIDU_ARCH variable to something like "amd64"? If not, would it be possible to introduce it, at least for next version? It would help with AT_s. TIA
I suppose it should. However, I feel I should point out that for GNU/Linux, it's still good form to not make assumptions about the system the program is running on (e.g., by including binaries), since WeiDU can be compiled for a larger set of systems than 32- and 64-bit x86 (e.g., there is also PPC). Additionally, WEIDU_ARCH is set at compile time, so it is possible to run 32-bit WeiDU (for which WEIDU_ARCH is "x86") on a 64-bit system.
thanks. I know that a 32 bit binary does not necessarily need 32-bit OS. But it might help performance if one uses the 64 bit version on a 64 bit system, and it's more likely that one has the required libraries installed.
If one uses a different arch than the "official" ones, then they probably already have enough knowledge, since they have to compile a custom version of WEIDU.
Posted by: Wisp
« on: September 29, 2013, 08:37:55 AM »

does the amd64 version also set the WEIDU_ARCH variable to something like "amd64"? If not, would it be possible to introduce it, at least for next version? It would help with AT_s. TIA
I suppose it should. However, I feel I should point out that for GNU/Linux, it's still good form to not make assumptions about the system the program is running on (e.g., by including binaries), since WeiDU can be compiled for a larger set of systems than 32- and 64-bit x86 (e.g., there is also PPC). Additionally, WEIDU_ARCH is set at compile time, so it is possible to run 32-bit WeiDU (for which WEIDU_ARCH is "x86") on a 64-bit system.
Posted by: CamDawg
« on: September 27, 2013, 02:49:54 PM »

Well, Apple stopped using the PowerPC processors in 2006 so it is time to let go I think...
... he says on a site dedicated to modding games from the late 90s/early 00s.

Also: devSin sighting, w00t!
Posted by: hook71
« on: September 27, 2013, 02:30:02 PM »

Well, Apple stopped using the PowerPC processors in 2006 so it is time to let go I think...
Posted by: devSin
« on: September 27, 2013, 01:50:29 PM »

I was going to check with devSin to see if he was prepared to continue compiling for PPC, but I was under the impression he was wanting to retire.
Yeah, I no longer compile WeiDU even for my own personal use and am not in a position to continue maintaining the Mac version.

Apologies to those affected.
Posted by: Turambar90
« on: September 27, 2013, 12:33:11 PM »

I compile for i386 and amd64 GNU/Linux (and 32-bit Windows). I haven't included the 64-bit Linux binaries in the beta releases because I haven't yet automated the merging of archives (and I did not know if they would be useful to anyone, so I did not do it by hand). Some folks (currently alnair) over at the BGEE boards are compiling for amd64 Mac. I was going to check with devSin to see if he was prepared to continue compiling for PPC, but I was under the impression he was wanting to retire. There possibly won't be any further PPC OS X builds in that case. The Windows build will probably continue to be 32-bit until hell freezes over, due to the setup-mymod.exe nonsense.
does the amd64 version also set the WEIDU_ARCH variable to something like "amd64"? If not, would it be possible to introduce it, at least for next version? It would help with AT_s. TIA
Posted by: Wisp
« on: September 27, 2013, 06:12:33 AM »

I compile for i386 and amd64 GNU/Linux (and 32-bit Windows). I haven't included the 64-bit Linux binaries in the beta releases because I haven't yet automated the merging of archives (and I did not know if they would be useful to anyone, so I did not do it by hand). Some folks (currently alnair) over at the BGEE boards are compiling for amd64 Mac. I was going to check with devSin to see if he was prepared to continue compiling for PPC, but I was under the impression he was wanting to retire. There possibly won't be any further PPC OS X builds in that case. The Windows build will probably continue to be 32-bit until hell freezes over, due to the setup-mymod.exe nonsense.
Posted by: Turambar90
« on: September 27, 2013, 04:17:08 AM »

Barring any further bugs (that can't be fixed in time), I'd like to have the new WeiDU out on Sunday (so it doesn't come as a surprise).
Wonderful! will it always be compiled for only linux-32, mac-ppc and win32? because from what I understand with BGEE mac amd64 is becoming more important, and with linux I have had some shared libraries missing which I had to install through multiarch (not for weidu itself IIRC but e.g. for the tis tools which are provided together).
Posted by: Wisp
« on: September 26, 2013, 10:35:02 AM »

Okay, the last one seemed to go over well, so how about this for the finals?
Quote
Please choose the language in which you wish to play the game.

If you later wish to play the game in a different language you will need to edit the file weidu.conf and reinstall your mods.
It's short, contains the necessary information and should hopefully be understandable to mostly everyone. I suppose we could also cut the second sentence and let everyone guess at what to do (but I imagine 99 % picks a language and sticks with it to the bitter end).

Actually changing baldur.ini to reflect this choice is perhaps a feature for next version.

Barring any further bugs (that can't be fixed in time), I'd like to have the new WeiDU out on Sunday (so it doesn't come as a surprise).
Posted by: Wisp
« on: September 25, 2013, 01:28:12 PM »

Wait, I've discovered a bug in HANDLE_AUDIO.

I installed G3A, then Auren, both of which use the HANDLE_AUDIO function (without arguments) and everything gets added just fine. I then chose to re-install G3A--so Auren uninstalls, G3A re-installs, and then Auren re-installs. In this case, Auren's audio is not added to the game as it's using the G3A paths when Auren's HANDLE_AUDIO is invoked.

Explicitly setting paths with Auren's HANDLE_AUDIO resolves the issue.
Ouch, in stack operations, the values of TP2_FILE_NAME, MOD_FOLDER and the rest are not updated for mods that are automatically handled. I'll see what I can do.
And fixed (it was a regression introduced in 231.10).
Posted by: CamDawg
« on: September 25, 2013, 10:00:24 AM »

It can wait. Is there a file I can add temporarily to fool the check as a workaround? A fake tobex ini perhaps?
If you have to do something I had better fix it. ...And done.
Well, crap, didn't mean to force the issue. Thanks!
Posted by: Kulyok
« on: September 25, 2013, 08:16:40 AM »

I'm suddenly reminded of all the backlash&confusion that's come after v200. I have a feeling we're going to deal with a lot of language-related questions after this comes out. Fortunately, we won't see this text message about the game's language on BG2/BG/Tutu/BGT installs, right?

Quote
My thoughts are roughly that it doesn't so much matter what the question is, as long as the obvious answer is obvious. Fritz knows he wants to play the game in German, so when the available answers include German, he's rather unlikely to pick the wrong language, even if he does not understand the question. On the other hand, it's nice if people who know what they are doing receive the information they need to do what they want.

But proceeding along this "shorter and simpler question" line, how about this:
Quote
Please choose the language in which you wish to play the game. This choice is different from the choice of the language in which you wish to install this mod.
What I would still like to convey is that mods will be unavailable in the other languages and perhaps that the choice is stored and automatically reused. Edit: hah, and with this phrasing, we can rewrite the info in baldur.ini to match the user's answer.

As a user, I think the first part is clear, but the second might be a little confusing(mod language? Where do I select it? When? How? Panic, panic!). Maybe
"Please choose the language in which you wish to play the game. You will be prompted for the mod's language later [in the installation]." Or maybe I'm being picky. Take your pick.
Posted by: Wisp
« on: September 25, 2013, 05:28:52 AM »

Can I somehow translate this line via tp2 of my mod?
Yes. It will be @-1040.
Posted by: AL|EN
« on: September 25, 2013, 04:53:34 AM »

But proceeding along this "shorter and simpler question" line, how about this:
Quote
Please choose the language in which you wish to play the game. This choice is different from the choice of the language in which you wish to install this mod.
What I would still like to convey is that mods will be unavailable in the other languages and perhaps that the choice is stored and automatically reused. Edit: hah, and with this phrasing, we can rewrite the info in baldur.ini to match the user's answer.
Much better now. Can I somehow translate this line via tp2 of my mod?
Posted by: Wisp
« on: September 25, 2013, 02:40:12 AM »

It can wait. Is there a file I can add temporarily to fool the check as a workaround? A fake tobex ini perhaps?
If you have to do something I had better fix it. ...And done.

Edit: oh, and if you, you know, want to be able to install your mod before the next version is out, you can create the file tobex_ini/tobexver.txt with the contents exactly equal to a number >= 20 and WeiDU should be fooled into thinking an acceptable version of ToBEx is installed.