Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Latest Comments by F.Ultra
Valve to begin moderating game forums on Steam next week
21 Sep 2018 at 7:39 pm UTC Likes: 1

Quoting: DrMcCoyValve is actually paying people to moderate things? Well, there's a first for everything, I guess.

Here's hoping they do it right, but I won't be holding my breath.

Quoting: 0aTTThe game was, of course, immediately banned in Germany
Nope, the game isn't banned in Germany. In fact, Germany (and many places in Europe) is way laxer than the US in terms of nudity and sexuality. The US is kind of...prude.

These games are perfectly fine and not-banned in Germany. They are, however, age-restricted. And there's the rub: it's just that the Steam age gate is, well, useless and not up to the German standards. Regulations in Germany require Valve to verify the age of buyers. Just saying "Yes, I'm 18" is not enough.

One way to do this for digital goods (for physical goods, our postal service offers age verification) would be, I guess, Postident [External Link], which is used for opening bank accounts, getting a mobile phone SIM, and things like that.
Yeah Germany is quite strict with their age limits. If a game or film is FSK18 then you have to prove without doubt that you are indeed 18 or over. Have had to mail in a picture of my drivers license on several occasions when ordering DVD:s from Germany and Holland back in the day when I was trying to get hold of some unrated films that where only released cut in my country due to how hostile our censor system was back in the 80:s.

The problem now is that even though we no longer have any censorship of films or games here in Sweden we are such a small market that distributors tend to group us together with the Germans and they sometimes want to get a FSK12 or 16 in order to wider the audience and thus releasing the same cut version also here.

Fun fact is that film censorship started in Germany 1906 due to police reacting to police officers being ridiculed in movies at the time. Here in Sweden it started in 1911 when a police officer (the police again) reacted with disgust on a movie where the kitchen aid was disrespectful to a landlord and woe if this kind of behaviour would get a foothold in the society as a whole... Thankfully the state censor-board got a CEO that had a secret plan to disband the whole thing, which she finally managed to do in 2011 but the last movie that was cut in any way was Casino back in 2009 (so much for the myth that Sweden is run by SJW:s).

Feral Interactive are teasing ANOTHER new Linux port
21 Sep 2018 at 7:22 pm UTC Likes: 4

Quoting: Patola
Quoting: jensAs far as I know they announce as soon as they are allowed to. You know what an NDA is?
I will tell you what it is not: it is no excuse from criticisms.
Then you should criticize the one forcing Feral to sign the NDA and not Feral who have no choice what so ever in the matter (other than not signing a NDA and thus not porting the game either).

Mesa 18.1.8 and Mesa 18.2.0 have been released, pushing Linux open source GPU drivers further
10 Sep 2018 at 6:54 pm UTC

Quoting: x_wing
Quoting: F.Ultra
Quoting: x_wing
Quoting: pete910Wonder if this will fix Dying light for non *butu users ?

And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?
I heard the same and also thinked that as I found out that the game wasn't working anymore when upgrading to Ubuntu 18.04. Nevertheless, I compiled my self Mesa drivers and made it work (last time I tested I used Mesa 18.02RC3). Not sure if it's glibc the problem, you can see others making it work here: https://www.reddit.com/r/linux_gaming/comments/901n3l/dying_light_crashing_to_desktop/ [External Link]

About getting the command that Steam runs before starting a game, just set as game start parameters: echo %command%

Worth mention: steam sets a lot of environment variables that let's the steamlib to start (from your user name to game information). You may want to create an script that prints the environment for you (I say this because I assume that you want to run from a terminal "without" steam in the middle, so you must create the env in order to make it work)

EDIT: Also I need to mention that if you want to simply preload glibc on your system, you will be forced to also preload the lib loader (you can find it on /lib/x86-linux-gnu/ld-X.XX.so). The problem with this idea is that older versions of glibc will probably not work with libs linked against a more modern version. This means that you'll be forced to add all your system dependencies linked against this old version. In others words: you may want to create a new libs hierarchy of your target system (maybe docker can help here) and use chroot in order to start using this new hierarchy (of course this is not trivial and will get you some headaches...).
Just don't understand how it could be a mesa problem since I had the same version (18.0.7) on 16.04 where it worked and in 18.04 when it didn't. Then of course those mesa:s could have been compiled differently (one was padoka and the other was Ubuntu stock) which could explain some of it but still...

