Quoting: Comandante ÑoñardoI wonder when this will be integrated in Proton.

I don't think DX10 support with DXVK is good enough for integration right now, but who knows when it comes to Valve? They seem to be moving very fast with updates so far.

View this comment - View article - View full comments

Quoting: areamanplaysgameI love that this is happening.

A small gripe... it is (so far) not configurable. So when Dark Souls doesn't play the movies, I can't apply the fix I know from experience.

But my guess is with all the resources they've put into making DX11 and DX12 work, they're much more concerned with newer games going forward, which is a good thing.

You could open a bug on proton github and mention the fix.

View this comment - View article - View full comments

I'm glad valve are focusing more on making games recently. I hope they revisit their classics and produce worthy sequels. We are all looking forward to some day when we can play Half life 3, portal 3, left 4 dead 3... Lots of trilogies waiting to happen. I know some of you think they'll never live up to the hype.

But Valve don't need to rush any old rubbish out. They can and do take their time and get it right.

View this comment - View article - View full comments

Well. I always love Linux support. But Dying Light doesn't even work on my Arch distro. I get further into the game using DXVK.

View this comment - View article - View full comments

Fantastic. I can now play GTA V since the hang bug was fixed in mesa 18.1. Runs really well on my system, 60-120fps @ 1440p. I would love to provide apitraces for some non-functioning games I own. But I haven't had any success using that tool so far. :(

View this comment - View article - View full comments

It's been broken since they introduced the Xen updates, I tried it the other day and all I got was a black screen. So it's nice if they've actually fixed it in this beta. I might give it a test this weekend.

I've been holding out on playing the game from start to finish until they completed Xen. It's been a long wait, but finally looks like we are going to see the finished product :D.

View this comment - View article - View full comments

I don't know what the hold up is. They've had Vulkan support for nearly a year now and asked if Linux customers had any interest 13+ months ago. I believe over 1,000 people signed the steam thread. Granted that isn't a massive figure in the grand scheme, but it's the most active thread on the steam forum for that game.

My guess is they haven't really put any real work into it, maybe just tinkered with the idea while focusing on other stuff. But they're welcome to prove me wrong, release a port and I will buy it. Not getting a penny otherwise.

View this comment - View article - View full comments

Super impressed, I submitted a bug report about a graphics glitch on Diablo 3, but couldn't get an apitrace to help diagnose the problem and it's still be fixed. I was able to get good frame rates on gallium-nine, but it always felt a bit stuttery. With DXVK it's buttery smooth especially if I cap the framerate.

View this comment - View article - View full comments

Quoting: nox

Quoting: lejimster

Quoting: LeopardI can run Dying Light native without problems on Nvidia binary. If you are a Mesa user , you must force OGL version to 4.5 via launch options.

Quoting: nox

Quoting: lejimsterI've thought about trying this with Dying Light as I can't get the native Linux version to launch.

Hello fellow vega 56 user!
Just force the gl version:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%

:)

Thanks, but I guess I should have been more specific. It appears to be an Arch issue that only effects Mesa users. I think some other distros suffer the same problem. I tried for hours different work arounds, even following GloriousEggroll's snap package guide and it still wouldn't launch :'(.

Interesting. I had no issues on arch when I tried it a month or so ago. What exactly is the issue?

I get a black screen with white loading bar at the bottom, it fills up and then crashes out.

Log file always goes something like this..

{14:41:30.422} INFO: [INFO] > Caught signal 11 (Segmentation fault).
{14:41:30.426} INFO: [INFO] > /usr/lib/libc.so.6(+0x348e0) [0x7f6ce555a8e0]
{14:41:30.426} INFO: [INFO] | libengine.so(_ZN12CTextManager10InitializeEv+0x26f) [0x7f6ce6fc78ff]
{14:41:30.426} INFO: [INFO] | libengine.so(_Z13CreateTextMgrv+0x40) [0x7f6ce6fc7a50]
{14:41:30.426} INFO: [INFO] | libengine.so(_ZN9CRenderer13LoadResourcesEv+0x2c) [0x7f6ce6fb50bc]
{14:41:30.426} INFO: [INFO] | libengine.so(_ZN5CGame10InitializeEPciPvS1_jjP18IProgressIndicator+0x2370) [0x7f6ce6a8e5b0]
{14:41:30.426} INFO: [INFO] | /mnt/Data/Steam/SteamLibrary/steamapps/common/Dying Light/DyingLightGame(main+0xa45) [0x43e315]
{14:41:30.426} INFO: [INFO] | /usr/lib/libc.so.6(__libc_start_main+0xea) [0x7f6ce5546f4a]
{14:41:30.426} INFO: [INFO] | /mnt/Data/Steam/SteamLibrary/steamapps/common/Dying Light/DyingLightGame() [0x4425d9]

View this comment - View article - View full comments

Quoting: LeopardI can run Dying Light native without problems on Nvidia binary. If you are a Mesa user , you must force OGL version to 4.5 via launch options.

Quoting: nox

Quoting: lejimsterI've thought about trying this with Dying Light as I can't get the native Linux version to launch.

Hello fellow vega 56 user!
Just force the gl version:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%

:)

Thanks, but I guess I should have been more specific. It appears to be an Arch issue that only effects Mesa users. I think some other distros suffer the same problem. I tried for hours different work arounds, even following GloriousEggroll's snap package guide and it still wouldn't launch :'(.

View this comment - View article - View full comments