Field Report / Troubleshooting Log — 60 Seconds! Reatomized (game) on macOS
I wanted to replay 60 Seconds! Reatomized on my Mac. Nothing heroic. Just a late evening, headphones on, and the plan was to see how long I could keep the family alive before everything inevitably went sideways. I’m on macOS Sonoma 14.3, MacBook Pro with an M1 Pro. This should have been a five-minute install and launch.
It wasn’t.
The install itself looked fine. Download completed, app icon in Applications, everything where it should be. I double-clicked. Bounce in the Dock. One bounce, two bounces… then nothing. No crash dialog, no error message, just silence. The Dock icon disappeared like it never existed.
First reaction: blame the system
My first instinct was Gatekeeper. That familiar macOS move where it decides today is the day it doesn’t trust something it happily ran last year. I checked System Settings → Privacy & Security, scrolled down, half-expecting the usual “app was blocked” message. Nothing. No “Open Anyway” button, no warning, just a clean page.
I tried again. Same result. Dock bounce, vanish.
Second attempt was the classic reboot. I didn’t expect miracles, but I’ve been doing this long enough to know that sometimes macOS just needs a nap. Rebooted, closed everything else, launched again. Same behavior. At this point it felt less like Gatekeeper and more like the game choking very early in startup.
Logs don’t lie (even when they’re vague)
Next stop: Console.app. I filtered for the process name right after launching. There it was—an entry about failing to load a dynamic library, followed by a quick exit. No friendly explanation, but enough to tell me this wasn’t a permissions popup issue. It was dying before it could even complain.
I briefly went down a dead end reinstalling the game. Full delete from Applications, cleared related folders in ~/Library/Application Support, downloaded again, repeated the ritual. Same outcome. Clean install, clean failure.
At this point I suspected Rosetta. The game is Intel-only, and while Rosetta usually just works, “usually” is doing a lot of work in that sentence.
What actually helped
I forced the issue. Right-clicked the app → Get Info → checked “Open using Rosetta.” I normally avoid this unless needed, but here it was worth a shot. Launched again.
This time the Dock icon stayed. The screen went black for a second, then the intro appeared. Music, menu, animations—all fine. No stutter, no graphical glitches. It just worked.
Out of curiosity, I unchecked Rosetta and tried again. Back to bouncing and disappearing. Re-enabled it, instant success. That was the missing piece.
For reference, Apple’s own notes on Rosetta behavior explain why some older binaries need explicit translation enabled on Apple silicon machines:
https://support.apple.com/en-us/HT211861
and the developer-side explanation of how macOS handles Intel apps under the hood helped confirm my suspicion:
https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment
Once it launched properly, performance was solid. CPU usage stayed reasonable, fans stayed quiet, and load times were exactly what I remembered from earlier macOS versions. No weird audio lag, no input delay.
One more small hiccup
After about twenty minutes, the game failed to save progress. No error message, just no save file next launch. This one turned out to be simpler: Full Disk Access. The app didn’t have it, and Sonoma is stricter about write permissions than older releases.
System Settings → Privacy & Security → Full Disk Access → add the game manually. Relaunch. Saves started working immediately. Apple’s documentation on privacy permissions is dry but accurate here:
https://support.apple.com/guide/mac-help/control-access-to-files-and-folders-mchld5a35146/mac
Somewhere in the middle of all this, I bookmarked this page because it was useful for keeping track of macOS quirks and compatibility notes across different setups: https://stmlare.xyz/game/80711-60-seconds-reatomized.html. Not magic, just handy context while troubleshooting.
What I’d do if I started over
If I were doing this fresh on an Apple silicon Mac, I’d skip the reinstall loop entirely.
I’d install the game, immediately enable “Open using Rosetta,” then check permissions before even launching. That would have saved me a good half hour of poking around logs and pretending the reboot was going to help.
Quick mental checklist for next time:
- Enable Rosetta explicitly for older titles.
- Check Console early if the app vanishes without errors.
- Verify Full Disk Access if saves mysteriously don’t exist.
- Don’t assume silence means Gatekeeper.
After that, the game runs exactly as expected. Which is all I wanted in the first place. The apocalypse is stressful enough without macOS adding its own survival mechanics.
Top comments (0)