Best would perhaps be to set up a vm to run DL (if there exists graphic drivers in VM:s these days that are powerfull enough to atleast make the game start) and then incremetnally try each version of glibc between the version from 16.04 up to where it breaks in order to see which patch (if the problem lies in glibc) that makes the game crash. Could be quite some time consuming task though since compiling glibc is probably not a small task.

Mesa 18.1.8 and Mesa 18.2.0 have been released, pushing Linux open source GPU drivers further
9 Sep 2018 at 1:08 pm UTC

Quoting: pete910
Quoting: F.Ultra
Quoting: x_wing
Quoting: pete910Wonder if this will fix Dying light for non *butu users ?

And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?
Arrrh that's right, damn!

Quoting: storma
Quoting: x_wing
Quoting: pete910Wonder if this will fix Dying light for non *butu users ?

And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
Just tried with the Arch testing packages.... No go.
I'll look into it a bit more, time permitting.
Looks like it is a glibc issue. :'(
Anyone that knows what kind of magic that Steam adds when running games? I've tried to rename "DyingLightGame" to "DyingLightGame.exe" and then created a small shell script named "DyingLightGame" that just did "./DyingLightGame.exe" as a preparation for doing glibc preload but the game refused to start even with such a basic script (it couldn't find the steam overlay I think it complained about) so it looks like Steam does more than just execute the binary.

Mesa 18.1.8 and Mesa 18.2.0 have been released, pushing Linux open source GPU drivers further
8 Sep 2018 at 4:15 pm UTC

Quoting: x_wing
Quoting: pete910Wonder if this will fix Dying light for non *butu users ?

And before anyone chimes in with " you just need to add..." They don't work!
DL wasn't working on Ubuntu 18.04 with Mesa 18.1, but using Mesa 18.2RC made it work (for me and many others, I think). So, try to test it and share your results.
I thought the problem with DL was with the new version of glibc?

A multi-vendor extension for transform feedback in Vulkan is being worked on to help DXVK and others
8 Sep 2018 at 4:11 pm UTC

Quoting: YoRHa-2B
Quoting: jensWhat I mean is, was it Valve that approached you first and had asked you to start DXVK? Or the other way around, did you started with DXVK for another reason and was it Valve that got interested in you/DXVK?
The latter, they first contacted me after that [External Link] happened. DXVK was ~four months old at that point.
Well, a big mega concrats, your work is one of the major milestones in the Linux gaming community. Not bad for such a new project :-)

Mesa now supports OpenGL 4.4 Compatibility Profile for radeonsi
25 Aug 2018 at 12:40 am UTC

Quoting: pete910
Quoting: F.Ultra
Quoting: pete910
Quoting: F.Ultra
Quoting: pete910
Quoting: ShmerlYep, it shows up in the OpenGL string now:

OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.25.0, 4.17.0-trunk-amd64, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel (git-2854c0f795)
OpenGL core profile shading language version string: 4.50
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.0-devel (git-2854c0f795)
OpenGL shading language version string: 4.40


Killing compat profile could have made sense if Khronos would have done it. But they didn't, and now it's proliferated in Nvidia blob, so some clueless developers use it despite many warnings not to, and you get results like Dying Light. There is no option for Mesa but to implement it.
Does Dying Light work for you ?
You can already make Dying Light run on stable mesa if you set the Launch Options in Steam to "MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%" the great thing with the new patches is that such workarounds will no longer be necessary.

