WineskinServer VS wine-staging

You may be interested in Wineskin for M1/M2 Macs. I use this to play some old school games on my 2023 M2 Max Mac. https://github.com/Gcenx/WineskinServer

Hi, I followed this guide of u/Gcenx https://github.com/Gcenx/WineskinServer/issues/420 and applied on wine 8.10 staging (this version https://github.com/Gcenx/macOS_Wine_builds/releases/tag/8.10) but it seems like it doesn't work I always get a stub error. My question is: I need to do something else or D3DMetal simply doesn't work on newer wine version

Otherwise I'd start on a per-game basis with wine, and if that doesn't work out then I would try crossover mac, which is similar but sometimes has better compatibility (and is relatively expensive). If those solutions don't work you can try Parallels (also relatively expensive), but personally I feel that solutions involving Parallels are too far gone to be practical.

better yet you can package notepad++ as a normal macOS app with Wineskin Winery, crossover is not needed here

(https://github.com/Gcenx/WineskinServer/releases/latest)

Then install the custom wineskin app by copying the code under **How to Install** (https://github.com/Gcenx/WineskinServer) and paste it into the Terminal.

Install Wineskin from https://github.com/Gcenx/WineskinServer. Note the option to install with homebrew. Run that command (again in terminal). Follow the steps.

CrossOver uses a modified version of Wine to let you install .exes into separate .apps. It can boot certain games that Parallels can't, but sometimes it can really chug. Parallels creates a virtual machine of ARM Windows, meaning you have to boot the virtual machine to run any apps. And then Wineskin just uses plain ol' Wine to create .apps, much like Crossover but perhaps less streamlined. It also has less compatibility, especially for more graphically demanding games. Porting Kit is another version of Wineskin, but with a lot of the nitty-gritty solved for you.

same principles still apply either way, you can just install gcenx's wineskin (and then steam) to play old valve games.

vkd3d-proton: - occasional upstream pending patches wine: - uses proton's bleeding edge wine base: https://github.com/ValveSoftware/wine/tree/experimental-wine-bleeding-edge-7.0-20190-20220716-pe79367-w7a9d8c-d5aa943-v5b7313 - adds wine-staging on top of it: https://github.com/wine-staging/wine-staging/tree/master/patches - adds FSR patches on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/48-proton-fshack\_amd\_fsr.patch - adds a handful of other game fixes on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/e01207aafe539d8d3ed49301665da717340e4c1d/patches/protonprep-valve-staging.sh#L295 - removes the proton-specific steamclient changes so that it works as a normal wine build: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/0001-De-steamify-proton-s-WINE-so-it-can-be-used-as-a-sta.patch ffmpeg: - we enable some codecs not available in steam's ffmpeg gstreamer: - we enable some codecs not available in steam's gstreamer protonfixes: - these are python scripts that automate installing various winetricks and/or other per-game tweaks. this achieves the same thing most lutris installers perform. -------------------------

USE "HOMEBREW" https://brew.sh/ Or "MACPORTS" https://www.macports.org/ As subsystem or wrapper to help wine to be stable. I trying homebrew for a week right now with many versions of wine ( stable & bev , etc The fastest WINE wrapper updated is WINE STAGING. 🍷 https://github.com/wine-staging/wine-staging

These patches are missing: https://github.com/wine-staging/wine-staging/tree/master/patches/winepulse-PulseAudio_Support

You'll need the usual dependencies for Wine, so installing Wine or Wine-staging on your system is recommended even if only for that. Comes with support for AMD FSR through Proton's fullscreen hack - Enable with WINE_FULLSCREEN_FSR=1 env var, and tweak sharpening amount with WINE_FULLSCREEN_FSR_STRENGTH=5 (5 is default sharpening, lower numbers mean more sharpening, 0 is max sharpening) Comes with support for Nvidia DLSS for native Vulkan games (requires driver 470+), disabled by default - You can enable it with the PROTON_ENABLE_NVAPI=1 env var in your game's launch options - ValveSoftware/Proton@0503dde Comes with staging's mfplat implementation - https://github.com/wine-staging/wine-staging/commits/master Comes with the latest devel version of DXVK - https://github.com/doitsujin/dxvk/commits/master Comes with the latest devel version of HansKristian & Doitsujin's vkd3d-proton standalone - https://github.com/HansKristian-Work/vkd3d LAA is enabled by default. It fixes a huge amount of crashes on 32-bit games when using DXVK. However a small number of (older) games might run into issues with it, so you can disable LAA by using PROTON_DISABLE_LARGE_ADDRESS_AWARE=1 %command% in your game's launch options. Proton build has winetricks integration. It requires you to have the tk package (python3-tk on Debian based distros) installed and can be turned on/off in the ~/.steam/(root)/compatibilitytools.d/proton_tkg_6.16.r0.g931daeff.release/user_settings.py file.

Download the staging patches: git clone https://github.com/wine-staging/wine-staging --depth 1 (same deal as the first step: added "--depth 1" to only download the latest files from the source code)

This one could be a candidate for fixing this (but I have not tried what happens if I don't apply this to a recent wine version): https://github.com/wine-staging/wine-staging/blob/534f6ae34e89615fa424ee3e3002b1b3d419a8ba/patches/winebuild-pe_syscall_thunks/0002-winebuild-Call-__wine_syscall_dispatcher-through-the.patch

Alternatively, re-compile wine-staging and add this patch, which fixes the crash; and also this patch that fixes the locking cursor issue.

Hah, sorry, I misread your post and thought you said Roblox was crashing for you. To fix the mouse issue, like I said, you'll need to compile wine-staging from the very latest commit (otherwise it will crash), and also include the patch I mentioned.

You'll need the usual dependencies for Wine, so installing Wine or Wine-staging on your system is recommended even if only for that. Comes with support for AMD FSR through Proton's fullscreen hack - Enable with WINE_FULLSCREEN_FSR=1 env var, and tweak sharpening amount with WINE_FULLSCREEN_FSR_STRENGTH=5 (5 is default sharpening, lower numbers mean more sharpening, 0 is max sharpening) Comes with support for Nvidia DLSS (requires driver 470+), disabled by default - You can enable it with the PROTON_ENABLE_NVAPI=1 env var in your game's launch options - ValveSoftware/Proton@0503dde Comes with staging's mfplat implementation - https://github.com/wine-staging/wine-staging/commits/master Comes with the latest devel version of DXVK - https://github.com/doitsujin/dxvk/commits/master Comes with the latest devel version of HansKristian & Doitsujin's vkd3d-proton standalone - https://github.com/HansKristian-Work/vkd3d LAA is enabled by default. It fixes a huge amount of crashes on 32-bit games when using DXVK. However a small number of (older) games might run into issues with it, so you can disable LAA by using PROTON_DISABLE_LARGE_ADDRESS_AWARE=1 %command% in your game's launch options. Proton build has winetricks integration. It requires you to have the tk package (python3-tk on Debian based distros) installed and can be turned on/off in the ~/.steam/(root)/compatibilitytools.d/proton_tkg_6.14.r6.g1bc4da9d.release/user_settings.py file.

Who thought calling this "DOSBox Staging" as a good idea? Using that as the project name for a fork is (unintentionally?) confusing. Staging has a specific meaning with regard to software development, and additionally Wine Staging is a test branch for wine development. In both uses the "staging" software is implied to be part of the same project and maintainers, whereas this is a fork that's maintained by different developers with significant differences.