Saltar al contenido principal

Getting Started

Prerequisites​

Before using the AI Localization Automator, ensure you have:

  1. Localizable Content: Text properties marked as localizable in your project
  2. Localization Target: A configured localization target with gathered source text
  3. Target Languages: At least one non-native culture added to your localization target
  4. AI Provider Access: API key or access to your chosen AI translation service
New to UE Localization?

If you're not familiar with making text localizable in Unreal Engine, start with our Localization Setup Guide to learn how to create and configure localizable text content.

Accessing the AI Translation Manager​

The plugin integrates directly with Unreal Engine's Localization Dashboard:

  1. Open the Localization Dashboard (Tools → Localization Dashboard)
  2. Select your localization target
  3. Look for the "AI Translate" button in the target toolbar
  4. Click the button to open the AI Translation Manager

Target Requirements

The AI Translate button only appears for non-engine localization targets that have gathered source text and target cultures configured.

Initial Configuration​

When you first open the AI Translation Manager, you'll need to configure your translation provider:

1. Select Translation Provider​

Choose from the available AI providers in the dropdown:

  • Ollama: Run locally for privacy and no API costs, requires local setup
  • OpenAI: Best overall quality, requires API key
  • Anthropic Claude: Excellent for nuanced translations, requires API key
  • DeepSeek: Cost-effective option, requires API key
  • Google Gemini: Good quality with competitive pricing, requires API key

2. Configure Provider Settings​

Each provider has different configuration requirements and options. While the interface provides helpful hints when you hover over each parameter, for comprehensive details on all available settings and configuration options for each specific provider, see the Translation Providers guide.

Cloud Providers (OpenAI, Claude, DeepSeek, Gemini) typically require at minimum an API Key for authentication, along with various other configuration options like model selection, temperature settings, token limits, and request timeouts.

Local Providers (Ollama) require at minimum a Base URL and Model to be specified, plus additional parameters for fine-tuning the local service.

3. Customize Translation Settings​

Configure the translation process behavior:

  • Max Concurrent Requests: Number of simultaneous translations (10 recommended to start, though some providers may require lower values - for example, Ollama typically works best with 4 max requests due to local processing limitations)
  • Max Attempts Per Translation: Retry limit for failed translations (2 recommended)
  • Max Consecutive Failures: Stop threshold for consecutive errors (6 recommended)

Your First Translation​

With configuration complete, you're ready to translate:

  1. Review Content: The translation table shows all discoverable text entries
  2. Check Status: See which translations are pending, completed, or failed
  3. Start Translation: Click "Start Translation" to begin the process
  4. Monitor Progress: Watch real-time progress updates and status messages
  5. Save Results: Use "Save Translations" to commit completed work to archive files

Complete the Localization Process​

After saving your translations, you need to complete the UE localization workflow:

1. Return to Localization Dashboard​

Close the AI Translation Manager and return to the Localization Dashboard.

2. Gather Text and Verify Results​

Click the "Gather Text" button and wait for the process to complete. This updates the localization system with your new translations. Once gathering completes, check that the Word Count statistics show your updated translations - you should see increased translation percentages for your target cultures.

3. Compile Text​

Click the "Compile Text" button to finalize the translations. This creates the binary files that your game will actually use.

4. Package Languages for Distribution​

After compiling text, to ensure translated text appears in your packaged project:

  1. Open Project Settings (Edit → Project Settings)
  2. Navigate to Packaging section in the left sidebar
  3. Expand the Advanced category in the Packaging settings
  4. Find "Languages to Package" field
  5. Click "Show Localized" radio button to display only previously localized languages
  6. Select languages to package - you can click "All" on the right side of the "Select" textbox to select all localized languages
  7. Package your project - the specified languages will now be included and available as localization options in your game

Project Settings - Languages to Package

This step is essential for making your translations available in the final packaged game.

5. Test Your Translations​

Once compilation is complete, you can test and preview your translations in the editor or game. For detailed instructions on testing localization, see our Testing Localization Guide.

Next Steps​

First Run Recommendation

Start with a small subset of text (perhaps 10-20 entries) to test your provider configuration and ensure translations meet your quality expectations before processing large batches.