Wine 2.3 released with more Direct3D command stream and Shader Model 5 work

Anyone 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

Are you attempting to compile Wine Staging? Reason I ask is because it looks like this patch https://github.com/wine-compholio/wine-staging/commit/fae17cd83a1523444e93bdd9ef86a88756c5cacf may be at fault judging by the "concrt140.spec:349: function '_CurrentScheduler_Id' not defined" error.

If so, you may want to submit a bug report to Wine HQ under the Wine Staging product...

...you may want to submit a bug report to Wine HQ under the Wine Staging product...

I wrote to Lackner. He said that others are reporting this and it would be fixed when 2.3(S)
is released.

O my WINE God , Warhammer:End Time work :O , unbelievable.

Anyone 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.

Now it's getting somewhere:

RX480, min settings, buffer pool patch

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


Last edited by Shmerl on 5 Mar 2017 at 8:00 pm UTC

Buffer 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.

Buffer 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.

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.


Last edited by Shmerl on 5 Mar 2017 at 9:35 pm UTC

Kaer Morhen balcony.


Ciri exercising


Kaer Morhen, sparring in the yard.


Another outside screenshot:


Besides certain shaders still missing (which produces transparent parts, wrong hair color and so on), it looks already pretty good, and the whole thing is fluidly playable (at least on lowest settings for me).


Last edited by Shmerl on 6 Mar 2017 at 3:36 am UTC

Another outside screenshot:
(...)
Besides certain shaders still missing (which produces transparent parts, wrong hair color and so on), it looks already pretty good, and the whole thing is fluidly playable (at least on lowest settings for me).

Fantastic. Are there any non-graphical issues or does everything function as it should?

Another outside screenshot:


Besides certain shaders still missing (which produces transparent parts, wrong hair color and so on), it looks already pretty good, and the whole thing is fluidly playable (at least on lowest settings for me).

This is definitely good news. Can't wait to 2.4/2.5 releases when we might be able to play it almost out of the box :D

Fantastic. Are there any non-graphical issues or does everything function as it should?

So far I didn't notice any non graphical issues.

Fantastic. Are there any non-graphical issues or does everything function as it should?

So far I didn't notice any non graphical issues.

Witcher 3 on Windows has support for the Xbox 360 controller. Have you been successful in getting that to work at all?

Witcher 3 on Windows has support for the Xbox 360 controller. Have you been successful in getting that to work at all?

I don't have a controller to test at present unfortunately. Feel free to run some tests. Let me know if you need help with building Wine with all needed patches to run it.

FYI: To run TW3 you don't need the complicated WoW64 build, which requires using something like lxc container, and running 32-bit build twice. You can simply build 64-bit Wine with patches from staging and buffer pool hack.


Last edited by Shmerl on 6 Mar 2017 at 6:07 pm UTC

Witcher 3 on Windows has support for the Xbox 360 controller. Have you been successful in getting that to work at all?

I don't have a controller to test at present unfortunately. Feel free to run some tests. Let me know if you need help with building Wine with all needed patches to run it.

FYI: To run TW3 you don't need the complicated WoW64 build, which requires using something like lxc container, and running 32-bit build twice. You can simply build 64-bit Wine with patches from staging and buffer pool hack.

Well, I use Arch's PKGBUILD which builds WoW64 Wine for me anyways so I don't have to worry about all that :) I only asked about controller support because the usual workaround (i.e. install x360ce in a prefix, dump some files next to the game's executable) does not work with purely 64-bit games for a number of reasons, the main one having to do with certain dotnet versions just not working in 64-bit prefixes.

I was hoping that the game may see the controller somewhat but perhaps just needs a winetrick or two...


Last edited by JudasIscariot on 6 Mar 2017 at 8:39 pm UTC

I suppose Steam controller could be a viable option.

Staging 2.3 has just been released in PPA Repos. Unfortunately performance in Guild Wars 2 is still 15-20fps less than 2.0 Staging. Meanwhile in Crysis Warhead there's 2-3 FPS more in Wine 2.3.

FYI: Wine staging 2.3 now includes the buffer patch, which improves TW3 performance.

See https://github.com/wine-compholio/wine-staging/commit/f473f9cb80b34e52b2c3d7a867d4d3f4b99f14c7

https://github.com/wine-compholio/wine-staging/blob/master/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch


Last edited by Shmerl on 7 Mar 2017 at 12:43 am UTC

Staging 2.3 has just been released in PPA Repos. Unfortunately performance in Guild Wars 2 is still 15-20fps less than 2.0 Staging. Meanwhile in Crysis Warhead there's 2-3 FPS more in Wine 2.3.

It's also available in the official Arch repos as well :D

The day Witcher 3 is playable on Wine will be milestone for me. Next steps will be GTA V and Fallout 4.
Having those titles playable will be great and it would be easier to convince people who like playing games to switch to Linux when Windows 7 looses it's support.

Of course there was a moment when Windows XP lost it's support and Linux missed it. One of the reasons was that Wine wasn't mature enough. With Wine in such a good shape it would be a good moment to take a little more from the market.
Microsoft tried to force people to upgrade to Windows 10 because they see the risk of loosing part of the market when support for Windows 7 ends. Unfortunately for them, they put so many questionable solutions to it's newer system, that some people didn't want to upgrade.

If they will have alternative (to Windows) system, that would allow them to play their favorite games and wouldn't spy them on every interaction with the system, they may consider it as a viable alternative.