Quoting: Guest

Quoting: Purple Library GuySo . . . to point out the simple and obvious, among all those sites the lowest figure is over 2%.
We have 2.2%, 3.8%, 5.6%, 3%. All in all, the 1% figure can maybe be put to bed.
So either there's something odd about Steam statistics, or Linux is used more for everything else but gaming.

Perhaps nobody is using wine where those 2-3% stats are collected. Wine is bad for us in every area. Thinking it gives us more games is a dangerous illusion. It gives us more devs and publishers who count us as customers without the need to actually make games for GNU/Linux.

When it comes to playing new games, sure. You're lucky if you're able to play a DirectX 11 game using wine, since the DirectX 11 implementation is not even close to being complete.

However, I have to disagree when it comes to older games. If it's obvious that a game will never be ported to Linux, then there's only one way to play it.

View this comment - View article - View full comments

Quoting: AryvandaarDoes it have turn based combat?

It has turn based combat. From what I can remember it is the real deal like in FF X, and not the semi turnbased system like it's in FF VIII / FF IX (atleast I think fans refer to those as turnbased games).

View this comment - View article - View full comments

If using Vulkan means it will be faster, then I don't mind. Lower system requirements is a good thing. If that is the case, they should use Vulkan for both windows and Linux, since Dx 12 is windows 10 only (I think some people still use Windows 7/8).

View this comment - View article - View full comments

Quoting: SeegrasYes, but does it run Fallout 4? ;)

Of course not, there is no DirectX 11 support yet.

Quoting: drmothCan't wait for the command stream stuff to be finalised. Great work WINE team...such an amazing project, and they've come so far.

If you want Direct3D command stream, aka csmt, it's available in wine-staging [External Link].

View this comment - View article - View full comments

Quoting: kon14This new update seems to be featuring some extra work towards wayland support. Perhaps they'll like it better this time.

They are still using EGLStreams, etc, so nothing has changed at all. So for now, if you want to use nvidia with wayland, the only option is to use the nouveau driver.

View this comment - View article - View full comments

Quoting: MblackwellDo we know if they have Vidal Sassoon, er TressFX on this one?
The Mac version did not, however it would be a fun addition here particularly with having newer available GL versions.

There is a trailer on youtube:

View video on youtube.com

Why it's called "Tomb Raider for Mac and Linux – Coming Soon trailer" doesn't really make sense, since there's already a Mac port.
*If* this is what it looks like on *both* Mac and Linux, then there's no TressFX support.

View this comment - View article - View full comments

Quoting: TheRiddickYou can also look at the results here:
Phoronix AMD/NVIDIA comparison (recent) [External Link]
I think you are overall wrong, AMD is having major issues keeping up in synthetic benchmarks also!

That's like saying all games and software under Linux are actually using OpenGL wrongly because AMD gets bad performance and NVIDIA doesn't.. so therefore AMD shouldn't really be trying to keep up with OGL performance...

Of course performance is important, and drivers must be optimized.

This was not supposed to be about performance, but whether something works or not. There should be no need for a driver workaround, the code should just work (and that is obviously not always the case, especially for non-nvidia gpus).

You mentioned earlier that games would crash, and that is a major problem, and why I wrote something in the first place. From the same forum thread (I guess I should have used this one instead):

First off, NVidia's driver not being especially faithful to the spec is a fact, but nobody said that's why it was faster. It's just why things tend to break on other drivers.

If a game only works with nvidia gpus, then It looks like the developer couldn't care less about other gpus. They should *always* write opengl compliant code, and then there would be no need for driver hacks.d

View this comment - View article - View full comments

Quoting: TheRiddickI wasn't referring to COH2, but in general. SOME things work, most don't. I really don't care if there is a error n AMD's code, that's not my fault.

And while you pick at NVIDIA, they have a working driver that delivers 200-300% more performance over AMD, so I'll take dishonest code over broken and terrible code any day!

I guess you didn't read anything at all, seems like you only read the title.

Example from that page (there's more on that page and others about opengl in general):

I know this has already been said, but the facts are that nVidia, OpenGL implementation on linux is not exactly conformant to the standards. We all know this, we've known it for years. Add in the fact that so many dumbasses only test on nVidia hardware and there's part of the problem. Even though nVidia's driver is not standards compliant, it's not the fault really. It's game devs relying on that behavior that is the real problem. Too many companies and projects know that behavior they rely on is not standards conformant and they do it anyways, so it's their own damn fault.

The broken / terrible code is the actual code that software developers write. Writing code that works with nvidia, and then maybe do a little testing with the other drivers is bad practice. They should also make sure that the code is opengl compliant in the first place.

With vulkan that will hopefully / probably not be a problem anymore.

View this comment - View article - View full comments

[

Quoting: TheRiddickProvided you stay away from AMD cards, then gaming under Linux is looking VERY good and prosperous.

(I have a 390x and tried ALL driver versions including experimental and its like ripping your eye balls out, crashes all over, then when it works you will end up with only %40-50 of the performance NVIDIA gets for similar/slower cards)

PS. My 390x is in the shop atm under RMA, yep AMD cards melt!

You should really check out this page [External Link] from the forums at phoronix. The nvidia driver isn't faitful to the specs, and code that works with the nvidia driver doesn't necessarily work with the amd driver. So the reason why it crashes can be the result of bad code.

The driver driver should not accept apps which use combinations of API calls and/or shader code which do not comply with the OpenGL spec. One example on that page is Unigine's engine.

View this comment - View article - View full comments

[quote=rkfg]I've become curious about one thing: if Vulkan provides such a low level access to hardware, what will happen if an app (a game usually) starts to misbehave? I read Vulkan has very little validation in favor of speed. Does that mean that a buggy game could crash the entire Xorg or freeze the driver? A user-space segfault usually leads to crashing the program but not the entire system (and Xorg/desktop for many people is the system), but if invalid data goes into the kernel space or the Xorg driver and crashes there because of that... I suppose it would be bad. Kernel panic for the module and Xorg crash in case of the Xorg driver.[/quote][s]A buggy OpenGL game can freeze your system...

Added this comment way too late in the thread. Doesn't seem like I can delete a comment I made, or am I wrong?

View this comment - View article - View full comments