Quoting: GuestOh, sorry, I wasn't clear enough: I simply meant that if the game was available without Steam, then for some users at least, "Proton" probably isn't available.

Ah, I see. Well I think the problems that stopped it from running in DX11 mode was fixed upstream in wine some versions back, so if we disregard performance and just go for "works out of the box" I think their own launcher does work in vanilla wine now. I might be wrong about that, though, as it might require wine-staging(?).

Totally with you on this mindset, though. Upstream is where all compatibility fixes that make things run should end up. Or at the very minimum in wine-staging as fast as possible. Having to resort to additional tweaks and patches from multiple places might be second nature to some of us, but certainly doesn't help the game devs or new users just looking to get their games running.

View this comment - View article - View full comments

Quoting: GuestIs Path of Exile only on Steam? Because otherwise I might nudge those talking about "Proton" that it would be better for it to run well under vanilla wine more than anything else (because that should be available from any distro package manager). I mean, it probably does (I don't play this game), just wanted to be more specific (it's a small detail perhaps, but in my view an important one).

Yes, it's on Steam! Won't show up in your library listing since it's free to play, but just search for it in the store, it's there. :)

It's a game running on DX9 and DX11, and for nearly all of us that means we're using DXVK and Esync to run it, both being enabled by default in Proton. I used to run it through their own launcher, but now it's working right out of the box in Proton, so I'm just going with that.

Still setting a few command line options to pre-cache things and collect garbage more often when running it though, since the micro stutter on linux is downright horrendous at times, and any little switch to improve it is a good one. This stutter comes from how DXVK handles shader compilation I understand, and unlike on Windows, DXVK has to wait for the shader to be compiled before doing anything else, so the stutter is worse here. We do have a cache, but until things are cached up - or right after a DXVK upgrade - you can get lagspikes that definitely will get your char killed. Which we all know sucks in PoE. Minus 10 percent XP. Yay. I think the stutter might be worse on AMD cards than NVIDIA, but don't quote me on that.

This is where the game running on Vulkan would probably be a life saver. Using a graphics API we have native support for would probably solve that "graphic APIs waiting in turn" stutter problem.

View this comment - View article - View full comments

Quoting: FatpugstudioHi guys, it's the dev here, i'm glad to see someone discussing about the game :)

Ah, Project X, i was 10 when it was released, beautiful graphics and fabulous music by mr Brimble had me enchanted. I still love that game. It will be available for Linux since it's made in Unity so no problems there. There's no fancy DX11 shaders, 16 channel audio surround and whatnot so everything should hopefully work properly.

Cheers!

Looking forward to it! :D

I was about 10 when I played R-Type on the C64, and later at about 15-16 Project X on the Amiga. Safe to say I love these kinds of games! Awesome to get a modern one for Linux!

View this comment - View article - View full comments

Kind of looks like a slightly stripped down version of the old Amiga game Project-X from Team17;
https://www.youtube.com/watch?v=Lvx9-I5qpy4 [External Link]

View this comment - View article - View full comments

Quoting: Alm888P.P.S. I know I'm also using a logic trick, basically "I personally do not care so every one else should not care" statement thinly veiled as a question. But it is no worse than "Many people care so you also should care" approach. :)

I think the reality here is neither. It would be better described as "there were a lot of people playing this game on linux, and THEY care".

The original statement was that nobody cares. While in fact, some do. Whether you care or not is ofc completely up to yourself. But those that care, exist. So they're not nobody.

View this comment - View article - View full comments

Quoting: GuestIf i recall well, we were at .59% last month. That would make a relative 20% increase in proportion.

Nah, you're counting the wrong way. If we were at .59 and went up to .71, the increase is relative to .59 as the 100% value, meaning this would be more correct: (.79 / .51) * 100 - 100

We're up 25.42%! :D

View this comment - View article - View full comments

Might work well with Steam Play and Proton, for those unwilling to wait. I'm currently running Walking Dead perfectly there, and aren't these games built on more or less the same engine? Or did I imagine that? :/

I'll personally be waiting until 2019, though. Never liked that "do a single episode, then wait" thing. Binge play ftw! :D

View this comment - View article - View full comments

Quoting: Comandante ÑoñardoIn my account, the 3.7-7 beta is not yet available.

Go into the menu and click "Check for Steam Client Updates..." to download the latest version. Then restart it.

View this comment - View article - View full comments

Quoting: bingus

Quoting: GoldpawThe Blizzard app is 32bit, so you need both the 32bit and 64bit versions of DXVK for it to work. The other thing you need to do is to set the env DXVK_FAKE_DX10_SUPPORT=1 in the launch string.)

Just an FYI - this is from the "read more about it here" link above:

The following environment variables, which sometimes need to be set in order to run a game, will no longer be available:

DXVK_FAKE_DX10_SUPPORT

I missed that one, my desire to help fellow gamers won over my desire to read on! ;)

Anyway, having read on I'm reading the option will be available in the new per game config settings:

# Return S_OK from IDXGIDevice::CheckInterfaceSupport when querying
# support for a Direct3D 10 COM interface. Some games require this
# in order to start up, others may break when this option is set.
# 
# Supported values: True, False
# 
# Enabled by default for:
# - World of Warcraft

# dxgi.fakeDx10Support = False
https://github.com/doitsujin/dxvk/wiki/Configuration [External Link]

So that's the difference from now. But we'll still be able to run both the Blizzard App and WoW this way! :)

Edit: And from what I understand this option will now be enabled by default, and we only need the config if we actually wish to disable it, yes...?

View this comment - View article - View full comments

Quoting: BS86I really hope that this might actually mean that we can use the Battle.net Launcher AND WoW without having to enable and disable DXVK in the wineprefix.

They both work actually, you just have to remember a few minor things:

The Blizzard app is 32bit, so you need both the 32bit and 64bit versions of DXVK for it to work. The other thing you need to do is to set the env DXVK_FAKE_DX10_SUPPORT=1 in the launch string. Because WoW uses some DX10 calls, but this little trick allows dxvk to use the equivalent dx11 calls instead, or something like that.

I run both the blizzard app and wow 8.0.1 with no problems with this. :)

View this comment - View article - View full comments