Quoting: PhlebiacTiny Tina's Wonderlands looks like it could be fun, but I note with interest that all of the DLC is very negatively reviewed.

I have been a Borderlands ADDICT for 10+ years. If I go back to any of those games for one night, I get sucked to it again. Except for Tiny Tina's Wonderlands.

If you've never fallen into the Borderlands trap* before, Tiny Tina's Wonderlands might seem like fun, but if you're a Borderlands aficionado, it's garbage. They broke the whole (very successful) formula for a cash grab.

They don't want you playing that game 5 years later, so there's no "True Vault Hunter" mode (second playthrough, kind of like a newgame+) and once your characters are maxed out, there's really nothing more but grinding with tedious, bullet sponge enemies. So all that money and gear and silly magic spells you've collected are all for naught, your character is done.

Traversal sucks (you have to suffer an irritating, minigame board game type thing to get to different areas)

The DLC is just tedious grinding "encounters" and the loot you get from the "wheel of fate" for doing them is just repetitive. I ran through them all twice.

The writing is terrible too. Insultingly stupid. Tina isn't even funny in her echo recorder appearances. They re-used voice actors in corny, in-your-face ways, too, that made me more irritated than amused.

(* I use the word "trap" because the Borderlands games tweak the dopamine reward circuit in your brain. You have to kill enemies (and complete quests) to level up, so you can get better gear, so you can kill enemies better, so you can level up, so you can get better gear, so you can kill enemies better so you can level up... because more awesome rewards await at higher levels lol)

Getting it in a bundle cheap, it would be an enjoyable game at face value, when not butthurt like I am, though.

View this comment - View article - View full comments

Quoting: setzer22Yes, I know, I could also shut up but... You know which GPU brand doesn't require jumping through hoops and just works on Linux? :grin:

I don't shut up about things I dislike either, but in this case the hoops are the hybrid GPU switching, not so much a problem with a vendor. That's going to be a pain in the ass either way.

Here's an example of the hoops a person would jump through with AMD switchable graphics:
https://wiki.archlinux.org/title/PRIME [External Link]

View this comment - View article - View full comments

Daggerfall... that was the huge (unprecedented at the time) procedurally generated one, wasn't it?

I'm not sure I'd play it now (I still haven't gotten that far in OpenMW morrowind) but that would have been highly impressive in its day.

View this comment - View article - View full comments

My GoG installers would run too on an updated (but not newly created) prefix with the Wow64 build.

View this comment - View article - View full comments

Epic is a scourge, and anything I can do to deprive them of money is my pleasure. I've hated them since they lied to us repeatedly for years after the 2007 release of Unreal Tournament 3. When they were boxed in a corner, and couldn't lie anymore, then they finally admitted there was going to be no Linux client.

Then they made the Gears of War franchise XBox exclusive. They announced it late too, soon before release. I had been eagerly awaiting Gears of War 2.

Now they are engaging in unfair business practices to get publishers to use their store.

Also, any game company that takes the Epic exclusive carrot I'll wait until they are offered at desperation sale prices, if ever, before I'll buy anything from those companies. I caved for Tiny Tina's Wonderlands out of boredom (and love of the franchise, the way it used to be), but was I ever sorry I did. The game turned out to be a royal burn. So now I am completely resolved on this.

View this comment - View article - View full comments

what I think happened with Fallout 3 is something in the wine prefix got overwritten. The game did run, but it needed reinstalling. Fallout 3 has something "sneaky" because it used to be a Games for Windows Live game. They've defanged it with a fake dll but there's something that makes the game need installing (it can't just be dropped in by copying). It won't find content.

If I could have reinstalled it (GoG installers wouldn't run) it would have worked. I switched it to another wine (my Proton-TKG) and it reinstalled OK. Converting it back to my wine 8.6.1 didn't break it again. Weird.

There is no benefit for me to use this new Wine implementation at this time, and a lot of problems with 32 bit applications. My 8.6.1 built the normal way is 100% for everything I use it for. Pretty easy choice :-)

I really wanted this to work. I convinced myself that I was just going to work around all the problems, but this will just be the start of the problems I would likely encounter. (I thought it was great until I started uncovering them)

The only good thing about beating your head against the wall is that it feels good when you stop :-)

View this comment - View article - View full comments

Well, I have to say I've now seen that this isn't completely appropriate yet for 32 bit games. I'm going to have to go back to the old method, moreover, I'm just going to go back to my recently recompiled wine 8.6.1 before I go converting more wine prefixes to this. It's a shame, because I'm mostly OK.

In testing Fallout 3, it didn't run correctly. I could hear the background audio, but the launcher program drew no window. So I ran the Fallout3.exe directly, and found that it needed to be "installed". It's a game that has to be installed correctly or it doesn't find mods and dlc, only the base game.

'Twas then that I found out that a lot of 32 bit programs won't indeed run, including GoG installers! Even for 64 bit games, the installers are 32 bit.

wine client error:124: sendmsg: Bad file descriptor

I get the same with a newly generated ~/.wine prefix (not only in lutris)

But other important programs won't run either, like the 32 bit wine mono installers

009c:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\removeuserinstalls-x86.exe" in experimental wow64 mode
00a4:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\installinf-x86.exe" in experimental wow64 mode

So, right now, for me, prefixes that updated properly STILL have old files that work. Updating a prefix doesn't remove files, if another dll was there it will still be there etc.

Some 32 bit games were OK running after being given new prefixes because they didn't run afoul of anything that wouldn't run. Like Just Cause 2 and Bioshock Infinite, for example.

This will not do for my system wine, obviously.

View this comment - View article - View full comments

They have never enforced it on me, but in my general "TOS" (that I did indeed read after I signed up) it's something like 300 Gb/month (what's that, 3 games now? lol). Now, I haven't looked or cared to look for any updated TOS, but I've never been billed for bandwidth or had the ISP complain about my usage or behaviour in the decade or so that I've had them.

