The response I got from GOG support: I don't quite get it. Why can't support team approach this directly? And if they need product team, why does it take so long to figure things out?

You mean the same inXile that still ships a broken Wasteland 2 DC Linux build? The same one that still hasn't brought the Bard's Tale (2004) patch to gog after years? The same one that won't produce a Linux build for the remastered BT1-3 because Steam-Wine is good enough?

Incredible.

They somehow posted a bad installer the same day as InXile gave it to them, but they can't make another attempt without an act of parliament signed in triplicate by the prime minster and sealed under a wax stamp kept locked in a castle dungeon and taken out only once a year on the winter solstace?

Now I suppose it will be next week before they try, because here we are at the weekend.

??? What? We're not talking about Wasteland 2 or BT:2004. Anyway, I"m running WL2 DC just fine on Linux.

Our complaint is that GOG is posting truncated installers for some reason, which they have done three times now. InXile does not create those installers, GOG does. This is GOG's failure. If they had gotten only a partial update from InXile, then the symptoms would be different. We don't have a valid installer installing a partial game, we have a truncated installer.

We're talking about inXile. You said, "inXile should pressure gog". You seem to think inXile cares about gog and/or Linux. I provide evidence that they do no really care past the release window, if that.

Wastalnd 2 DC works fine on my machine as well, after raising the file descriptor limit to insane levels to work around their broken file descriptor leak. A bug which has been known for a very long time with no fix or intention to fix.

Please go re-read the thread because you're not making any sense. Our complaint is about the Bard's Tale 4 Director's Cut installer that GOG created is bad. Literally nobody else in the thread besides you said anything about Wasteland 2. We're trying to get a good installer posted for BT4 DC, and InXile can't do that, because GOG creates them. However, InXile can talk to GOG. Hence my comment above. In fact, if you go check their forums, they are already raising the issue with GOG, so even your comment that "they don't care" is false.

The BT4 DC installer. Not Wasteland. Not BT2004. Not Steam/Wine BT1. Not whatever you're on about with file descriptors. >>Bard's Tale 4 DC installer.<<

Hi. In post #90 of this thread, you said, and I quote, again, even though I quoted in my original response:

I responded to this statement, and this statement alone. The fact that you think I'm responding to the thread as a whole just shows your woeful lack of reading comprehension.

I don't care any more, though. Think what you want. Don't bother replying, because I will ignore everything you write from now on.

Just checked - GOG installer wasn't yet updated, so I doubt they'll fix it this week already.

The more annoying thing is, that there is no one to talk in GOG about these issues. Support team says it's not their problem but "product" one. And support team is the only one we can reach. A convenient system for GOG to avoid having any discussion about it.

So ... what's wrong with that statement? That IS one thing they can do, and it is what they are doing.

I guess you're just trying to stir up arguments for some reason.
Agreed 100%. It is rather frustrating :(. I hope InXile will have better luck than we have, but who knows if GOG will even listen to them.

And yet the archive was reuploaded! Now as multipart zip.
Just download:

for (( count=2; count<11; count++ )); do lgogdownloader --download-file the_bards_tale_iv_directors_cut/en3installer"$count"; done

then:

cat the_bard_s_tale_iv_director_s_cut_4_20_1_153615_32362_linux.zip.00* > the_bard_s_tale_iv.zip

then unzip and get the_bard_s_tale_iv_director_s_cut_4_20_1_153615_32362.sh

While on principal level you are basically correct, the final installer-binaries **are** "developed" at GOG, as they have their own tools and requirements (mostly due to galaxy), so they repack everything themselves. And then they can't even upload complete file (I would really love to know what's behind that, maybe even some trivial firewall/antivirus/proxy-cache/timeout thing configured too strictly for ~40GB upload... hard to believe it's some impatient human closing the upload too early, although that's also an option :D ).

GOG receives from developers raw files (as-if-after-install) and they build their own diff-update packages for incremental updates by Galaxy client (not much info know about this step). And couple of years back they started to use these for another tool which rebuilds full installers, to avoid that process being done manually. And the shell-script installer build by this tool seems correct so far, so this part of their pipeline works ok. But then they are unable to upload the whole .sh file to their CDN servers, for whatever reason the upload is truncated.

BTW, if you think some folks here can't tell from the observable symptoms how things are processed and what's the competence level of involved parties... you would be surprised how much can seasoned developer guess from very little info. That's what ordinary users train us at... "it doesn't work" is my favourite bug report... :D

Or it may be like in that joke... where native American is lying at high-road with ear on the ground and curious driver spots him, brakes, leans to him and the guy whispers "red corvette, model C7, michelin tires" .... driver: "that's amazing, you can tell that all just by listening to the ground?" ... "no, he drove over me..."

EDIT:
.. so I downloaded it with simple:`lgogdownloader --download --game the_bards_tale_iv_directors_cut --create-xml=automatic --platform l,w`
and unzipped with `7z x the_bard_s_tale_iv_director_s_cut_4_20_1_153615_32362_linux.zip.001`
... said "ok" and I got 35GB shellscript out of it, it's actually almost -4G compared to first package, nice optimization.

Hmm... saved games seem to be in ~/.config/Epic/BardsTale4DC/Saved/SaveGames/ ... so I can like uninstall the old and install the new? Let's try it (in worst case I will lose only about 13h of game progress.. :D ... who cares...)

ok, uninstall did work well (keeping files unknown to him, like pdf with manual I copied manually there ...)
... now installing... seems like everything is OK so far....

(the videos are of course still jpeg files, but that's no surprise considering the time frames, I'm actually already shocked a bit they managed to shave those 4G off... even if they did just delete h264 files like me... ah, they did not delete them?! so it's real hard work on optimizing the actual game resources, seems to me... nice! ... (adding here things over time as the installer runs, if you are wondering why I am writing it like this) ... ok, posting it before it will finish install, but unless I edit here part2 with moaning in an hour, everything went ok and game was playable)

EDIT2:
Yup, so far works, loads save games from previous version well, overall feels lot more nimble, especially after load (I'm running it on Intel GPU, so everything off/low and it still did need about 5-20s after load to start moving (after rendering first frame), with new patch it doesn't choke that hard (visually seems same on the off+low settings :) ). (yeah, I know, it's super ugly with the lighting blinking everywhere just when you turn around, but I'm having fun with the game, I don't care about graphics that much).

I still don't get it. Why are they even messing with zips, yet alone multipart ones? Something is seriously amiss with their toolchain.

You also don't need to cat, if you use 7z on the first volume. It understands it's multipart.

Incorrect so far as the problem we've seen is concerned. GOG creates their installers, not InXile. Those installers are custom to GOG and created by GOG. This fact is confirmed by GOG itself. There's little InXile can do to fix this besides contact GOG as a developer, which has more weight than us doing it as customers. Also, the Linux version on steam did not have this problem, because it did not use GOG's custom installer. Also, the zip file itself was truncated, rather than being a complete zip file of incomplete contents, as your theory would have resulted in. This problem was not InXile's doing.

But good news! InXile did contact GOG about it, and GOG has fixed the problem now. Yay! Thanks to both InXile for raising it with GOG, and GOG for having someone fix over the weekend.