Quoting: ToposBuffer patch? Never heard of that. Wait does it mean you can now play 60 fps meaning the game is now fully playable? I'm really impressed. Please do post more screenshots if you can, preferably from the open world sections of the game.

It's a hack which in this case makes GPU more loaded (before it was idle too much). See here [External Link].

The game is somewhat playable, but some graphics still look incorrect or missing, so I wouldn't call it fully playbale. Still, the progress of Wine developers has been very good. I didn't progress in the game much, but I'll try to make some screenshots of outside areas.

I got 60fps on low settings with RX480 and Mesa master (relatively recent build). On max settings, GPU load spikes to 100%, and framerate drops to 45-50fps. I assume a better card can possibly push it higher. I'm looking forward to Vega for this. It possibly can still get better even on RX480 too.

View this comment - View article - View full comments

Now it's getting somewhere:

RX480, min settings, buffer pool patch


RX480, max settings, no hairworks, no SSAO, buffer pool patch

View this comment - View article - View full comments

Quoting: sr_ls_boyAnyone having problems during compilation? This is with the patches.

make[1]: Entering directory '/home/sr_ls_boy/src/wine/build64/dlls/concrt140'
../../tools/winegcc/winegcc -o concrt140.dll.so -B../../tools/winebuild -m64 -fasynchronous-unwind-tables -shared ../../.././dlls/concrt140/concrt140.spec \
../../libs/port/libwine_port.a -Wl,-rpath,/usr/lib64 -L/usr/lib64 -Wl,-rpath,/lib64 -L/lib4
../../.././dlls/concrt140/concrt140.spec:349: function '_CurrentScheduler_Id' not defined
winegcc: ../../tools/winebuild/winebuild failed
make[1]: *** [Makefile:165: concrt140.dll.so] Error 2
make[1]: Leaving directory '/home/sr_ls_boy/src/wine/build64/dlls/concrt140'
make: *** [Makefile:5982: dlls/concrt140] Error 2

Yes, when applying staging patches, I had to add -W msvcrt-CurrentScheduler_Id

To avoid this breakage.

View this comment - View article - View full comments

Here is more detailed GALLIUM_HUD, showing individual CPU cores load:



Mostly it seems one core tends to max out, so it's not very evenly distributed.

Wine is clearly progressing with DX11 features, but performance will be another major area developers will need to address. I'm not sure how much of this is caused by Mesa as well. I hope someone with Nvidia blob and recent cards will post more benchmarks.

View this comment - View article - View full comments

OK, here is the result with Wine staging built from source (CSMT enabled):

Low settings:



High settings:



FPS is pretty bad. On RX 480 I'm getting 6fps at 1920x1200 no matter what graphics settings are selected.

View this comment - View article - View full comments

Quoting: Leopard@Shmerl

No native Tux,no bucks

I didn't pay for the game so far, someone gave me a spare GOG key that came with Nvidia card (they had that promo for a while).

View this comment - View article - View full comments

Quoting: sbolokanovJust retested witcher 3 with latest git (wine 2.3) + memory patch and it does render better (not as good though, staging we need).

Looks like staging git just was rebased on the recent Wine git master. I'll try building it from source with all staging patches to see how it works.

View this comment - View article - View full comments

Waiting to test TW3 in Wine staging, once patches will catch up. Guillaume Charifi from Wine developers claims, that he tested tesselation shaders implementation, and got such results:



These patches don't seem to be public though.

View this comment - View article - View full comments

Unofficial community bug tracker opened: https://github.com/tton-bugs-hunters/tton-bug-tracker/issues [External Link]

How to report bugs [External Link].

View this comment - View article - View full comments

Quoting: ShabbyXIn other words, you would end up coding in Vulkan as the universal API, and use the translation layer when not possible, for example on OSX, PS and XBox.

Yes, that's actually a good direction for now. And unlike MoltenVK that translation layer should be open.

View this comment - View article - View full comments