Quoting: rstrubeOne thing worth mentioning is that I'm using a Nvidia GTX 1060 with driver 390.48. Are there some additional environment variables that I need to set?

Nvidia introduced a new SPIR-V compiler recently, may be it's affecting it? Try disabling it with:

__GL_NextGenCompiler=0

Quoting: rstrubeMan I can't wait to move to Vega, I've had it with this binary driver bullshit...

I got Vega 56 recently (Sapphire Pulse) and it's a good card, but prices on it jump like crazy. Wait for a chance when it's at some normal level and buy quickly :)

[quote=YoRHa-2B]

Quoting: Shmerl

Quoting: ajgpI do wonder how Feral works around stream output limitations in their ports; because Im sure some of the games they have ported with Vulkan must use that DX feature

Rise of the Tomb Raider doesn't. Not sure about F1 2017 and the earlier Vulkan ports, but it's certainly possible that they just never ran into this issue in the first place.

If the game doesn't care about the ordering guarantees that D3D11 Stream Output provides, a rather efficient workaround is trivial: Just use SSBO writes and an atomic counter. Done.

If the game does care about the ordering guarantees, things get hairy. If the game doesn't use indirect draws and if the geometry shaders unconditionally write data to their output streams and if the game doesn't rely on overflow behaviour, you can still use SSBO stores combined with some gl_PrimitiveID and gl_InstanceID magic.

Feral know what their game needs and can adjust their wrapper accordingly. DXVK can't, it needs to satisfy all possible use cases.

Wow, OK far more complicated than I imagined, and yes I can see for a general 'emulator' not knowing how each implementation of stream output in every game works you cant produce a general function to replace, you would have to create one case for every game and that would be ugly and wasteful.

Thanks for the explanation.

Quoting: ShmerlNvidia introduced a new SPIR-V compiler recently, may be it's affecting it? Try disabling it with:

__GL_NextGenCompiler=0

The new compiler was introduced in the 396.18 beta driver, so that can't be it.

Quoting: GuestDXVK now support fullscreen in non native resolutions :D

It's still a bit broken and particularly for Witcher 3, transitioning back from fullscreen to windowed doesn't work properly (missing window border) - but that did never work in the first place.

Quoting: tuubi

Quoting: ShmerlNvidia introduced a new SPIR-V compiler recently, may be it's affecting it? Try disabling it with:

__GL_NextGenCompiler=0

The new compiler was introduced in the 396.18 beta driver, so that can't be it.

I tried setting that environment variable, and I'm still having the same problems. At this point, I'll probably wait until after I upgrade to Fedora 28 and then give things another go. I'm wondering if perhaps the binary .dll files that I downloaded are linked in a certain way that's incompatible with Fedora? Has everyone here built their own DXVK, or are other folks also using the binary releases?

Thanks!

Quoting: rstrubeHas everyone here built their own DXVK, or are other folks also using the binary releases?

I always build them, it's not hard - give it a try.

Quoting: rstrube

Quoting: tuubi

Quoting: ShmerlNvidia introduced a new SPIR-V compiler recently, may be it's affecting it? Try disabling it with:

__GL_NextGenCompiler=0

The new compiler was introduced in the 396.18 beta driver, so that can't be it.

I tried setting that environment variable, and I'm still having the same problems. At this point, I'll probably wait until after I upgrade to Fedora 28 and then give things another go. I'm wondering if perhaps the binary .dll files that I downloaded are linked in a certain way that's incompatible with Fedora? Has everyone here built their own DXVK, or are other folks also using the binary releases?

Thanks!

I've only tried the Unigine benchmarks using binaries from https://haagch.frickel.club/files/dxvk/README.txt (found the link somewhere here on GOL). They worked pretty much out of the box (very impressively) on my Fedora 27 machine with wine 3.5 (and now 3.6) from the Fedora repositories. I'm still on NVidia 390.48.

Quoting: rstrubeHas everyone here built their own DXVK, or are other folks also using the binary releases?

Thanks!

I used the Binary when I tested; I have a few other games to go so will probably wait a while til either the OpenGL WINE implementation is providing better performance, or until Vulkan has a way to elegantly deal with Stream Output.

Quoting: ajgpI have a few other games to go so will probably wait a while til either the OpenGL WINE implementation is providing better performance, or until Vulkan has a way to elegantly deal with Stream Output.

Both will take a while.

Mohandevir:

"I've been able to install and make Steam's Witcher 3 start following cRaZy-bisCuiT's how-to, with Wine 3.7.

In fact I copied the game folder of my Windows install to my wine prefix. This said, it's really laggy and slow. Better than stock Wine but not really playable. It's far from the Windows version with the same hardware (i7-3770, GTX 960, Nvidia 396.18). Any clue what might be wrong?"


Shmerl:
"Better use this thread for it."

Thanks! Didn't tought about this one.

I'm using DXVK 0.42 with Wine 3.7. Didn't know about the regression with Nvidia driver 396.18. Will try driver 390.

Found this thread:
https://github.com/doitsujin/dxvk/issues/267

Totally noob in _GL_NextGenCompiler... Is this a xorg.conf parameter? How do you configure that?