edit: however reading the mesa-dev post it seams that this perhaps does fix some stability for Dying Light that the override did not. In that case this change is even better :)
As mentioned numerous times, that fix does not work for arch users or even non *buntu based distros. :(
Yeah I know but that should indicate that the problem on Arch is something else. I do hope that this is where I'm totally wrong so that things will start to work for you Arch-guys as well.
It's not just arch seems to be anything other than *ubuntu/debian but I agree hope its fixed soon too, I have already played through it once so not a major issue but it's a good co-op game.
Just upgraded to Ubuntu 18.04LTS from 16.04 and Dying Light crashes after the loading screen. So I guess that the rumours that I heard on Phoronix that this is somehow related to a new version of glibc might be true.

Valve officially confirm a new version of 'Steam Play' which includes a modified version of Wine
22 Aug 2018 at 8:59 pm UTC

Quoting: Shmerl
Quoting: dubigrasuWhat? Of course it matters! It matters to me anyway. I have a deep respect for Feral and I'm curious in which way this it affects them.
I mean it doesn't matter in the sense that it should provide positive outcome for Linux gaming either way. Feral might need to change something, and hopefully the right way. For one I hope they'll start releasing DRM-free games.
If I where Feral I would negotiate the license sooner than today and do a same day release by using the proton wrapper (for the games where Proton works) and then release the native port with full performance and support later. That way they will not loose sales with this change while still being able to produce a proper native port later.

Valve officially confirm a new version of 'Steam Play' which includes a modified version of Wine
22 Aug 2018 at 8:42 pm UTC Likes: 1

Quoting: silentprocyon
Quoting: Alm888So, in case Valve in fact gets somewhere with its small WINE trick…

How long will it take for Microsoft® to sue WINE and Valve® for copyright infringement regarding Windows™ API and unlicensed DirectX™ implementation?

After all, WINE was tolerated only as long as it was relatively useless. I dobt Microsoft® will allow someone to chew off some 20…30% of its market share with basically its own API.
This. In regard to Wine, that's been something at the back of my mind for a while. Since the Oracle vs Google case, a new precedent was set that APIs can be copyrighted. I think if this does start to make a significant dent in Windows marketshare, I doubt MS is just going to sit still. Even if MS doesn't go the "API copyright" route, nor pursue any other kind of legal action, I'm half expecting MS to launch a big FUD+shill campaign.

Here's some a links to the articles regarding Oracle vs Google...
https://arstechnica.com/tech-policy/2012/04/oracles-ip-war-against-google-finally-going-to-trial-whats-at-stake/ [External Link]
https://arstechnica.com/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-fair-use [External Link]
https://arstechnica.com/tech-policy/2016/05/round-2-of-oracle-v-google-is-an-unpredictable-trial-over-api-fair-use/ [External Link]
https://arstechnica.com/tech-policy/2017/02/oracle-refuses-to-accept-pro-google-fair-use-verdict-in-api-battle/ [External Link]

By the way, the case is still going... And this is why judge appointments from a President are something to be concerned about...
https://arstechnica.com/tech-policy/2018/03/googles-use-of-the-java-api-packages-was-not-fair-appeals-court-rules/ [External Link]

TL;DR... Outcome of Oracle feuding with Google is that APIs can now be copyrighted. It started with Oracle acquiring Sun, wanting to make lots of money from Java; not satisfied with just some money, they also attempted to launch their own smartphone venture that failed; after failing in the smartphone business, Oracle sought to make more money from Java by suing Google over the latter copying code from Java (which was not the case) and claimed they owned copyright of the APIs; Oracle had lost in court and appealed, then another court ruled in Oracle's favor over copyright, but ruled that Google's use is "fair use"; not happy with the "fair use" ruling and wanting $9 billion for copyright infringement, Oracle appealed again, battle is still going on in Federal court; might or might not reach Supreme Court.
It's a bit different, AFAIK the Oracle vs Google is about building software for Android using Googles tools and not Oracles and in doing so Google have to expose the Java API:s (aka include files if this where C/C++). Proton does not need to expose the API since the people who build the games build on Windows and not on Proton. Anyway I think that Valve have enough lawyers to determine the legality of this all by themselves.

The Communist Dogifesto, an open source first-person shooter has a big update
20 Aug 2018 at 7:32 pm UTC

Went to Steam since I'm far too rich to buy such a interesting game from itch.io but unfortunately there is currently a -50% offer there as well so I had to cave in an bought it.