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](https://github.com/wine-staging/wine-staging)

Quoting: malek69btw: new wine staging repo: [https://github.com/wine-staging/wine-staging](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](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](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). :-(

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

Could it be some Nvidia driver regression? Did you update it recently? At least with Mesa I don't see anything of the sort.

Similar to what I thought, but I got the problem on the old driver and then updated to the latest.
I upgraded after I got the problem, so it was present on 387.xx as well. :-/
Also tried it on kernel 4.14 etc.

Same scenario, works on 3.0 but not on 3.2.

A major patch related to memory management / buffer hack: https://source.winehq.org/patches/data/141918

So far no improvement with those patches:



CPU utilization is now also erratic.

Quoting: GuestHonestly.. i think they should stop wasting their time trying to get Witcher 3 to go well with GL. DXVK is the approach they should take.

I wouldn't call it a waste. OpenGL backend for DX11 in Wine is already in a very good shape, while work on dxvk will take a long time still. I'd suggest for them to finish it, and work on dxvk in parallel. Though I don't know how good the chances are for upstreaming it.

Freshly built Vanilla Wine 3.2 (64bit only) - No Staging patches.







Framerate doesn't surpass the 20fps mark and for the first time I'm not seeing invisible floor.

Registry Settings:

[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"csmt"=dword:00000001
"UseGLSL"="enabled"
"VideoMemorySize"="6144"

System:

Linux Mint 18.1*
GTX 1060 / Driver 384.111
Kernel 4.15.3-generic

*Wine binaries have been built using Debian 9

Quoting: Avehicle7887for the first time I'm not seeing invisible floor.

That has been fixed for a while already.

Quoting: Shmerl

Quoting: Avehicle7887for the first time I'm not seeing invisible floor.

That has been fixed for a while already.

I kinda knew I was a bit late for the party :-)

EDIT: Any idea about the fps improvement over 3.1?

Quoting: Avehicle7887EDIT: Any idea about the fps improvement over 3.1?

For me it only got worse since buffer pool hack isn't applicable anymore.

Tried a build based on wine staging 2.21 with the recently announced wine-pba.
Sadly it results in the same "black screen with cursor" that is already reported in github.

Looks like work is ongoing to port it to DX11 so black screen in DX11-Witcher probably is to be expected.

Very interesting to see where this goes. :-)

https://comminos.com/posts/2018-02-21-wined3d-profiling.html