# TextractorCLI TextractorCLI is a third-party integration. VNTranslator does not provide support for game-specific hooking issues. For problems related to text extraction from specific games, please refer to the [Textractor GitHub Issues page](https://github.com/Artikash/Textractor/issues). ## Error Dialog: "Textractor ERROR"

Textractor ERROR

* Check the [Textractor GitHub Issues page](https://github.com/Artikash/Textractor/issues) for known problems with your specific game * Search for your game title or error message to find solutions from the community * Make sure you're using the correct architecture (x86 vs x64) for your game *** ## Smart Filtering Window is Blank / No Text Appears #### 1. Do not run Textractor.exe while using TextractorCLI VNTranslator automatically launches `TextractorCLI.exe` to hook game text. If you manually run `Textractor.exe` at the same time, it will cause a conflict because both programs try to use the same text extraction pipeline. This prevents the text from being sent to VNTranslator. #### 2. Run VNTranslator as Administrator Text hooking requires elevated permissions to inject into game processes. #### 3. Add TextractorCLI.exe to antivirus exceptions Antivirus software often blocks text hooking programs because they inject code into running processes. #### 4. Verify the TextractorCLI path is correct Make sure the path in VNTranslator settings points to the correct TextractorCLI.exe file. **Example paths:** * `C:\Textractor\x86\TextractorCLI.exe` (for 32-bit) * `C:\Textractor\x64\TextractorCLI.exe` (for 64-bit) #### 5. Ensure your game engine is supported Not all game engines are compatible with Textractor. Check the [Textractor GitHub Issues page](https://github.com/Artikash/Textractor/issues) to see if your specific game or engine is supported. *** ## **Newer Visual Novel Games Not Working** Textractor is no longer actively developed, so some newer visual novel games may not work with the current version. **Solution:** Update the `texthook.dll` file in your Textractor installation folder with a newer community-maintained version. *** ## Testing TextractorCLI

Console

You can verify if TextractorCLI is working correctly by running it manually: * Open the Run Command (Windows key + R) * Type the path to TextractorCLI.exe: * `C:\Textractor\x86\TextractorCLI.exe` (for 32-bit) * `C:\Textractor\x64\TextractorCLI.exe` (for 64-bit ) * Click **OK** to confirm * Check the output\ If TextractorCLI is working correctly, you should see output like this in the console window:`[1:0:0:FFFFFFFFFFFFFFFF:FFFFFFFFFFFFFFFF:Clipboard:HB0@0]`\ If the clipboard address appears in the console, TextractorCLI is functioning properly. *** ## **Additional Troubleshooting Tips** * **Game crashes when hooking:** Try using a different architecture (x86 vs x64) or check if the game has anti-cheat protection * **Garbled or duplicate text:** Use the Smart Filtering feature in VNTranslator to filter out unwanted text threads * **No hooks detected:** Some games require custom H-codes. Search for your game on the Textractor GitHub Issues page or VNDB to find working H-codes * **Still having issues?** Consider using the Clipboard Integration method as an alternative, which is often more stable --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vntranslator.com/help/troubleshooting/textractorcli.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.