Wine 3.2 released with gamepad improvements and more Direct3D work

I wonder if Wine Staging is still a thing.

Looking foreward, I wonder if System Shock fix related to 4 player coop lan.

Is Wine Staging dead now?

In this wine version add csmt as default (must be disable depending app)

James Bond 007 Blood Stone

With wine 2.1

https://www.youtube.com/watch?v=TBdC6C4Pyyg

And now

View video on youtube.com

Samurai Warriors 4 II

With wine 2.3

https://www.youtube.com/watch?v=npb2112xhsE

And now (curiously in test require d3dx9_43 as built-in for run and other case devenum, qedit and quartz as native for cinematics)

View video on youtube.com

Spiderman Shattered Dimensions

With wine 2.2

https://www.youtube.com/watch?v=2CPO-LUfMz0

And now

View video on youtube.com

Add multisample textures but dont stay clear if inmutable storage stay ready according jozef kucia said

Xinput shows improvements (Aric Stewart work) but lack code but next wine stay very interesting

Quotewinebus.sys: map SDL GameControllers if requested

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

winebus.sys: Implement SDL Haptic for controller vibration

In other things quartz as native works better allow cinematics in fullscreen (virtual desktop mode tested) in before version are needed put as built in and need push in taskbar for game reentry and show cinematics

And in tests WINEDEBUG=-all,+fps works better for fps counter than steam fps overlay

^_^


Last edited by mrdeathjr on 18 February 2018 at 1:29 am UTC

Quoting: LeopardIs Wine Staging dead now?

Take with a wheelbarrow of salt.

IIUC a lot of staging was mainlined suchas CMST around 3.0.

wine staging maintainer is AFK for a while now and someone else was looking to step in to do his job.

Last wine staging was 2.2X.


Last edited by ElectricPrism on 17 February 2018 at 12:17 am UTC

For them asking staging situation in this topic find more information

https://bugs.winehq.org/show_bug.cgi?id=44406

This is some information posted today

QuoteSveinar Søpler 2018-02-16 09:41:49 CST

There are enourmous amounts of changes from 2.x -> 3.x, so rebasing wine staging from last-known 2.21 -> 3.1 is a huge undertaking.

If staging should have stayed "alive" in its previous form, this would have been needed to be rebased each git-master i guess, cos the changes from 2.21 -> 3.1 (current dev) is very large.

Its a real shame that none from winehq-dev spits out any public message, cos what is going on now is that there will be 2-3-4+ ppl/groups all doing their own rebases.. possibly to varying degrees.

The documentation on the staging repository is there.. in the history of commits, so if it would be of use, one should cherry pick "important" patches, and get those in. Doing the whole patch-set is... well.. too daunting imo.

Kudos to everyone lending a hand tho! :)


Comment 12 Henri Verbeet 2018-02-16 10:20:46 CST

If it's any consolation, the Staging people haven't told us anything either. Clearly that's not ideal.

I'd suggest people interested in picking up the Staging patches coordinate on the wine-devel mailing list and the #winehackers IRC channel, but ultimately that's of course up to individual people.


Comment 13 Luke Short 2018-02-16 17:50:50 CST

It was expressed a few months ago at WineConf 2017 that, moving forward, the idea is to work on cleaning up the hacky patches from Wine-Staging and get them into the official Wine project faster.

If you keep track of the wine-devel mailing list you will already notice that a lot of patches have already been cleaned up and integrated.

With the Wine 3.0 release, Alexandre even gave the greenlight to integrate the long-awaited command stream multi-threading (CSMT) patches.

https://www.youtube.com/watch?v=AokFgDSLMWU


Comment 14 Zebediah Figura 2018-02-16 18:36:12 CST

The suggestion was made, and some people (mostly Vincent, more recently also Alistair among others) have been trying to do so.

That said, none of the Staging people attended the last conference (and indeed they've been radio-silent since early November, before the conference began), so it's not really the case that the agreed-upon intent is now to get rid of Staging.

^_^

HID Gamepad support means that we don't need to use dumbxinputemu etc. anymore? If that's the case, great news.

Does anyone know what's the situation with Gallium Nine, will it be rebased on Wine vanilla?

Quoting: ziabiceDoes anyone know what's the situation with Gallium Nine, will it be rebased on Wine vanilla?

I dont think so

Wine devs sometime ago cited dont have any interest in support double implementation

In same situation could be put dxvk

However in last point wine stay working in vkd3d (for now dx12)

Maybe them can change in future to vulkan* because this api runs in all hardware with all type of drivers

*Thanks to dxvk project for probe vulkan possibilities

^_^

Quoting: YoRHa-2BHID Gamepad support means that we don't need to use dumbxinputemu etc. anymore? If that's the case, great news.

In teory yes however i said before dont have all code now

In next wine if devs approve aric stewart work could recognize xbox gamepads with own names thanks to add xbox gamepads pids

Maybe in next two weeks aric stewart can add pids of playstation gamepads

^_^

Seems like wine-staging is being rebased to wine 3.x

wine-satging github