Quoting: ageresdoes it work only on Nvidia RTX cards?

Yes. It depends on an Nvidia-only Vulkan extension that has only been implemented (so far?) for the RTX series cards.

View this comment - View article - View full comments

Quoting: dubigrasuBoth versions are working for me with Mesa, but only GL mode. In Vulkan mode the benchmark also works, but the screen is filled with red artifacts.

To protect your privacy, external media requires approval to load.

Source: i.postimg.cc

View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

How did you download 1.1.0? I can't seem to find a link anywhere.

View this comment - View article - View full comments

Quoting: wolfyrionAt loading screens I am getting 1-9 FPS

Can't say anything about the rest, but this bit is normal. Games don't usually make many draw calls during load screens, they only do so to update the progress bar which happens even less frequently on an HDD.

View this comment - View article - View full comments

This is most excellent news! Steam says I've played this game for 34 hours so far, including the first episode of the season pass, so I was quite a bit worried they were leaving Linux behind. It's not even about the money - I've already gotten way more than my money's worth out of This War of Mine - I just don't want to miss out on the stories.

View this comment - View article - View full comments

I can understand why this will be an issue for some, since you will miss out on the discourse and hype surrounding the release of each episode.

Unfortunately for Feral, this is exactly the case for me. For the first game, a significant part of my enjoyment was community discussion, guesswork and speculation after each episode. I'm not willing to give that up for idelogical reasons.

Oh well, maybe I can gift it to someone after the Linux version is launched.

View this comment - View article - View full comments

Quoting: elmapulits not Thelio, its Thel.io , like in itch.io

That's simply not true, which you could have discovered yourself if you've visited the link you are talking about.

View this comment - View article - View full comments

Quoting: tuubiI don't follow your reasoning. Wine has a problem, so Wayland needs to fix it?

Wine doesn't have a problem, Wine works just fine. The problem was invented by DE people who think their compositors should prevent clients from positioning their own children. Naturally, Wine cannot solve a problem in a compositor's code.

Quoting: tuubiSince when is a Windows compatibility layer such an important concern that display server protocols should start accommodating its quirks?

Wine isn't a compatibility layer, it's the compatibility layer. When it comes to Linux adoption on the desktop it's one of the single most important pieces of software, ever.

Quoting: tuubiCan't speak about the DE folk, as I don't know what this would require of them. If it was mentioned in your IRC log, I'm sorry but it's too much of a wall of text to pore through.

What's required is for them to let windows position their own children. Not one DE developer managed to articulate why exactly that would be a security problem. And yes, that IRC log contains most of that discussion.

View this comment - View article - View full comments

Wayland wouldn't have gained this much traction

On the desktop? 90%+ of Wayland usage is on not-desktop, like car infotainment systems. On the desktop, anyone using Nvidia is by necessity on X11 which, according to this very website, is almost 70% of users. So if anything has traction on desktop, it's X.

clearly not required to implement crucial features if current Wayland-compatible toolkits make do without it and have not complained about this. [...] Of course it's understandable that Wine could use a more Windows-compatible feature set and their frustration isn't unfounded.

It doesn't matter one bit what "Wayland compatible toolkits" are doing. Wine runs Windows programs. That's its entire reason of existence. As long as Windows uses windows to implement menus and dropdowns, Wine needs to do that too. So the responsibility in fixing this lies not with Wine people, but with the protocol and DE folks who, as you can see, are not interested in solving it.

View this comment - View article - View full comments

but if you know where a window is positioned, you can scrape its contents or whatever.

These are completely orthogonal features. Saying "put this window over there" in no way implies "also give me its contents".

Furthermore, these are not arbitrary windows we are talking about - there is a parent/child relationship here and there are no security implications whatsoever in giving a parent window full control (yes including contents) over its children. After all, this is how all the other OSes work.

They probably think this is something that needs to be solved higher in the stack.

The "they" here are the people in the IRC log I've linked to and they are DE people, not Xorg. And it can't be solved higher up the stack than that because everything downstream of the compositor is restricted "for security".

View this comment - View article - View full comments

Quoting: tuubiI know it's inconvenient, but that "lol" is uncalled for. It's a bit over the top for most users, but not allowing access to other windows is a legit and actually rather obvious security measure.

This is not about "allowing access to other windows". The only concern here is whether a parent window should be able to dictate where a child window appears. Linux-with-X, Windows and macOS all seem to answer yes. So yeah, it's definitely a "lol" for Wayland.

View this comment - View article - View full comments