Known Issues

What you'll see   When you press the audio button on a Japanese sentence, the text-to-speech engine reads kanji with incorrect or inconsistent readings. In long sentences, this can result in playback that does not sound like natural Japanese.

Why   Japanese kanji-to-reading conversion is hard — the same character can have multiple valid readings depending on context, and the current TTS pipeline does not yet use a full Japanese morphological analyzer for pronunciation.

Workaround   For now, audio playback is most reliable on single words saved to your dictionary rather than full sentences. Pronunciation for learning practice is best verified against a native dictionary entry.

What you'll see   The model download during setup or from the Models page crawls or stops, mainly on connections in China, Hong Kong and Taiwan.

Why   Downloads try several sources in turn, including a mirror in the region, and some connections there are slow to every source. The default translation model now ships inside the installer, so translation works before any download finishes; the larger models still have to come down.

Workaround   Press Download again and it resumes from where it stopped. Keep Playto open while it runs. The Models page also lists where each file goes with a direct link, so you can download with another tool and place the file yourself.

What you'll see   On a fresh install, tapping a word for its meaning shows a prompt saying a larger model is needed, every time, for a while.

Why   The translation model that ships with Playto (Hy-MT2) only translates. Word meanings need the larger general model, which downloads in the background after setup. Until that download finishes the prompt keeps appearing. This is our design problem, not your machine.

Workaround   Open Settings, then Engine, to see whether the download is still running. Since the September update the download starts from that dialog and shows its progress there.

What you'll see   Translation never starts, or a model that was downloaded is reported missing or corrupt. Windows may have shown a security notice at the time.

Why   Some Windows security features, Smart App Control among them, block the translation engine from running or move a model file into quarantine.

Workaround   Playto now detects this and shows the recovery steps in place: allow the app in Windows Security, restore the file from quarantine if it was moved, then use Steam's Verify integrity of game files to restore anything still missing.

What you'll see   The engine status stays on failed or keeps restarting, and no translation appears.

Why   Several causes look identical from the outside: a damaged file, a GPU driver the engine cannot use, an overlay layer injected by another program, or a security block like the one above.

Workaround   First run Steam's Verify integrity of game files on Playto. If it still fails, run Self-diagnosis in the app, which tests the engine start in two stages and names the one that stopped, then send a report from Contact us. The report includes the engine log we need.

What you'll see   On Windows 10, stylized game fonts are misread more often than on Windows 11.

Why   Playto uses the Windows 11 OCR engine when it is available. On Windows 10 it falls back to the standard Windows OCR, which is weaker on decorative fonts.

Workaround   Windows 11 is recommended. On Windows 10, the Text+ and Image modes in the full version read stylized text with a vision model instead.