itch.io

So sorry to have been the bearer of bad news about my testing, the game does work great once I've ad hoc signed it. Hopefully other Mac users can make use of a signed copy of DOSBox Staging for this.

Incidentally, ad hoc signed (run with `-s -` on codesign, after assembling it) does still show a "damaged" notice on machines other than the one it was assembled on, but usually lets you override it, either with right click / ctrl click running, or with the Security preferences page showing a notice for the last security failure and a button to authorize it, and it does remember until the app signature changes, ie. replaced or upgraded. I don't *think* it minds the profile file being inside the app bundle, but I could be wrong.

Love the game, it's pretty fun!

I just tested this on my Apple silicon Mac (M1 mini) and it doesn't run even if I right click it. I had to manually ad hoc sign it to allow it to run, because Apple silicon outright requires signatures even on your own local builds to run them. In fact, Xcode ad hoc signs everything it links these days. (I've been told I overexplain things, sometimes even to people who already knew those things. Maybe it's sometimes helpful for information to be available in lots of places, though. Especially with Google circling the drain as it is.)

I'd be willing to help with notary signing, but you should probably do that yourself if you can afford it, since the signature does expose the name of the person or team that signed the app, unless you're using ad hoc signing, then it's an anonymous machine specific signature.

Just a minor hint that seemed to pop up when I was checking the signature myself, it seems it may be objecting to a signature having been applied to the DOSBox bundle prior to the settings files and resources being inserted. It needs to be re-signed after everything is embedded proper. Hope this helps somewhat. (And this would definitely be breaking the ad hoc signing if you were just using the link time auto signing of the bundle.)

Replying to OP and the author with the absolutely wacky controller input behavior of the Xbox Series X|S controller under macOS Big Sur.

All of the inputs appear to behave as expected and push either analog sticks or buttons. Except for the Analog Triggers, which appear to do nothing under A Short Hike's input detector.

Worse still is the digital pad, which does weird things. It appears to be fed to A Short Hike under its distributed version of Unity as two analog axes, A4 and A5.

The default state of the D-pad is A4 centered, A5 negative.

Pressing the pad up: A4 positive, A5 negative.

To the upper left: A4 centered, A5 centered.

To the left: A4 negative, A5 negative.

To the lower left: A4 negative, A5 centered.

To the bottom: A4 negative, A5 positive.

To the bottom right: A4 centered, A5 positive.

To the right: A4 positive, A5 positive.

To the top right: A4 positive, A5 centered.

The unpressed state of A5 being negative causes the controller input to break analog presses. The confusing mapping of the d-pad breaks it period.