Hi everybody. I tired it again, and this time with the _new_ installer script. It works now! Sorry I was little distracted in the last months.

Thanks for the feedback ;)

Update

Baldur’s Gate 2 - Enhanced Edition

* Improve dependencies handling
    - Add missing dependency on OpenSSL 1.0.0 for Gentoo
    - Missing dependency on libexpat.so.1
    - Missing dependency on libX11.so.6
    - If libxrandr2 is not available trying to run the game in full screen (default display mode) on Mesa drivers won’t work, and might lock the X server
    - Add dependency on ALSA plugins, to ensure audio plays on systems without PulseAudio
    - Hardware cursor doesn’t work without libXcursor.so.1

Update

Baldurʼs Gate (original classic)

* Fix cursor rendering issues in full screen mode
* Fix resolution switching issues
* Fix really poor graphical performances with WINE ≥ 4.0

Update

Baldur’s Gate 2 - Enhanced Edition

* Add support for provided 64-bit binary

Update

Baldurʼs Gate Ⅱ - Enhanced Edition

* Build a dedicated package for each localization
    English localization is included in the base data package, to be used as a fallback with incomplete localizations
    Installing an extra localization on top of the English one is not required

Update

Baldurʼs Gate - Enhanced Edition

• Add support for 64-bit binary
• Improve handling of libjson.so.0 requirement

Hi everyone,

I am trying to install BG EE on Ubuntu 18.04 with the ./play script. What I get is this output:

$ sh ./play-baldurs-gate-1-enhanced-edition.sh
Using baldur_s_gate_enhanced_edition_en_2_5_23121.sh
Checking integrity of baldur_s_gate_enhanced_edition_en_2_5_23121.sh OK
Using baldurs-gate-1-enhanced-edition_icons.tar.gz
Checking integrity of baldurs-gate-1-enhanced-edition_icons.tar.gz OK
Using libssl_1.0.0_32-bit.tar.gz
Checking integrity of libssl_1.0.0_32-bit.tar.gz OK
Extracting data from libssl_1.0.0_32-bit.tar.gz OK
Using libssl_1.0.0_64-bit.tar.gz
Checking integrity of libssl_1.0.0_64-bit.tar.gz OK
Extracting data from libssl_1.0.0_64-bit.tar.gz OK
Extracting data from baldur_s_gate_enhanced_edition_en_2_5_23121.shtar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains ‘\r\b\024\344\246\352?\271)\224s4’ where numeric off_t value expected
tar: Exiting with failure status due to previous errors

What's going wrong? Can someone help me, please?

There seems to be an issue with the version of `bsdtar` that is provided by your system.
Could you please share the return of the following command, so that we may know a bit more about this tool version? ---

There might be an alternative that require only a slight tweak to the game script, so it does not require the use of `bsdtar`.
Open `play-baldurs-gate-1-enhanced-edition.sh` in a text editor, and look for the line 52, that should look like: Replace this line by the following one: Then run the script again, this time it should use `unzip` instead of `bsdtar` for extracting the game data from the installer.

Hi vv221

bsdtar 3.2.2 - libarchive 3.2.2 zlib/1.2.11 liblzma/5.2.2 bz2lib/1.0.6 liblz4/1.7.1

I don't know why but after your trick the outcome is the same, it keeps using bsdtar

Extracting data from baldur_s_gate_enhanced_edition_en_2_5_23121.shtar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains ‘\r\b\024\344\246\352?\271)\224s4’ where numeric off_t value expected
tar: Exiting with failure status due to previous errors

Thank you for the time you put in this project

It seems to be a bug that prevent to get the correct ARCHIVE_GOG_TYPE and use always tar

If I use
bsdtar --directory test --extract --file baldur_s_gate_enhanced_edition_en_2_5_23121.sh
everything work fine and I have game directories extracted in test

But if I use
tar --directory test --extract --file baldur_s_gate_enhanced_edition_en_2_5_23121.sh
I get the same error I have with the ./play script
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains ‘\r\b\024\344\246\352?\271)\224s4’ where numeric off_t value expected
tar: Exiting with failure status due to previous errors

I have fixed it. Here the problem and the fix for a future release.

I just moved the line 175 and 210 from before the if block of instructions to the line after the if closure

Hope can be useful for the next players.

Thank you guys.

I double checked, the ARCHIVE="$ARCHIVE_MAIN" lines are actually where they should be.
But for some reason on your system the ARCHIVE declarations on lines 177 and 212 seem to leak outside of their scope.

I can see two reasons for that:
- a bug in your shell interpreter
- an error when you downloaded the script

Did you directly download the script, or displayed its content and copied it into a new file?

Then I don’t understand what triggered the variable leaking on your system.
I guess I would need to setup a Ubuntu 18.04 to run some tests, but I’m not sure when I’m going to have time for that…