I applied that method above to Wine master, setting access mask WINED3D_RESOURCE_ACCESS_GPU | WINED3D_RESOURCE_ACCESS_MAP. Performance is pretty bad, just around 20fps instead of 40 like before.

No black screen or anything the like though, the game starts OK.

Just tried with official/white 3.2 build:
Same exception and black screen as with black build from master.
Official 3.1 works fine on the given wineprefix.

So probably something related to my system and some change in Wine introduced lately. :-(
When I have the time I will try on a fresh wineprefix.

Linux 4.15.3-041503-generic x86_64
NVIDIA GTX 1080 with driver version: 387.34
Ryzen 1700

I just tested with my old prefix. Wine-devel 3.2 and was able to get to in game just fine. Performance wasn't as good as with old staging versions but between 10-30fps depending on conditions. GPU utilization was quite low, 30~40% with GTX 1070, 384.111 driver.

Yes, vanilla is still sucking.
wine 3.2 View video on youtube.com
old wine staging 15-20 fps View video on youtube.com

btw: new wine staging repo: https://github.com/wine-staging/wine-staging

Quoting: malek69btw: new wine staging repo: https://github.com/wine-staging/wine-staging

I don't think we need Wine staging for TW3 anymore.

Quoting: Shmerl

Quoting: malek69btw: new wine staging repo: https://github.com/wine-staging/wine-staging

I don't think we need Wine staging for TW3 anymore.

You have to wait a little.
https://dev.wine-staging.com/patches/submission/269/

ninja edit, i see Your answer. :D

Yeah. I think the point is to make upstream Wine work well with TW3, applying only very minimal patches if needed. Not the full staging patchset.

That's how this pool hack used to work, until it became outdated.

Quoting: ShmerlThat's how this pool hack used to work, until it became outdated.

this patch??
https://source.winehq.org/git/wine.git/commit/916c13c6c132edbcfc4558a779813a263d0c4e77

Quoting: malek69

Quoting: ShmerlThat's how this pool hack used to work, until it became outdated.

this patch??

I mean the regular staging pool hack: https://github.com/wine-compholio/wine-staging/blob/master/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch

It was applicable without touching any other staging patches. Now it's obsolete, and even its reworked version doesn't help (as I said above).

I suppose Wine developers will need to figure out how to properly address low performance issue.

Just FYI, tried with a clean wineprefix with only steam and witcher => same behavior as in previous post. Hanging and black screen (Wine 3.2). :-(