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?

View this comment - View article - View full comments

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 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 :-)

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

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/
https://arstechnica.com/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-fair-use
https://arstechnica.com/tech-policy/2016/05/round-2-of-oracle-v-google-is-an-unpredictable-trial-over-api-fair-use/
https://arstechnica.com/tech-policy/2017/02/oracle-refuses-to-accept-pro-google-fair-use-verdict-in-api-battle/

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/


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.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments

Quoting: syxbitArt makes me think of sunset riders. Man I wish they did an HD remake of that.

And Shank!

View this comment - View article - View full comments

Wow, impressive. So they have written their own Sega Genesis emulator as well while being able to add achievements from the rom. Instabought this one.

View this comment - View article - View full comments

Yet again I don't understand why some devs don't code cross platform from the start and test on every platform, it's a good way to catch bugs and problems that you never knew you had which in the end leads to a more stable product on all platforms.

View this comment - View article - View full comments

Quoting: x_wing

Quoting: F.UltraAccording to https://lists.freedesktop.org/archives/mesa-dev/2017-June/160362.html the GLSL specs (where this is happening) says that "derivatives are undefined after non-uniform discard" so you could argue that this use is forbidden (if you act like a GCC developer) or that it's a grey area.

I'm a complete ignorant about OpenGL nor graphics APIs, but how hard would be to specify an OGL extension to address this issue? Is Khronos group a problem to create such extension?

From my point of view, Mesa will not accept to change anything if they don't get some clarification from the standard and I remember that Malek mention this as a possible solution (if I didn't get him wrong).

I don't know either. Anyway there exists now a drirc setting so if any game continues to use this use-after-free functionality they can always be added to drirc for the workaround.

View this comment - View article - View full comments