What benefit does a native build have over proton? I used to care more about it on Linux, until I realized that "native build" probably means "doesn't work." I can only imagine this being much worse on a niche gaming target which there are extremely few users making (and voting for) bug reports.
replyTack on having to pay Apple to play in their shitty ecosystem and it makes complete sense.
Wine/proton as a gaming ABI/runtime is perfectly fine, Microsoft used to do a lot to maintain backcompat and that spirit has clearly distilled into proton: it even runs games Windows is unable to (most recent example of mine is Black and White).
Native build usually also means it’s a supported platform and developers will try to fix any big issues coming up.
replyPeople stopped releasing Linux builds, too, since proton+win32 works better on average
reply> There were official native MacOS builds and now there aren't
replyThey probably stopped supporting macOS when Apple introduced the notarization bullshit. Can't blame the DF team tbh, macOS is a royal PITA to support (even without notarization), Apple doesn't mind breaking stuff from one OS release to another.
You should try speaking to the Apple manager.
replymacOS has changed a lot more than Windows or Linux did in the last decade. It's hardly Tarn's fault, here.
replymacOS is also just a proper PITA through and through. I'm annoyed that I can't play it on my m4 but I also understand that supporting macOS has always been a nuisance.
replyIf I were making games I wouldn't support it either. Apple does just about everything to not support backwards compat.
FWIW DF and DFHack work flawlessly through Crossover on macOS on my M2 and my M5
reply