However... I have always considered bandwidth to be a resource that is mine to use, but is not mine to waste. I feel STUPID, and remorseful if I pointlessly download some 70 Gb game and remove it.

P.S. I really miss this game and I'm probably going to download it again sometime soon. Because this thread brought it in mind again :-)

View this comment - View article - View full comments

I uninstalled that a few months ago because of frequent, large updates to accommodate rip-off DLC content that I'm never going to buy (was not impressed with what I got from the first season pass and I'm not buying another). That was unexpected from that game company, and one of my favourite franchises. I bought everything for all those games and didn't feel burned like that.

When that happens, I regret it because I won't be inclined to free up space and download 100+ Gb any time soon. I do miss some parts of that game though but having to download 50+ Gb updates for no reason just to be able to hop in to play a mission was too onerous, was preventing me from playing it, and I could use the space on my NVME drive for something else.

Nice to see them putting in some effort for Linux though. I don't play multiplayer anything, and unchecked the box, so I wasn't affected by EAC problems, but this game worked for me right out of the box on launch day, with the Vulkan renderer. There were some quest bugs, reward unlock bugs etc. that got fixed (though some of that stuff took a long time). They broke it once with an update (failing on entry points in directx dlls, while probing early on launch regardless of renderer, if not certain Windows 10 patch level... affected Windows users too), and promptly fixed it in less than one day. They are good that way, at least.

View this comment - View article - View full comments

Oh bugger, here's a show stopper (for me, in Lutris). I can't seem to create new wine prefixes

Started initial process 1225 from /usr/bin/wine winecfg.exe
Start monitoring process.
fsync: up and running.
wine: '/storage3/shit/justcause2' is a 32-bit installation, it cannot support 64-bit applications.
Monitored process exited.

I actually updated that prefix OK and the game worked, but I decided to do a test of creating a new wine prefix for a 32 bit game. Good thing I did, because this will not do.

I then forced it to be a "64 bit architecture" (Lutris has a setting that is Auto by default) and got

wine: could not load kernel32.dll, status c0000135

This is all 64 bit wine binaries

It's got to be something related to Lutris hard coding paths or something, because I can do

rm -r /home/grogan/.wine
wine winecfg.exe (and get the progress dialog, and winecfg opens)
wine notepad.exe

Sigh... time to go poking the python.

P.S. Got it to work, to generate a prefix with the "64-bit" architecture setting in Lutris (still can't get "Auto" to work)

The 32 bit Just Cause 2 game works just great in this "64-bit" arch Wine prefix, so the thunking is working.

View this comment - View article - View full comments