Quoting: ikey

Quoting: soulsourceThis does not solve any issues, just creates more. Using a Flatpak or Snap package is basically the same thing as the Steam Runtime (which by itself was a bad idea already...).
The ABI incompatibility with Mesa is a prime example of issues caused by such an approach, as it was actually an error on the side of the Steam Runtime, and if one would make the same mistake within a Flatpak/Snap package, one would see exactly the same issue.
If people would just rtfm [External Link]... It is clearly stated, that "The reverse (backwards compatibility) is not true. It is not possible to take program binaries linked with the latest version of a library binary in a release series (with additional symbols added), substitute in the initial release of the library binary, and remain link compatible."

It solves the issues specifically because it does away with the current problem we have of **mixed** runtimes, and instead provides a single consistent runtime with full ABI consistency, without being affected or influenced by host libraries. At that point Steam would be running in an environment specifically created to run Steam and the Steam games.

You're also looking at it from the wrong angle, we're not trying to put the older ones in, we're putting the **newer** ones in and ensuring they remain consistent. We then also have fine grained control over what can and cannot be vendored by games via LSI, and disable use of the binary runtime provided by Steam themselves.

Wait a second, you are saying, you ship a complete runtime inside the Snap, without a single dependency on the outside system? That then indeed solves the linking inconsistency, at the cost of size and possible security issues.

View this comment - View article - View full comments

This does not solve any issues, just creates more. Using a Flatpak or Snap package is basically the same thing as the Steam Runtime (which by itself was a bad idea already...).
The ABI incompatibility with Mesa is a prime example of issues caused by such an approach, as it was actually an error on the side of the Steam Runtime, and if one would make the same mistake within a Flatpak/Snap package, one would see exactly the same issue.
If people would just rtfm [External Link]... It is clearly stated, that "The reverse (backwards compatibility) is not true. It is not possible to take program binaries linked with the latest version of a library binary in a release series (with additional symbols added), substitute in the initial release of the library binary, and remain link compatible."

View this comment - View article - View full comments

Quoting: ArdjeI fear I only play ARK, which looks beautiful again since somebody found out how to fix the missing water asset.

I am waiting for the new fortresscraft release which should have an automation item I need to continue my game.

Funny: fortresscraft evolved and ark survival have always been my main time consumers. In both I play a world that I started in 2015.
In the mean time I did play saints row, but these 2 games demand creativity... building effort. I like that.

Would you be so nice as to elaborate? I haven't bought ARK (yet), as the ugly water was kind of a show stopper to me. Is the water fixed by a developer's patch, or does one have to fix stuff manually?

View this comment - View article - View full comments

Recently I've been playing Dominions 4 (after reading through the non-table part of the manual...) a lot, it's an awesome strategy game.
Of course I'm still playing Kerbal Space Program regularly, but as I'm now playing the Realistic Progression Zero mod, progress is a lot slower than with stock, and that lowers my motivation a bit.
This weekend I mostly played Tyranny. It was on my pile of shame for far too long. Now that I've finally started playing this game, I regret not doing so sooner. It's an interesting experience playing a character caught in the game's setting. Finally one of those games where one has to consider every dialogue option, and where it's often better not to ask certain questions, however tempting they may seem.

View this comment - View article - View full comments

Quoting: cprnI ride a motorcycle. :><: Hatred grows when I see arcade physics...

It's a spiritual successor to RoadRash, so it does make kind of sense that it has the same intentionally unrealistic physics and controls.

View this comment - View article - View full comments

It's released? I'll have to install this one again then. Last time I tried it (several months ago) it still had ugly garbage collector lag spikes. Hopefully the developers have meanwhile reduced heap allocations to get this issue under control.

View this comment - View article - View full comments

I can confirm that this game freezes the system if one tries to start it with AMD open source drivers when using llvm-4.0.1. An update to the just recently released llvm version 5.0.0 does fix this issue however.

View this comment - View article - View full comments

It's a nice remake. Yet, while I can't name any real reason, I still prefer the original DOS game (which btw. is available at GoG [External Link] and runs pretty well in DOSBox).

View this comment - View article - View full comments

Including Quadro/FireGL might actually be reasonable for laptop users. Laptop manufacturers tend to only sell regular GeForce or Radeon chips in their lowest quality, ultra-cheap models.
If one wants a somewhat acceptable build quality (think: sufficient cooling, so that the laptop case does not start to melt when gaming...), one is either stuck with integrated graphics, or one has to buy a device with a workstation graphics chip...

View this comment - View article - View full comments

Does the OpenGL core context usage relate to WINE's own Direct3D -> OpenGL translation layer, or does it apply to Windows applications using OpenGL (if the latter: how)?

View this comment - View article - View full comments