Wine 3.3 is out with a start on Vulkan support, D3D multi-threaded command stream is on by default

How does the witcher 3 run in regular wine nowadays? Does it run faster or show less graphical artifacts than wine-staging?

Performance is bad now. Also, the bug with invisible monsters has a fix in Wine source, but it's still causing freezes with AMD / Mesa, at least for some people. Strangely, some don't get these freezes.

Does this mean that Xbox controllers are finally recognized, or does it still need more work? Sorry not too familiar on wine stuff.

This wine version needs new dependency: LibSDL2.0-dev

Also add part of colenbrander vulkan work, another items dont be approved for now

This is some titles working in this wine version

View video on youtube.com

View video on youtube.com

View video on youtube.com

^_^


Last edited by mrdeathjr on 3 Mar 2018 at 11:10 pm UTC

Does this mean that Xbox controllers are finally recognized, or does it still need more work? Sorry not too familiar on wine stuff.

I already play Zelda BOTW with wine-staging 2.21+cemu with an xbox 360 controller without any tweaks, so I think it's compatible for a while..

Hello Mrdeathjr,

Rayman Origins doesn't need directx installed anymore? It works now without native dll?


Last edited by legluondunet on 3 Mar 2018 at 9:43 am UTC

/me waiting for wine-staging to hit AUR...

Hello Mrdeathjr,

Rayman Origins doesn't need directx installed anymore? It works now without native dll?

Hi

I use steam version of rayman origins and steam installs directx

However dont need configure any native dll for this game*

*In other cases is needed configure native dll on winecfg

^_^

/me waiting for wine-staging to hit AUR...

Try this one:
https://aur.archlinux.org/packages/wine-staging-dev/

I uploaded it, and it's compiled from the official wine development git, as well as the new staging fork that is 3.x compatible located over at https://github.com/wine-staging/wine-staging

Edit:
Updated my package name to not indicate affiliation with Lutris, which was never anything but a misunderstanding based on twitter comments. *rofl*


Last edited by Goldpaw on 3 Mar 2018 at 2:28 pm UTC

Wonder if it is possible to disable Direct3D multi-threaded command stream now with Wine 3.3, as there is one or two games that doesn't like it

/me waiting for wine-staging to hit AUR...

Try this one:
https://aur.archlinux.org/packages/wine-staging-lutris-git/

I uploaded it, and it's compiled from the official wine development git, as well as the new staging fork that is 3.x compatible located over at https://github.com/wine-staging/wine-staging

I guess the name is slightly misleading as it's not really affiliated with Lutris, I just named it so since the news about the new staging fork was from the Lutris guys to begin with. The staging repository is worked on daily though, and currently by far the most updated one.

Go for it! :)

Wait, what? The new Staging fork is already 3.3 compatible?

Goldpaw: I am going to compile it right now. Thanks :)

/me waiting for wine-staging to hit AUR...

Try this one:
https://aur.archlinux.org/packages/wine-staging-lutris-git/

I uploaded it, and it's compiled from the official wine development git, as well as the new staging fork that is 3.x compatible located over at https://github.com/wine-staging/wine-staging

I guess the name is slightly misleading as it's not really affiliated with Lutris, I just named it so since the news about the new staging fork was from the Lutris guys to begin with. The staging repository is worked on daily though, and currently by far the most updated one.

Go for it! :)

Wait, what? The new Staging fork is already 3.3 compatible?

Well I really hope so since my AUR package is based on the git versions! :D

But yeah, as far as I can tell the new staging branch is based off of the most recent versions of the official wine development git repository. I have been unable to apply the staging patches to anything else. And I've been using it with 3.2 for a while already.

Oh, and I renamed my package since it is unrelated to Lutris, btw:
https://aur.archlinux.org/packages/wine-staging-dev/

Same package as before, though. Just a more correct name, reflecting that it's a development version of the new staging, how confusing that might sound! I'm currently in the process of building it myself here. Crossing my fingers, but don't expect any problems tbh. As mentioned I've been doing fine with the 3.2 version for some time now.

Goldpaw: I am going to compile it right now. Thanks :)

Moved it to https://aur.archlinux.org/packages/wine-staging-dev/
It's the same package though, only the misleading name has been changed.

Edit:
Package deleted. The owner of the wine-staging-git package at the AUR updated his to use the same new staging repository as mine, then requested mine to be deleted on the basis of it being "a clone of his". Think of that what you may. The new updated staging AUR repository can be found at:
https://aur.archlinux.org/packages/wine-staging-git/


Last edited by Goldpaw on 5 Mar 2018 at 12:33 pm UTC

Wonder if it is possible to disable Direct3D multi-threaded command stream now with Wine 3.3, as there is one or two games that doesn't like it

You can turn CSMT on or off in Wine with the latest version of winetricks these days. Just fire up the winetricks GUI and you will see the setting for CSMT.

Also, CSMT in Wine (non-staging) is off by default for reasons such as the one you listed in your post.

Wonder if it is possible to disable Direct3D multi-threaded command stream now with Wine 3.3, as there is one or two games that doesn't like it

Yeah as your said various titles give troubles with csmt

However wine entry registry stay avalaible, winetricks as other said or if you use vanilla can add donat enikeev patch for winecfg

https://mega.nz/#!XNkBVDgA!nhjqiDlzfxw7VhY8OVTpNXzZtYmoLZm6wNVkfX6ueZs

^_^

winetricks csmt=on
winetricks csmt=off


Last edited by malek69 on 4 Mar 2018 at 10:11 am UTC

winetricks csmt=on
winetricks csmt=off

Except you need to set needed wine and wineprefix variables properly first. Example:
export wine_bin='wine' # in case of 32-bit
export wine_bin='wine64' # in case of 64-bit

# needed for wine
export WINEPREFIX=... # path to your Wine prefix
export WINEVERPATH=... # path to your Wine directory
export WINESERVER=${WINEVERPATH}/bin/wineserver
export WINELOADER=${WINEVERPATH}/bin/${wine_bin}
export WINEDLLPATH=${WINEVERPATH}/lib/wine/fakedlls
export PATH=${WINEVERPATH}/bin:$PATH 
export LD_LIBRARY_PATH="${WINEVERPATH}/lib:${LD_LIBRARY_PATH}"

# needed for winetricks
export WINE=${WINEVERPATH}/bin/${wine_bin}


Last edited by Shmerl on 4 Mar 2018 at 10:43 pm UTC