Quoting: salamanderrakeThe important question here is, do the boards have PCIe 4.0??? If its 3.0 it is barely forgivable, but if its still at 2.0 AMD is dead to me.

The CPU itself directly offers PCI Express 3.0 x16 (which is of course connected to according ports on the mainboards), and the more expansive boards have an additional PCI Express 2.0 controller in their northbridge.
(Source: http://www.tweaktown.com/news/56340/amd-ryzen-explained-motherboards-cpus-more/index.html [External Link] )

View this comment - View article - View full comments

Quoting: lejimster

Quoting: Leopard*snip*

It should work with Padoka and Oibaf I'm pretty sure. From what I read Padoka has Vulkan and bleeding edge stuff and Oibaf is more stable.

You won't find gallium-nine on official wine because they refuse to have it upstream.

I personally don't use Ubuntu/Mint, but I run on the latest mesa-git and wine-staging with gallium-nine support and its very good.

Have fun.

And I still don't get their reasoning behind refusing Gallium Nine for it being too vendor specific (AMD, nVidia), but supporting CUDA, which is even more vendor specific (only nVidia)...

View this comment - View article - View full comments

Quoting: barottoRight now Civ6 uses 1 thread. I have a 4 cores cpu, this means that only 1 core is being used. This also means that fans are not spinning and I can play in complete silence!
Yes, it's a bit jerky at times, but in a game like this I value the lack of noise much more than 60fps.

Civ 6 has a frame limiter, so you should be able to reduce system load also with proper multithreading.
Anyhow, if you consider your CPU fan noise disturbing, I'd recommend to buy a better cooler. They are not that expensive, and good ones are a real pleasure to the ear. My current CPU cooler is a Scythe Mugen 2, and while it is clearly audible at full system load, it's far from annoying.

Back on topic though: I'm really happy that Aspyr is working on multithreading the game, as, when comparing it to Windows, it becomes obvious, that on Linux Civ 6 is strongly CPU limited.

View this comment - View article - View full comments

Quoting: Luke_NukemBecause of Ubuntu being outdated most of the time, I kind of wish devs would target fedora stable releases as well / in replacement of.

What we users benefit most of is developers working on/supporting older/conservative distributions. Almost all libraries on Linux follow the rule of changing the soname [External Link] when they change their ABI [External Link] in an incompatible way. This of course does not mean that the libraries cannot get additional functionality with newer releases, as long as they don't break the old ABI by this. So, if one develops an application relying on newer functionality of a new version of a library, it will not run with older versions of the same lib. The other way around, developing the application with an older library version, and running it with a newer one (of the same soname), should always work, though. Problems only arise if applications ship their own libraries and do not read the documentation of said libraries (for instance Steam devs never read the libstdc++ ABI doc [External Link], otherwise they would not ship a copy of said lib together with Steam, causing breakage whenever the system-installed libstdc++ is newer than the useless Steam-supplied copy...), or if applications use an old, no longer supported ABI version of a library (for instance the old GTK 1, which is not shipped by distributions any more).

View this comment - View article - View full comments

Quoting: wolfyrion

Quoting: soulsource

Quoting: NoYzEIs there any good resource about what mesa actually is? I think i am using nvidia libgl, so is a new mesa version affecting me in any way or is it just for the amd folks?

Yep, the FAQ on the Mesa homepage [External Link], although that's slightly dated information. If you are using the nVidia proprietary drivers, Mesa is not relevant for you, as the proprietary nVidia driver ships a complete graphics stack, that basically replaces all open-source components.
For modern Intel hardware, there is basically one Linux driver, the OpenGL (and Vulkan, and OpenCL) component of which is part of Mesa. The same is true for the open source AMD driver (which also has parts in the llvm project, namely the shader compiler). The proprietary AMD driver replaces the OpenGL (and Vulkan, and OpenCL) driver of Mesa, but uses the open source AMDGPU Kernel module.

I think that all graphic card driver developers are affected by each MESA upgrade , NVIDIA , AMD , Intel etc in one way or another.
I will explain... for example NVIDIA Proprietary drivers.

Each upgrade of Mesa affects NVIDIA because it has to do with OpenGL,VULKAN, OPENCL and so on.
I beleive that all the graphic developers contribute to MESA and at the end they will use the open source code and integrate it into their own proprietary drivers.

Well maybe I am wrong though.. if someone can shed some light on this ..

The contributions of nVidia to the open source graphics stack are very limited, especially when it comes to dedicated GPUs. Actually they are even reluctant to publish signed firmware binaries, which are required by the nVidia open source drivers to achieve acceptable performance, in a timely manner (see for instance "Nouveau Developers Remain Frustrated By NVIDIA's Firmware Practices [External Link]" ). Other contributions like libglvnd [External Link] serve mostly the purpose of making the installation of the proprietary drivers easier. The only really noteworthy contribution to Mesa I am aware of was to improve Tegra support [External Link], so also hardly relevant for desktop users.

(must resist urge to post Linus' "nVidia, fuck you" video)

View this comment - View article - View full comments

Quoting: NoYzEIs there any good resource about what mesa actually is? I think i am using nvidia libgl, so is a new mesa version affecting me in any way or is it just for the amd folks?

Yep, the FAQ on the Mesa homepage [External Link], although that's slightly dated information. If you are using the nVidia proprietary drivers, Mesa is not relevant for you, as the proprietary nVidia driver ships a complete graphics stack, that basically replaces all open-source components.
For modern Intel hardware, there is basically one Linux driver, the OpenGL (and Vulkan, and OpenCL) component of which is part of Mesa. The same is true for the open source AMD driver (which also has parts in the llvm project, namely the shader compiler). The proprietary AMD driver replaces the OpenGL (and Vulkan, and OpenCL) driver of Mesa, but uses the open source AMDGPU Kernel module.

View this comment - View article - View full comments

Quoting: STiAT

Quoting: soulsourcewine-gaming-nine should work with all graphics drivers, but in order to enable the Gallium Nine feature, you'll need to run a Gallium3D driver (AMD or nVidia open source drivers).
Also, I'd suggest not to waste time with AMD GPU-Pro drivers, as they in general don't have better performance than the open source drivers (except for a few games, Deus Ex: MD being the only one that comes to my mind) and are (except for *buntu) a pain to install.

So you'd recommend me to go with the radeonsi driver when testing with the RX460? That should be pretty straight forward then ...

Yup. The numbers are slightly outdated, but Phoronix has some comparisons between AMD GPU-Pro and Mesa, showing that for some games the one is faster, for other games the other: AMDGPU-PRO 16.50 vs. Mesa 13.1-dev [External Link]
The main issue I have with AMD GPU-Pro is that it currently brings along a patched kernel, making installation less easy than it should be. If there is a well packaged version of it available for your distribution of choice, you can definitely try it, but if not, it depends on how much time you want to invest.
If you use OpenCL, installing AMD GPU-Pro is still the best choice, as the open source OpenCL support is in a rather bad shape, and getting the proprietary OpenCL libs of AMD working on the open source graphics drivers is, while possible, also quite a bit of work.

View this comment - View article - View full comments

wine-gaming-nine should work with all graphics drivers, but in order to enable the Gallium Nine feature, you'll need to run a Gallium3D driver (AMD or nVidia open source drivers).
Also, I'd suggest not to waste time with AMD GPU-Pro drivers, as they in general don't have better performance than the open source drivers (except for a few games, Deus Ex: MD being the only one that comes to my mind) and are (except for *buntu) a pain to install.

View this comment - View article - View full comments

Quoting: MaelraneI honestly don't know: does amdgpu (mesa! Not proprietary pro one) profit from this?

Just to clarify: AMDGPU is the kernel DRM driver used by GCN 1.2 cards, while radeonsi is the user space OpenGL driver (part of mesa) used by all GCN cards. (For GCN 1.1 and 1.0 the kernel DRM module is called radeon.)

View this comment - View article - View full comments

Ah, right. I didn't think about Steam, as I bought Divinity:OS at GoG.
For Steam you'll need to preserve the original LD_PRELOAD variable, as Steam also sets it (for the Steam Overlay, for instance).
I think the correct launch options should be:
allow_glsl_extension_directive_midshader=true LD_PRELOAD="divos-hack.so:$LD_PRELOAD" %command%
It might be necessary to give the full path to divos-hack.so in case Steam runs the program from a different folder.

Thanks for bringing this up, I'll edit my original post.

View this comment - View article - View full comments