Quoting: BelvarI think it would be worth noting in the article that it is the publisher, Bigben interactive, and not the developer that has stated the game would not come to GNU/Linux. They are also responsible for the game being on Steam only and being shipped with Denuvo (see the statement on gloomywood website).
I think Bigben is the one to blame in this case, Gloomywood was looking for a publisher after succeeding their crowdfunding campaign (you can argue that it is unethical, but a lot of indie studios do that) and the one that got their interested was clearly a shitty one.

You can blame Bigben for being DRM crooks, but developers willingly partnered with them, breaking their crowdfunding promises. For that, developers bear full responsibility, and they can't shift this blame to the publisher. They should have looked for proper partners, instead of crooks.

View this comment - View article - View full comments

Quoting: emphyCompare this to how obsidian treated their backers when signing a publisher deal: Pillars of eternity got released on gog fine despite paradox entertainment refusing to publish there nowadays.

Paradox released Tyranny on GOG, which was developed by Obsidian without crowdfunding (i.e. it's owned by Paradox). I think their main problem is in their own studio (Paradox have a studio, in addition to being a publisher, which mostly makes strategy games). Their studio is very Steam oriented, and outright refuses to consider those who don't use Steam.

View this comment - View article - View full comments

Denuvo DRM for a crowdfunded game? What a shame. Backers should require refunds.

From their campaign page:

Which DRM will be used for 2Dark?

2Dark will be distributed through Steam, but also on other platforms (GOG, Desura, etc.) which don't use DRM. Which means the version you get won't have DRM...

Liars. I'm not surprised about broken Linux promises.

View this comment - View article - View full comments

Why is contractor work called "consulting"

And while it's good they are trying to improve things under X, it only highlights that it's time to push Wayland forward instead of lagging behind.

View this comment - View article - View full comments

Regarding Mesa. Did anyone manage to run Trine 3 on radeonsi recently? It hangs / doesn't work for me. I wonder if it's my setup, or Mesa issue. If the later, I'll report it to their bug tracker.

Quoting: RussianNeuroMancer

Quoting: AnxiousInfusionMesa got over the major hurdles of reaching OGL 4.5 compliance finally.

Only for GCN and latest Intels, unfortunately.

Which is OK, at least for demanding games. You don't want to use anything older. Mesa developers obviously prioritize recent hardware, since each driver needs additional work.

View this comment - View article - View full comments

Is it available without Steam?

View this comment - View article - View full comments

I wouldn't limit using newest Mesa to single vendor. Wine for example uses OpenGL 4.5 for DX11 support, and it simply won't work without it. So you have clear advantage in using newer Mesa for it.

View this comment - View article - View full comments

Quoting: dmantioneTo make Bioshock Infinite launch on Mesa 13.0.3 I need these Steam launch options:

MESA_GLSL_VERSION_OVERRIDE=410 MESA_GL_VERSION_OVERRIDE=4.5 %command%

Perhaps on different hardware this isn't needed, Mesa returns different version numbers on different hardware.

What do you expect, that version of Mesa wasn't fully ready for OpenGL 4.5 on AMD (radeonsi). All your complaints seem to ignore, that Mesa is actively developed. I'm not sure what problem you have with that. Looks like you are in a rush, and expect Mesa to move faster than it does. I think it already moves pretty fast.

Regardless, current stable version of Mesa is 17.0.1, so you should be using at least that for gaming.

View this comment - View article - View full comments

Quoting: dmantioneWhat makes the discussion difficult is that we have little concrete information to confirm this (sorry to say again, Feral never elaborate) and then we have to base ourselves on statistics, with other games, and those statistics unfortunately do not confirm that demanding games.

Well, some developers explicitly list extensions that are required for the game to work. Look in the readme file in Shadow Warrior for example. If Feral would do that, it would simplify things for users, and they can adjust their expectations.

So I agree here. Feral should elaborate what they require, and what they think doesn't work with certain drivers.

View this comment - View article - View full comments

Quoting: dmantione

More and more of their games directly support Mesa as Mesa has continued to mature. This will likely be a thing of the past in a year or so as Mesa will be in fantastic shape by then.

I sincerely hope so and I do expect things will be better, but there also is risk of a scenario that games and other games will continue to demand the maximum from drivers (because with Mesa, multiple games still don't run out of the box) and that we will be compiling and patching source code for many years to come.

This doesn't make sense really. Need to compile Mesa arises only if some feature is so recent, that it wasn't released in the stable Mesa yet. Since Mesa gained OpenGL 4.5 support last year, that was fairly common case, but it's not going to happen all the time. Besides a few non versioned OpenGL extensions, Mesa already implements OpenGL 4.5 proper. So further work will go into optimizations.

Vulkan can be in such situation though, until radv will reach completeness. But again, after rapid development, usually features aren't added so often. Therefore there is no point to complain. Either compile from source in such case, or wait for Mesa to catch up. I don't think Feral should be blamed for anything like that. On the contrary, their contribution to Mesa should be welcomed. And if they consider pro driver broken - so be it. Users should be switching to Mesa anyway (the only place where PRO is now useful for non legacy stuff is full Vulkan support).

View this comment - View article - View full comments