This update is mostly about one thing: translation that stops mid-session and never comes back.
When the engine stops, translation comes back
Until now, if the local AI crashed or quietly stopped answering while you were playing, Playto kept capturing and showed nothing. You had to notice it yourself and restart.
Automatic recovery — if the engine dies during a session, Playto restarts it once and tells you on the overlay.
Silent stalls are detected — an engine that is still running but has stopped answering is now caught too, not just one that crashed outright.
No more restart loops — Playto no longer mistakes an engine that is still starting up for a dead one, which could restart a perfectly healthy engine over and over.
Fewer false alarms — the "translation is taking a while" warning no longer appears while translations are actually showing up.
Readings are easier to see
Furigana and pinyin now appear in the dictionary popup examples and in the context block in Words, not only in the log.
Readings now have a minimum size and will not shrink with the text until they are unreadable.
Japanese and Chinese source text in the log has been resized so it sits better next to the translation.
Larger interface
UI scale now goes up to 200%, from 150% before. Settings, Advanced, UI Scale. If text is too small on a high-resolution display, this is the setting to change.
Downloads
Stalled model downloads are now detected, and the download retries instead of sitting at the same percentage.
Progress no longer drops back to zero when a download retries.
Download errors are shown in your language instead of raw technical text.
Also in this update
Overlay notices are now translated into every supported language.
When the engine fails to start, the suggested actions — retry, switch to Vulkan, switch to CPU — stay on screen instead of being pushed off the edge.
Known issues
Cloud translation is not reliable yet — some users and regions still see connection failures. We are investigating and it is our current priority. Local engines are not affected.
If something is not working, use Help and support, Contact us, and tick the diagnostics box. Reproduce the problem first, then send within about ten minutes without restarting Playto — the diagnostics only cover what just happened.
playto.dev →