We do often include affiliate links to earn us some pennies. See more here.
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.
Tags: Wine
9 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
44 comments
Page: «2/5»
  Go to:

wojtek88 Mar 4, 2017
Quoting: STiATThere is no reason to believe that CDPR is going to Vulkan at all. They use HLSL compiler for Cyberpunk, so.. no Vulkan there. Maybe DX12 if even, CDPR is not known to be adopting technology fast. Maybe for titles after Cyberpunk.

Bethe is another topic. They have been always negative about Linux, but if they port to Vulkan I believe we could get some nice performance using wind (or similar, maybe newer and lesa cluttered solution).
Instead of using wind I would use flame. Or water! Or stone!

Quoting: ShmerlWaiting 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.
It seems that Wine is reaching a point when it will be possible to run Witcher 3. The day it will be possible to fluently play the whole game would be IMO a milestone for Wine. And I can't wait this day.
bubexel Mar 4, 2017
To much talking about witcher 3... what about fallout 4? anyone tested it?
mrdeathjr Mar 4, 2017
In this wine version more work related csmt are added (but in test some games and dont note changes at simple seek)

However more game begins needs xinput libraries as builtin to have input (case senran kagura: xinput1_4 and others)

View video on youtube.com

^_^

​​​​​​​


Last edited by mrdeathjr on 4 March 2017 at 10:14 pm UTC
Shmerl Mar 5, 2017
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.
TheRiddick Mar 5, 2017
Witcher 3 is such a hungry game, your going to need at least %70 of windows performance for it to be playable at 1080p.

That's going to take a VERY long time, the reason why I suggested TW3 devs could make Vulkan happen is because VulkanAPI is getting momentum which often encourages the industry to move along with API's, if SkyrimSE/Fallout4 get Vulkan then tw3 is going to look pretty weak in comparison.

Just keep in mind the Switch is apparently running Skyrim under Vulkan ;)
Shmerl Mar 5, 2017
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).
Shmerl Mar 5, 2017
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.


Last edited by Shmerl on 5 March 2017 at 7:42 am UTC
Shmerl Mar 5, 2017
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.


Last edited by Shmerl on 5 March 2017 at 6:39 am UTC
mrdeathjr Mar 5, 2017
Quoting: ShmerlWine 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.

Interesting but tesselation patch from Guillaume Charifi is possible cant aproved in main branch, staging is different thing

Because DX11 area depend of jozef kucia work, recently in wine-dev them talk about this*

*Apparently jozef kucia tesselation work appears more valid than Guillaume Charifi, however jozef kucia tesselation work dont uploaded

Without forget henri verbeet must be approved or reject patch

Respect performance traditionally dont have high priority for wine devs (staging are different) for them are is more important have function, test function (this is very important to approval patch), after this could be stay compatibility and after this appears performance

^_^


Last edited by mrdeathjr on 5 March 2017 at 2:09 pm UTC
sr_ls_boy Mar 5, 2017
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
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.