Known issues & fix status

Reported  When learning Japanese, words made of several kanji are sometimes broken up in the wrong places, and the meanings shown for the pieces don't match the word as a whole. For a learner this can be misleading.

Why  Japanese has no spaces, so Playto has to decide where each word starts and ends. Long compounds are where that guess goes wrong most often.

What we're looking at  Showing where the words split when you retranslate a line, so you can see how a compound was read, and improving how compounds are kept together.

Reported  In RPGs, the same menu or status labels (items, skills, equipment and so on) come out with a different translation from one moment to the next.

Why  Each time a label appears, Playto translates it again on its own. Short words with little context around them are where the translation varies most.

What we're looking at  Keeping the translation of a label the same for the rest of the game once it has been translated.

Reported  When you press the audio button on a Japanese sentence, some kanji are read with the wrong reading, especially in long sentences.

Why  The same kanji can have several valid readings depending on context, and choosing the right one for every word is hard.

What to do  Audio is most reliable on single words saved to your wordbook. For pronunciation practice, check against a dictionary when a reading looks wrong.

Reported  The translation engine is stopped every time it starts, and verifying the game files on Steam does not help. CPU-only mode is stopped the same way.

Why  Windows Smart App Control only lets programs it already trusts run. It stops Playto's local translation engine (llama-server.exe and its DLLs) from starting, in every mode including CPU-only. This is Windows' decision about the files, so verifying them on Steam does not change it.

What to do

• Easiest: switch the engine to Playto Cloud (Settings → Engine → Cloud). It translates on our servers, so it works with Smart App Control left on, in both Playto Lite and Playto.
• To use the local engine instead, turn Smart App Control off: Windows Security → App & browser control → Smart App Control. Once it is off, Windows does not let you turn it back on without reinstalling Windows.
• If you use other security software (for example IObit Malware Fighter), add Playto's folder to its exclusions.
• If a model file was quarantined, restore it in your security software, then run Verify integrity of game files on Steam.

Note  Since v2026.1008.1851, Playto's own message for PLT-ENGINE-019 gives these same steps.

Reported  On Windows 10, stylized game fonts are misread more often than on Windows 11.

Why  Playto uses the Windows 11 text reader when it is available. Windows 10 doesn't have it, so Playto reads with the reader that ships inside the app instead.

What to do  Windows 11 is recommended. On Windows 10, the Image mode in the full version reads stylized text with a vision model instead.

Reported  A player following the tutorial could not find the Start button and stopped at step 3.

Where it is  In the Playto window, not on the game or on the practice scene. The tutorial opens a small practice window and keeps the tour card on top of it, so the Playto window can end up behind them. Click the Playto window to bring it forward and go to Home, the first item in the left sidebar. The Learning session card is in the middle of that page, and Start is the button on it — the tour draws a ring around it once the window is in front.

Reported  Started from Steam on Linux, Playto stopped with PLT-LINUX-002 "Required system libraries are missing" (for example libssl.so.3 or libbrotlidec.so.1), even though those libraries were installed.

Why  Steam started Playto inside the Steam Linux Runtime container, and from inside it Playto couldn't see the libraries installed on the PC.

Fix  Playto now ships the libraries it needs and runs inside Steam's Linux runtime. If you forced "Legacy runtime 1.0" under Properties → Compatibility as a workaround, you can untick it; Playto works either way.

Reported  On X11 desktops, and on GNOME (including Ubuntu's default desktop), Playto's window could stop updating right after it started. Clicks didn't change what it showed, and enlarging the window left a grey area. KDE Plasma on Wayland was not affected.

Fix  Playto now avoids this automatically. If you added WEBKIT_DISABLE_DMABUF_RENDERER=1 %command% to the launch options, you can remove it; keeping it does no harm.

Reported  No matter how the dialogue-box area was dragged, Playto did not take it and kept asking for the area again.

Why  A drag made on the preview inside Playto's start screen was saved as an area over Playto's own window instead of the game.

Fix  When you press Add or Redraw, a drag on the preview and a drag on the game screen both set the area, and the guide says so.

Reported  Playto sometimes froze and translation could not be stopped; the only way out was to quit from Steam and start again.

Why  In exclusive fullscreen, or with the game minimized, the screen capture can stall. Stop then waited for it without a time limit, so it never finished and the translation stayed on screen.

Fix  Stop no longer waits on a stalled capture without a limit: it gives up after about 2 seconds, so it always finishes. Pressing Start again right after Stop also works.

Reported  With a game that only offers exclusive fullscreen, the game minimized as soon as Playto's window was used, so the area could not be drawn and a Fixed Region session could not start.

Why  Some games minimize themselves whenever another window takes focus. While the game is minimized there is nothing on screen to draw on or read.

Fix  Playto keeps the last frame of the game and its position, so you can draw the area on that preview and start the Fixed Region session while the game is minimized. Reading begins once the game is back in front. If the game has a borderless or windowed option, it is still the smoothest way to play.

Since v2026.1006.2209

• Redrawing the area during a session (the bar's area action, Fixed on the learning bar and so on) opens the Region settings with the game's preview, and you draw there. The game is not minimized.
• With Start capture open, switch to the game and back, and the preview updates to the game's latest screen.

Reported  On a laptop with integrated graphics, the engine crashed several times every time Playto started, then fell back to the CPU. Each start took up to a minute and a half, and translation was slow afterwards.

Why  Some graphics chips can't use a memory-saving setting Playto turns on by default for the engine. The engine then failed on the graphics chip instead of running without that setting.

Fix  Playto now turns that setting off for such graphics chips and keeps translating on the GPU, and it remembers this for later starts. You'll see a one-time notice when it happens.

Reported  A request to show the translation overlay in OBS while streaming, including with Game Capture.

Now  Playto can put the translations on your stream as an OBS Browser Source, so you can keep Game Capture as your game source. In Playto, open Integration, press Start under OBS / Streaming and copy the URL into a Browser source in OBS. With Display Capture the desktop overlay is already part of the screen and shows up without any setup.

Reported  With Playto Cloud as the engine, pressing Start did nothing at all: no translation, no error, and the self-diagnosis finished with nothing captured.

Why  After a session ends, Playto fills in the meanings of the words you saved, and with Cloud that work was holding the next session back.

Fix  Filling in meanings no longer holds back a new session.

Reported  The app opened in English regardless of the system language, which made it hard to use for players who don't read English.

Fix  A new install now opens in your system language, Traditional Chinese included. You can still change it during setup or in Settings.

Reported  In a shooter, the resident bar took a click and paused the game, and there was no clear way to hide it.

Fix  The bar now steps aside while a game hides the cursor and comes back when you stop aiming. The × at its top right closes it; the Resident mode card on Home brings it back.

Reported  Quick Translate, the way to translate a region without setting up a game, had disappeared from Home.

Fix  It is back on the Learning session card. Drag a frame and translation starts right away; words you save still go to your wordbook.

Reported  The translation engine started but Playto gave up waiting for it, on GPU and CPU alike.

Fix  A system proxy or VPN was also capturing Playto's local connection to its own engine. Local connections now bypass the proxy; Cloud and downloads still use it.

Reported  On some PCs, translation never appeared after switching to a larger model.

Fix  A larger model can be too slow for some PCs to answer in time. Playto now says so and offers a one-tap switch to the included Hy-MT2, which answers in under a second on most PCs.