Quoting: strycoreThis is a vendor specific implementation of something that already exists and is not vendor specific. We have supported switching vulkan drivers with the VK_ICD_FILENAMES environment variable for months in Lutris so I don't really see what the big improvement is here.

Yep. In fact, you can use the same env var to switch to the closed source vulkan implementation as well. The only advantage I can see to this is that you can switch from one driver to another by just using a short name instead of a full path.

View this comment - View article - View full comments

Quoting: 3zekielI mean other OSes, at least ChromeOS and Android was their argument. I did not say their argument is good either. And if anything, issue is they did not say anything for years and then came and said "we support that and only that"

AFAIK, no other OS uses EGLStream (I'm sure Android doesn't at least). Nvidia presented EGLStream as a OS independent solution, but the reality is that it was designed with the sole purpose of adapting to their needs. If Nvidia would want to improve GBM they would sit down with other wayland devs and start discussing a new standard that also works for Mesa drivers.

The big problem here is that Nvidia doesn't want to do a step back or rework in their driver design.

View this comment - View article - View full comments

Quoting: 3zekielNvidia already has wayland support, using standard egl extenstions. Rest of the Linux world uses custom (GBM) extensions. Then it becomes a question on who is right or wrong in this story. Nvidia says everyone else uses eglstream, Linux world says yes, but GBM has been there for quite some time.

What do you mean by "everyone"? Nvidia is the only one that adopted EGLStreams, not to mention that they are the ones that created this "standard" that only they implement.

View this comment - View article - View full comments

Quoting: XenanthropyHas anyone figured out the steps for a solid fix (besides building lib32-mesa) Currently on Arch and still has issues with both overture and black plague.

Conveniently, Frictional has decided to delete their forums so I can't browse that thread to try to find a solution :cry:

I'm assuming the Angelscript fix is not applicable to Black Plague since the source code hasn't been released for it, but it does fix Overture, correct? I would do it but i'd need steps to fix that. I tried running the games through Proton on Steam but for some reason, fullscreen doesn't want to seem to work! The games themselves run fine, but the "fullscreen" window is halfway between my two monitors, a bit difficult to play like that!

Any solutions would be welcome~! (Would really be nice if Frictional had let us know they were shutting down the forums...)

Can you share your specs? The only issue you have is related to playing in fullscreen?

View this comment - View article - View full comments

Quoting: furaxhornyxI know ; still, it didn't work for me :sad:

Which game is giving you problems?

View this comment - View article - View full comments

Quoting: furaxhornyx

Quoting: CybolicAt this rate, doesn't Wine actually have better general Windows compatibilities now than Win7/8 did when they came out?

Not sure ; for me, the only (very few) games and application that were not compatible with win7 were using anti-copy software such as Starforce (which, unless I missed something, do not work under Wine either, since they rely on a special driver being installed).

Still, this does not remove Wine's merit to allow compatibility with so many games :wink:

Remember that you can use no CD patches for those cases. AFAIK, most Starforce games have one... or at least a patched disk imagen.

View this comment - View article - View full comments

Quoting: LinuxwarperThey can leverage Stadia doing the heavy work and offer Chromebooks that are elegant and slim with modest but capable GPU and CPU for a good price, that you can do work and gaming on. If games aren't made available for local play on Linux (even for Chromebooks), desktop Linux will suffer while Chromebooks will not. Because Google seems to want a streaming only future and probably will base their Chromebook business based on that.

Stadia real leverage are Android and Chromecast, Chromebooks are barely starting to gain traction (just see the numbers). Once again, the big win for a service like Stadia is the almost null requirement of Hardware power, installation/download time and mobility. Even if locally running a Stadia game on a common distro is possible (something that I really doubt), the advantages of the service are still there and there is nothing that any Linux distro or any other OS can do in order to affect them.

I truly believe that if running Stadia version of a game locally in any distro was possible (with the exception of multiplayer games), Google would not have any problem on allowing their users to download the game so they can use it offline as it would be very cool extra feature. So, with all this said, I completely disagree with your theory.

View this comment - View article - View full comments

Quoting: LinuxwarperStadia is Google's push for gaming. Google's main OS is ChromeOS, that powers Chromebooks. If Google decides to market Chromebooks as aggressively as they are marketing Stadia, who do you think it's detrimental for? Only Windows and Mac?

And how is this connected with your theory of the clause to not allow to use the Stadia work for a Linux release?

IMO, the fact that you have to buy a Chromebook in order to get ChromeOS shows that it is more a direct competitor to Windows/MacOS computers as one of the main problems of Linux distros is that they aren't widely preinstalled in the notebooks/desktop sold to the public.

View this comment - View article - View full comments

Quoting: slaapliedjeI firgot Rage 2 was even a thing!

Did they choose DX12 because they could use nifty things like Ray Tracing, and Vulkan wasn't ready? Game looks amazing with all the features on, for what its worth.

Impossible to know. This game started development a little before DX12 and Vulkan was a thing, not to mention RT. If I have to guess, RT and DLSS is there because of Nvidia wallet. I doubt that CDPR didn't have the option to use Vulkan instead of DX12 at the moment they decided for DX12.

My point here is: lets be realistic, that the game works on Linux it's not a priority nor a concern for CDPR.

View this comment - View article - View full comments

Quoting: orochi_kyoAt least they give chance AMD Linux users to play the game, better than a middle finger, and as Pierre said, CDPR gave the game prior release to Valve to adjust everything for Proton, that is a good sign they take LINUX into account, better than the other 90% of companies outthere, including EPIC or the same Google.

Sharing a beta key doesn't mean anything (which may also be related to letting Steam test if their overlay is working as expected). Looking at how GOG has been handling the Linux status for their galaxy client says much more than this, so you're definitely giving them a credit for nothing. The fact that their game uses DX12 proves that Linux was never an option and we suffer the consequences of that decision mainly in the game performance.

Sorry, but you're being delusional. If you really think that CDPR deserves any credit for the work that Valve did, then you must do the same with Bethesda as we also got day one support with Rage 2.

View this comment - View article - View full comments