TOEM 2 Demo Not Working — Mac Crash & Bugs
The macOS build of the demo has a confirmed crash on the first photo, acknowledged by the developer in the Steam forums. Other reported issues are listed here with their sources.
The short version
If the TOEM 2 demo crashes on your Mac the moment you take your first photo, it is not your machine. The developer has publicly acknowledged the macOS build is rough.
Everything below is sourced from the official Steam discussion board for TOEM 2, read on August 19, 2026. Where something is a player report rather than a developer statement, this page says so.
macOS: crash when taking the first photo
Status: acknowledged by the developer, no fix confirmed.
A player reported on June 7, 2026 that on macOS Sonoma 14.8.7 running on an Intel MacBook Pro, the demo launched and ran fine — but crashed consistently when they tried to take their first photo of the critter in the opening zone, making it impossible to continue.
Something We Made replied on the same thread, the same day, with the developer tag on their account:
Thanks for the input & Sorry about the crashes, the macOS is a bit of rushed build from our side!
A second player followed up on July 11, 2026 reporting the same crash on an Intel Mac running macOS Sequoia 15.7.7, and asked whether a new build was coming. There is no developer answer to that follow-up on the thread.
A separate thread titled "Doesn't work on MacOs anymore" is the most-replied thread on the board, which suggests this is not an isolated case.
What you can do: there is no published workaround. If you are on a Mac and want to try TOEM 2 before buying, the practical options are to play on a Windows machine, or wait — the full game releases September 29, 2026, and the demo build is separate from it. The Steam macOS requirements for the full game currently read "TBD", so Mac support at launch has not been detailed either.
macOS: incorrect compatibility warning
Status: player report, plausible.
The same June 7 thread reported a second, smaller issue: the demo's Steam page displayed a warning that it does not support macOS Catalina (10.15) and above — which on Steam indicates a 32-bit-only application. The player noted this is inaccurate, since they were able to run it on a 64-bit system.
This is a store metadata problem rather than a game bug. If you saw that warning and skipped the demo because of it, that is why.
Photos not saving after quitting
Status: player report, no developer response on the thread.
One thread reports that photos taken during a session are not present after quitting and relaunching. No reproduction steps, affected platform or developer reply are attached to it, so it is listed here as an open report rather than a confirmed bug.
If this happens to you, the demo does support Steam Cloud and save-anytime, so it is worth checking whether Steam Cloud sync completed before you closed the game.
Everything renders purple
Status: player report.
A thread titled "Everything is purple" describes a display problem. In game development, magenta or purple surfaces are the standard placeholder for missing or failed-to-load textures, which usually points at a graphics driver or shader compilation issue rather than a broken install.
No developer response is attached. The usual first steps for this class of problem — updating graphics drivers, verifying the game files through Steam — are worth trying, but neither has been confirmed to fix this specific case.
Reporting a new problem
The developer is demonstrably active on the Steam board — they replied to the macOS report within about twenty minutes. The two places to report:
Including your operating system version, hardware, and the exact point where the problem happens is what made the macOS report actionable — the reporter named their macOS version, their Mac's processor architecture, and the precise action that triggered the crash.
A note on this page
None of the above is a "known issues" list published by the developer — no such list exists. This page collects what players have publicly reported and marks which items the developer has responded to. The macOS crash is the only one with a direct developer acknowledgement; the rest are reports.