Really fun!

View this comment - View article - View full comments

Like this: https://gpuopen.com/gaming-product/radeon-gpu-profiler-rgp/ [External Link] or this https://github.com/GPUOpen-Tools/CodeXL [External Link]

But with all the marketing that Nvidia likes to add.

View this comment - View article - View full comments

Quoting: TheRiddick

Quoting: x_wingBased on Phoronix results, seems that there is some test bias with OGL. Vulkan 4k-High results show more or less the expected classification on Linux.

https://www.phoronix.com/scan.php?page=article&item=basemark-12-linux&num=3 [External Link]

The 2060 Flogs ALL AMD cards under vulkan. I don't think that is correct either sorry. The Radeon 7 for example should be getting close to 1080TI if not better.

Results look a tiny bit better at higher resolutions sure but AMD shouldn't be doing this badly at lower resolutions.

Vulkan 4k-High:


Is more or less what Phoronix avg test always shows (even for OGL).

The difference in other res may be related to CPU bottlenecks in the OSS drivers.

View this comment - View article - View full comments

Quoting: TheRiddickInitial results MAY show it heavily favors NVIDIA GPU's as AMD's cards ALL perform under 2060 levels. Nobody has done testing under windows yet to verify if its unique issue to Linux AMD drivers or not...

In their web page you can see other results: https://powerboard.basemark.com/top/gpu-families/basemark-gpu-1.2-high/computers/default-os/vulkan-1.0/avg/100/1 [External Link]

Based on Phoronix results, seems that there is some test bias with OGL. Vulkan 4k-High results show more or less the expected classification on Linux.

Here are my results for high settings using the latest Mesa versions (or at least the latest I have compiled :P):


From top to down:
Mesa 19.2.8 with LLVM 9.0.0
Mesa 20.0.0 with LLVM 9.0.0
Mesa 20.0.0 with ACO
Mesa 19.3.4 with LLVM 9.0.0
Mesa 19.3.4 with ACO

I also have Mesa 19.1.2 but Vulkan results are invalid (there is a rendering issue that generates a better score).

View this comment - View article - View full comments

Quoting: ShmerlMy question was about games developed by studios that Google now owns, so that decision is up to Stadia after all (or Google if you prefer).

Well, in that case I think that the answer is pretty obvious. Still, even Microsoft end up publishing his main xbox exclusive game on Steam so everything is possible (but not probable in the short end).

View this comment - View article - View full comments

Quoting: ShmerlWill they release their games for normal desktop Linux too, or they'll remain Stadia exclusive? In general, exclusivity is a bad thing.

But such release is all up to Stadia? I mean, Stadia stands for the infrastructure required to run the game on the cloud. This means that Stadia is working like a platform by itself in the same way as PS4, XBOX, Switch or Windows does. So, I think that this requirement you mention is more on the publishers decision that something that Stadia can/must deal with.

Still, it would be nice to get the game "as is" on Stadia server in order to take a look on what are the tech requirements for them... which probably will also make them useless for any desktop distro.

View this comment - View article - View full comments

Quoting: celphyYeah. That's why I said I'm torn on that.
I'll propably buy it if it works well enough.
Most versions still seem to have technical difficulties though.

Well, since they announced that Exodus will come to Linux I decided to start playing Metro series (always had them on my library but never made the time to get into them... shame on me) and I have to say that redux is a very solid port. Outside of some very rare crashes (probably I got 3 in 25 hs of game play of 2033 and last light) it works flawlessly with Mesa drivers. So I'm confident that we will get a well polished version :D

View this comment - View article - View full comments

Finally! I always wondered of the state of this project. I remember that the devs gave us some extra details of technology & dev process they were working (own engine and using linux as dev platform <3). Wishlisting!

View this comment - View article - View full comments

Quoting: GuestYeah, this solved the problem. Weird, this issue has been around for a long time, why Unity hasn't fixed this yet? Is it not reported?

The bug is reported here: https://gitlab.freedesktop.org/mesa/mesa/issues/1345 [External Link]

DCC stands for "Delta Color Compression", which is a method that allows the driver to compress data in a lossless way in order to save memory bandwidth (if I understand correctly, it is something similar to the macro block compression strategy on video codecs). Based on what the gpuopen dcc overview [External Link] says and answer that I got from a dev (here [External Link] ) my theory is that the issue may not be in the driver but in how the shader flags the textures affected by compression.

Either way, as disabling dcc doesn't affect the image quality and doesn't have a big performance impact I think that this bug doesn't have a big priority. It would be nice to add this workaround to drirc though.

View this comment - View article - View full comments

Quoting: GuestNow that MESA is complete let's hope they have more time to fix some annoying niche bugs, like for example the ambient occlusion bug in Two Point Hospital (and Parkitekt i think?).

Add AMD_DEBUG=nodcc as game arg (i.e. AMD_DEBUG=nodcc %command%) and AO will work as expected. The problem seems to be related to Unity implementation of AO, so it may not be a radeonsi issue.

View this comment - View article - View full comments