You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Is your feature request related to a problem?
Right now, vinegar requires you to have /bin/wine64 located in wineroot, but nowdays wine, after v10 bundles all them into one binary, even the ones that isn't wow64.
There's a missing support for higher wine 10 versions, because they don't come with wine64 executable, and thus it fail.
Describe the Solution you'd Like
Maybe add a bool variable for [studio] to manually activate wow64 support or latest wine versions, so if it's true, it won't check for wine64, only for wine.
Describe Alternatives you've considered
(none)
Obviously, using default steam wine 9.0 will still be usable.
But, since latest wine version includes better support for Wayland, this is a better option to choose this over outdated wine versions.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Is your feature request related to a problem?
Right now, vinegar requires you to have /bin/wine64 located in wineroot, but nowdays wine, after v10 bundles all them into one binary, even the ones that isn't wow64.
There's a missing support for higher wine 10 versions, because they don't come with wine64 executable, and thus it fail.
Describe the Solution you'd Like
Maybe add a bool variable for [studio] to manually activate wow64 support or latest wine versions, so if it's true, it won't check for
wine64
, only forwine
.Describe Alternatives you've considered
(none)
Obviously, using default steam wine 9.0 will still be usable.
But, since latest wine version includes better support for Wayland, this is a better option to choose this over outdated wine versions.
Additional context
No response
The text was updated successfully, but these errors were encountered: