The new WINE 4.6 development release is available for testing and with initial Vulkan backend support for WineD3D.
Last Friday (12), the WineHQ folks released WINE development version 4.6, bringing some code improvements, bug fixes, and timely updates. This to make life even easier for those who need to run a program or game that has no native version for Linux.
WINE is very important in the Linux world, because through it we can run a range of programs and games that do not have a native version of Penguin, so these can be enjoyed by Linux users.
And in this new development version of WINE, came some very interesting implementations, such as:
– Start of a Vulkan backend for WineD3D;
– Support for loading Mono libraries from a shared location;
– Libwine.dll is no longer needed when using Wine DLLs on Windows;
– Support for complex structures in marshaller typelib;
– Video capture ported to Video4Linux version 2;
– Initial version of the debug engine DLL.
Besides bringing corrections to games like Warframe (via Steam), Mass Effect 1, The Sims and others. And the most curious point, was Battleye appearing in the list of WINE mails, with the following line:
Battleye's BEDaisy.sys requires correct KeGetCurrentThread implementation
But, nothing concerning the functioning of the Battleye of Windows at the Wine, which would allow games like RainbowSix, PUBG and Fortnite for example. And as the company told the people at GamingOnLinux, That can only support Linux if the game has a native version of the system., it seems that WINE people will have to create their own solutions.
But a good sign to see WINE people, CodeWeavers and Valve try to make the Battleye because Valve negotiates with EAC, so she can bring her anticheat compatibility to Protron.
If you would like to check out all bug fixes and improvements in this version of WINE, you can check this link. This article does not end here, keep exchanging an idea there in our forum
Hope to see you next, a big hug.
_____________________________________________________________________________ See any errors or would you like to add any suggestions to this article? Collaborate, click here.