Playing unlocalised games on a Mac fails in two different places, and they get conflated: the game fails to start (engine/build problem), or the game starts and you cannot read it (localisation problem). This post separates the two, with the concrete errors you actually see, and a workflow for the second case that does not break fullscreen.
Case 1: the game does not launch
Unity IL2CPP build fails or the player crashes on start. The IL2CPP backend generates C++ and compiles it; failures surface far from your C# code.
-
il2cpp.exeerrors during build: usually a missing or mismatched Burst/IL2CPP package for the editor version. Build the same project with Mono to confirm the code is fine and the problem is the backend. - Player crashes immediately after launch with a
Data folder not foundor "Unable to load player data": the build output was moved without its<GameName>_Datadirectory, or two builds were merged. -
DllNotFoundExceptionat runtime: a native plugin was built for the wrong architecture. On Apple Silicon check the binary withfileandlipo -info;x86_64-only plugins need Rosetta or a universal rebuild.
Steam launch fails with a bare error dialog. Three checks, in order:
- Steam's own log tells you more than the dialog:
~/Library/Application Support/Steam/logs/content_log.txtandbootstrap_log.txt. - Launch options can break a game silently. A stray
%command%fragment, a quoting mistake, or a leftover-dx11flag from a different machine is enough. Clear the field entirely, then re-add one flag at a time. - Verify integrity (
Properties → Installed Files → Verify integrity) after clearing launch options, not before — otherwise you re-download 20 GB to test a typo.
None of these need a translator. They need the log path and one variable changed at a time.
Case 2: the game runs, but you cannot read it
This is the more common complaint, and the usual fixes are all expensive:
- Phone camera OCR — one hand off the keyboard, autofocus hunting across a dark UI, and decorative serif fonts with drop shadows defeat most phone OCR.
-
⌘Tabto a browser translator — fullscreen state is lost, some engines only render dialogue while focused, and the line you wanted is gone when you come back. -
Copy-paste — most game UIs are rendered to a surface with no text layer.
⌘Creturns nothing. Same class of problem as a canvas-drawn Electron pane.
The constraint that matters is do not take focus from the game. That leads to a specific design: capture only a rectangle the player draws, recognise it locally, and show the result in a panel that does not activate.
⌃S → drag a rectangle over the dialogue
→ CGImage in memory
→ VNRecognizeTextRequest (on-device)
→ text → translation
→ floating panel, game keeps focus
Settings that matter for game text:
-
usesLanguageCorrection = false— item names and invented nouns are not dictionary words; correction rewrites them. -
minimumTextHeightexplicit — stylised display fonts have small x-height and get dropped under the default threshold. - Order
recognitionLanguagesby what you actually read.
Practical notes from use: select the dialogue box rather than the whole frame (HUD markers add noise), avoid selecting over animated particle backgrounds, and skip title art — decorative logos are where OCR fails first.
Honest limits
- Hand-written or heavily stylised display faces can fail
- Low-contrast subtitles over bright scenes are unreliable
- Text smaller than roughly 10px on a 1440p frame, unless you crop tighter
- Rotated or perspective-skewed UI text
- Anything that is not text: icons, minimaps, damage numbers
Also: recognition is local, translation is a network call. Offline you get OCR and no translation — often still enough to get unstuck on a quest log.
Links
16:9 walkthrough (Ep4, Steam English UI):
https://www.youtube.com/watch?v=2-t-IE345pI
Screen-OCR flow, direct download page:
https://www.zipp-mac.com/solutions/mac-screenshot-ocr-screen-translate/?utm_source=devto&utm_medium=article&utm_campaign=steam_unity_v2
Distribution page (BOOTH):
https://zipp-mac.booth.pm/items/9082185
Top comments (0)