Visual Novel OCR Not Reading Text? Fix Capture and Dialogue Updates

Quick Diagnosis

A. Nothing Is Recognized

Lexa can only read text that is visible in the screen or window it is pointed at, inside the area of the mode you started. When nothing comes through at all, check the basics before changing anything else.

• The target: "Current screen" reads anything visible on that monitor, while a window picked under "Open apps" limits Lexa to that app. Make sure it is the monitor or window where the VN actually is.
• The mode: Realtime mode should be running with its frame over the dialogue box. If the frame label reads "PAUSED" instead of "REALTIME CAPTURE", select the resume button on the frame (its tooltip reads "Resume capture").
• The source language: in "Settings", under "Translation Languages", set "I see text on my screen in..." to the language the VN is written in, such as Japanese.
• The text itself: start from a scene where dialogue is on screen, not a title screen, movie, or transition.

Then test one fully displayed, stable line, which removes as many variables as possible:

1. 1

   Pick a stable, readable line

   Open a normal dialogue scene and stop on a short line in plain text that is fully displayed.

2. 2

   Turn off auto-advance in the visual novel

   Use the game's own setting while testing, so the line will not change mid-test.

3. 3

   Place the Realtime mode frame over the text only

   Drag the frame and pull its edges until it covers the dialogue text, not the whole screen.

4. 4

   Compare the panel with the screen

   With the original text showing in the Realtime mode panel, check whether it matches the line. If it does, the setup works and the problem is specific to the scenes that fail.

If the text is visible but the way the game draws it keeps OCR from reading it, a text hooker may work better for that particular title. The Textractor vs OCR comparison explains when that is worth trying.

B. Extra Menu Text or Unrelated Words Appear

If the frame also covers quick-menu buttons such as Auto, Skip, or Log, a clock, or text in the background art, those words end up in the recognized text and then in the translation.

• Drag the frame so it sits around the lines of dialogue text, inside the edges of the text box.
• Leave a small margin so the first and last characters of a line are not cut off.
• Keep quick-menu buttons and other interface text outside the frame wherever the layout allows.
• If the text box moves for narration or special scenes, move the frame for that scene instead of stretching it to cover every position.

For the speaker name, use the speaker area instead of enlarging the dialogue frame. On the Realtime mode capture border, select the person icon (its tooltip reads "Show speaker name area") and place the smaller "SPEAKER" area over the nameplate. The main frame can then stay on the dialogue itself, and Lexa remembers the speaker area's position for your next session.

Open larger view:

Open larger view:

Illustrative visual novel scene created for this demonstration. Both screenshots show actual captures and output from Lexa.

C. Characters or Words Are Missing or Incorrect

When the right area is captured but the original text has wrong or missing characters, look at the text as an image. OCR works from what is drawn on screen, so these are the things to check:

• Text size: very small characters are harder to recognize. If the VN has a text size or font option, try a larger setting. A bigger game window does not always mean bigger text, so check whether the characters themselves got larger.
• Contrast: light text on a semi-transparent box over bright art loses contrast. If the VN lets you change the text box opacity, try a more solid box.
• Background clutter: busy art, effects, or overlapping images behind the text can be read as extra marks. Tightening the frame around the text helps keep the area clean.
• Stylized fonts: heavy outlines, handwriting, decorative, or vertical text is harder to read than plain horizontal dialogue. If the game offers a plainer font, test it.

D. Dialogue Updates Seem Incomplete or Out of Sync

Realtime mode translates again whenever the text inside its frame changes. It is built to handle dialogue that appears character by character, but a line that is still being typed out can briefly show an earlier, partial version before the complete line comes through.

Fast auto-advance and moving elements inside the frame can also make the panel feel out of step with where you are in the story.

• Turn off auto-advance and skip in the visual novel while you test.
• If the VN has a text speed option, try a faster or instant setting so each line appears complete.
• Wait for the full line to be on screen before you advance, then compare the panel with the game.
• Keep animated elements, such as a blinking next-line arrow, outside the frame if the layout allows.

If a fully displayed, stable line comes through correctly but fast reading does not, the issue is pacing: give each line time to translate before moving on. If even a stable line comes through incomplete, go back to sections B and C. With "On this device" processing, how quickly each line is translated also depends on your computer.

E. Choices and Menus Are Outside the Dialogue Area

Realtime mode follows one area, and that area should stay on the dialogue box. Choices often appear in the middle of the screen and menus somewhere else entirely, so instead of moving or enlarging the frame, use the companion mode made for that text.

Keep Realtime mode as the main way to read, and reach for Cursor mode or Watch mode only when the text you need is somewhere else.

F. The Recognized Text Is Correct, but the Translation Is Awkward

If the original text in the Realtime mode panel matches the game, OCR did its part and the problem is machine translation. Names, honorifics, jokes, and route-specific terms are the usual trouble spots. A few tools can help:

• Link the visual novel in the "Info" tab of the Realtime mode panel, for example with "Link this VN" on a suggested match. Lexa matches character names against VNDB, and linking the right VN lets it use that game's character dictionary to resolve more names.
• Save a fix under "Translation fixes" in the same "Info" tab when a name or word keeps appearing untranslated. Lexa reuses your wording for that VN. The Free plan limits how many fixes you can save per visual novel.
• Select "Improve with Lexa" on a line that needs a second look. It needs an internet connection and uses one of your monthly Lexa Improvements.

These help with specific lines and names, but the result is still machine translation: it can miss nuance that a careful human translation would keep. Pro raises usage limits; it does not make recognition or translation perfect.

If It Still Fails

If none of the above helps, contact Lexa support through the options in "Settings", under "About". These details make the problem much easier to look into:

• Your Lexa version, shown in "Settings" under "About"
• The mode you were using: Realtime mode, Cursor mode, or Watch mode
• Your choice under "Realtime, Watch and Cursor processing": "On this device" or "Cloud"
• Your languages: "I see text on my screen in..." and "Translate to..."
• The game's display mode: Windowed, Borderless Fullscreen, or Fullscreen
• A screenshot of only the relevant area: the text on screen, the frame, and the panel

For how these modes fit together during a normal reading session, see the visual novel translator workflow.