Quoting: johndoeDid you guys tried the "modesetting" driver

Yes, because it's default [External Link].

View this comment - View article - View full comments

Quoting: Leopard

Quoting: m2mg2

Quoting: RussianNeuroMancer

Quoting: GuestThey've not been ignoring anything.

You forgot BayTrail/CherryTrail SoC drivers fiasco - as soon as management pull the plug for Atom series, almost all Intel's own Atom development efforts stopped, including Windows (no drivers updates since year 2016) and Linux drivers (left unusable; devboards was tested and supported, tablets and laptops - not). Only occasional GPU driver fixes left, and not as fast as one would expect [External Link]. Couple of years later BayTrail/CherryTrail devices gets usable, but only because external (and some internal [External Link] developers polished drivers in their own free time.

So, Intel do ignore hardware they intentionally left behind, and they ignore it on Linux too. And I not even talking about (drivers for) boards and IoT platforms they introduce, just to kill it year of two later.

On topic: BayTrail Vulkan drivers allow to play Talos Principle with Vulkan API and 20+ fps even on low-end laptop with Z3735F, which is kind of unexpected from unfinished experimental driver (BayTrail share GPU with Ivybridge). Running same game in OpenGL mode produce empty skybox with few objects, so seems like OpenGL implementation for BayTrail is more buggy than Vulkan implementation. It's will be interesting to see how DXVK would perform on such low-end devices.

There is an intel graphics driver bug that affects my laptop that has been there since fedora 27. I have to use the Fedora 26 kernel in Fedora 28 or my screen flickers constantly. I have had so many issues like this with intel graphics. They should just work, but whatever machine I'm working with almost always happens to be affected by some bug where the intel graphics driver doesn't work right. My laptop isn't even that old, it's a Latitude 5480.

By flicker , you mean tearing?

If it is , you can change your accel to UXA

https://wiki.archlinux.org/index.php/intel_graphics#SNA_issues [External Link]

I pretty sure he mean "flicker". I have same issue on HP EliteBook Folio G1 on anything newer than Linux 4.15. Workaround is disabling rc6, but this kills power management [External Link], which is unacceptable for laptop, disabling rc6 is impossible with newer kernels, so stuck with 4.15 for now. This bug, of course, was reported [External Link].

View this comment - View article - View full comments

Quoting: GuestThey've not been ignoring anything.

You forgot BayTrail/CherryTrail SoC drivers fiasco - as soon as management pull the plug for Atom series, almost all Intel's own Atom development efforts stopped, including Windows (no drivers updates since year 2016) and Linux drivers (left unusable; devboards was tested and supported, tablets and laptops - not). Only occasional GPU driver fixes left, and not as fast as one would expect [External Link]. Couple of years later BayTrail/CherryTrail devices gets usable, but only because external (and some internal [External Link] developers polished drivers in their own free time.

So, Intel do ignore hardware they intentionally left behind, and they ignore it on Linux too. And I not even talking about (drivers for) boards and IoT platforms they introduce, just to kill it year of two later.

On topic: BayTrail Vulkan drivers allow to play Talos Principle with Vulkan API and 20+ fps even on low-end laptop with Z3735F, which is kind of unexpected from unfinished experimental driver (BayTrail share GPU with Ivybridge). Running same game in OpenGL mode produce empty skybox with few objects, so seems like OpenGL implementation for BayTrail is more buggy than Vulkan implementation. It's will be interesting to see how DXVK would perform on such low-end devices.

View this comment - View article - View full comments

Instabuy

View this comment - View article - View full comments

Quoting: TheRiddickGame developers are still finding it easier to get more framerate with DX12 over vulkan. Not sure why but games that offer both next gen renderer options seem to show DX12 doing better... Not completely sure why that happens yet.

They won't offer anything. They just initialize D3D12 context and use D3D11 API calls inside it. D3D12 "support" in released games is marking gimmick.

View this comment - View article - View full comments

Is this native Unity build for Linux, or D3D11->OGL wrapper is running under the hood?

View this comment - View article - View full comments

What is current status of Linux build?

View this comment - View article - View full comments

Quoting: oldeschoolLooks likes this is happening a bunch of people have been requesting a Linux port of City of Brass; the developer finally replied with a link to the announcement of Steam Play.

I did what I can [External Link].

View this comment - View article - View full comments

Instabuy

View this comment - View article - View full comments

Quoting: GuestYou cannot expect game devs to be able to jump in and fix bugs in Unity. That is like expecting everyone who can drive a car to be a mechanic. It simply does not work that way. You also cant expect them to delay their major sales platform for the minor ones. It wont happen.

You are right. We seen same thing with Everspace, they delayed Linux release because of UE4 bugs. Yet somehow people praise Everspace developers and hate Garry. Why is that? Proper communication is the key.

If, for example, Linux ports of TW2 would be released in the same way (with proper message about initial quality of the port, under alpha/beta branch, etc.) there would be much less backlash. However, since there was no such communication, Linux gaming community had it's very own "Batman: Arkham Knight" moment.

Again, what is similar in all three cases? (Rust, TW2, Batman: Arkham Knight) Lack of proper communication about quality of the port. And it have nothing to do with engine bugs, port bugs, game bugs and especially - it have nothing to do with community. Lack of proper communication is only publisher/developer fault.

View this comment - View article - View full comments