Wine 2.3 has officially released today and the developers are continuing their work to improve Wine performance and work on Shader Model 5.
For those of you that don't know what "Direct3D command stream" means, it's multithreading to improve performance of games ran in Wine with OpenGL.
Highlights:
- Obsolete wineinstall script removed.
- More Direct3D command stream work.
- A few more Shader Model 5 instructions.
- Better underline rendering in DirectWrite.
- Improved ODBC support on 64-bit.
They also fixed 41 bugs with running Starcraft 2, Final Fantasy XI Online, STALKER Shadow of Chernobyl, Final Fantasy V and plenty more.
I expect Wine-Staging will also have their own 2.3 release within a few days with their usual extras included. Article taken from GamingOnLinux.com.
For those of you that don't know what "Direct3D command stream" means, it's multithreading to improve performance of games ran in Wine with OpenGL.
Highlights:
- Obsolete wineinstall script removed.
- More Direct3D command stream work.
- A few more Shader Model 5 instructions.
- Better underline rendering in DirectWrite.
- Improved ODBC support on 64-bit.
They also fixed 41 bugs with running Starcraft 2, Final Fantasy XI Online, STALKER Shadow of Chernobyl, Final Fantasy V and plenty more.
I expect Wine-Staging will also have their own 2.3 release within a few days with their usual extras included. Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
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
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...
0 Likes
Quoting: JudasIscariot...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.
1 Likes, Who?
O my WINE God , Warhammer:End Time work :O , unbelievable.
0 Likes
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_IdTo avoid this breakage.
0 Likes
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 March 2017 at 8:00 pm UTC
RX480, min settings, buffer pool patch
RX480, max settings, no hairworks, no SSAO, buffer pool patch
Last edited by Shmerl on 5 March 2017 at 8:00 pm UTC
2 Likes, Who?
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.
0 Likes
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.
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 March 2017 at 9:35 pm UTC
0 Likes
Kaer Morhen balcony.
Ciri exercising
Kaer Morhen, sparring in the yard.
Ciri exercising
Kaer Morhen, sparring in the yard.
0 Likes
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 March 2017 at 3:36 am UTC
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 March 2017 at 3:36 am UTC
1 Likes, Who?
qptain Nemo Mar 6, 2017
Quoting: ShmerlAnother outside screenshot:Fantastic. Are there any non-graphical issues or does everything function as it should?
(...)
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).
0 Likes
Patreon
PayPal
See more from me