Quoting: slaapliedjeI wouldn't think SDL is a wrapper. Isn't SDL basically DirectX for non-Windows platforms? (at least that's how I always viewed it. Just an API with a stack for input, graphical output, etc). Just like DirectX.

By definition it is a wrapper. And the difference with DirectX is that SDL is actually using DirectX underneath (if required).

Quoting: slaapliedjeHa, the argument of native vs not is kind of like the argument between FPGA and Emulation. There is a difference to a point, but when you think of it all as 'x86 compatible code' then yeah it's all native in that respect.

I don't see an analogy in your example to be honest. The discussion here is that an ELF binary compiled and linked to run on Linux is, somehow, at the same level as PE binary compiled and linked to run on Windows.

View this comment - View article - View full comments

Quoting: ShmerlYou could use dxvk without Wine, yes. But it's still wrapping, not a fully native renderer. That's why Feral ones aren't really native either.

By native renderer I mean one that doesn't need translating DX abstractions into Vulkan ones (on whatever stage, at compile time, at runtime etc.).

So, from your definition if I develop something and use SDL as my graphic API I don't have a native game in any platform as I'm using a wrapper for all of them?

View this comment - View article - View full comments

Quoting: jarhead_hBecause it's always better to have more than you need than to need and not have. The 3090RTX is supposed to be a 350w card. According to LTT it can pull almost 500w and caused them noticeable problems on their test system because it only had an 850w PSU. Now do you think I trust AMD's power rating? Do you? If so, why would you do that?

Bare in mind that LTT tests were made with a CPU with a high power consumption as well (the GPU by itself went slightly over 450W peaks). So, a 850w may not be enough for such configuration because you don't have enough current in the 12v line for both components but this is an extreme configuration.

IMO, going very high in PSU wattage is not always the best for efficiency as your computer will probably by idling more than 50% of the time (or more than 90% if you keep it always on... like me) and you will probably get better efficiency with a certificated PSU that has a wattage more in line with your total system consumption.

View this comment - View article - View full comments

Quoting: GuestAsync reprojection is a hack to hide the lack of GPU power.

Well, the same can be said about DLSS.

View this comment - View article - View full comments

Quoting: GuestIf the driver breaks with a kernel update then one would assume that it's obvious that it is the kernel which breaks its own interface and not vice versa. The kernel doesn't provide any stable interface. Read about the latest breakage: https://lwn.net/Articles/827596/ [External Link]

We are definitely talking about different things then. AFAIK, Nvidia proprietary driver doesn't implement DRM api, so you are installing a piece of software that doesn't follow Linux design guidelines.

Regarding the problem you mentioned, the issue Nvidia has with each new release of the kernel is that some parts of the driver may get broken because the guts of the kernel may change from time to time, which means that if your driver is not mainlined you will have to take care of following and patching your driver in parallel to the kernel releases (there isn't any other way around). But still, mainlining your kernel driver doesn't mean in anyway that you cannot still provide your dkms driver for downloading and installing in older kernels (of course, the company in charge of the module will have to take care of adapting their code for older kernels if necessary). You can see an example of this with AMDGPU-PRO, where they include AMDGPU DRM as dkms for the kernel supported by Ubuntu LTS and Rhel versions.

View this comment - View article - View full comments

Quoting: GuestHaving the driver in the kernel is both a pro and a cons. With integrated driver modules you are forced to use the latest kernels which can introduce stability issues. If we rely on dkms then we don't need to live on bleeding-edge and we can get the latest drivers immediately but the linux kernel developers don't guarantee any compatibility from new kernels, only for their own driver modules.

From an outsider's perspective this sounds bad.

Not sure what you meant with this as any GPU company can follow DRM interface and deliver your driver through dkms. The problem here is that Nvidia approach completely avoids the guidelines Linux provides for graphic drivers, so if their module gets broken after a kernel update the guilt is a 100% on them.

View this comment - View article - View full comments

Quoting: GuestEvery product is different and the ideology is the least important difference between them. If you have failed to realize that then you should spend more time trying to understand the metrics we use to evaluate a GPU. Watch some reviews and interact with the community. Learn to carefully choose between PC components.

The review I only see is that Nvidia doesn't follow Linux standards with their drivers. This is not about ideology, is about doing things in the right way so the OS we use improves.

View this comment - View article - View full comments

Quoting: SamsaiPlot thickens. It crashed on Vulkan too, so I figured I'd throw my old R7 370 in and see how it fares. Seems crash free now, even when running it on the amdgpu driver instead of radeonsi. So now the worry shifts to whether or not the 580 is okay.

If your are willing to do an extra troubleshoot, run the game while reporting your temps (you can use MangoHud or simply a scripts that saves to a file the content of /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input). My 580 gets around 76°C while playing with my fans increasing their speed quite a bit.

View this comment - View article - View full comments

Quoting: SamsaiI don't think so, since the fans stay relatively quiet all the way until the GPU hangs and the fan speeds max out. I know that my first-gen Ryzen is a temperamental one, so my current working theory (that I'm desperately trying to disprove) is that my CPU is doing something that upsets the GPU driver. If that's the case then this will be an expensive fix.

hmmm, I find difficult that the CPU could be a factor (but who knows). Either way, remember that you can play the game using vulkan if you set "-force-vulkan" as game parameter. If with Vulkan your system stops crashing, that would probably put the full blame on Mesa.

View this comment - View article - View full comments

Quoting: SamsaiIt seems lovely, but sadly something about my setup is not dealing well with it and I'm ending up with random amdgpu hangs while playing. I don't know if it's my CPU acting up, Mesa issue or a kernel issue.

I played an hour without any issues. The only thing I noticed is that it puts at a 100% my GPU, so maybe your GPU temps could be a factor too.

Worth mention: I played it with Mesa 20.0.8 and 20.2.1

View this comment - View article - View full comments