-
-
Notifications
You must be signed in to change notification settings - Fork 1
Options
Here is a detailed description on what each option does within the dqxclarity
UI.
This uses the pykakasi library to scan for player names and translate them to their Romaji counterpart. Uses a little CPU as it's constantly scanning for player names to translate.
This downloads the latest game data files that contain all of the game's local English translations. It's recommended to keep this on, as translation work is ongoing and these files are automatically updated with the newest translations daily. If using this option, dqxclarity
must be opened as an administrator and Dragon Quest X must be closed before dqxclarity
is launched. Once you see "Searching for DQXGame.exe" in the Powershell window, you can launch Dragon Quest X and dqxclarity
will automatically activate once you reach the "Important Announcements" screen.
Checking this box, alongside setting up a translation service (explained below), allows you use API translated text that's inserted natively into the game's dialogue box. If for whatever reason you do not want to use this feature, leave it unchecked.
This will disable dqxclarity
from checking for any updates, as well as downloading any game data files or custom translation files.
Scans for both NPC and monster names from their respective translation files and translates them. Uses a little CPU as it's constantly scanning for names to translate.
Only enable this if you're interested in supporting the project. This provides lots of helpful logging for the dqxclarity
project to gather information about where the game files are stored. Provide a zipped up attachment of your logs
folder to anyone in the Discord and we'll happily grab it from you!
Provides more verbose logging in the out.log
file, especially when using the API Dialogue Insertion feature. If you are running into errors when running Clarity, it's recommended to turn this on for better troubleshooting.
Click this button to set up the translation service you will use for API Dialogue insertion. Make sure you check only one of the translation service boxes - not both. This is also where you put your DeepL or Google Translate API key. You'll see "API Functionality Enabled!" on the GUI when this is set up correctly.
This enables the functionality to insert API translated text natively into the game's dialogue box. This translates a large majority of dialog in the game that isn't picked up from the previous options. It will either use the translated files we have now, or in the case we don't, it will send the text to the translation option you checked for translation and write it to memory. In order to use this, you must enable a translation service with the "API Service Settings" button. By not setting this up, a majority of NPC dialogue will remain in Japanese, but some facility NPC dialogue and all cutscenes will still display in English.