Tool RPGM SLR/DSLR/SEP - Translation Engines for RPG Maker VX, VX Ace, MV, MZ, and Pictures

[Shisaye]

Overview:
SLR Translator is a tool I've been developing over the past few years to translate RPGM games at a high enough standard to be able to finish them without getting stuck.
(This will actually work on a fairly old laptop as long as it doesn't overheat.)
You can find countless translation examples in my main translation thread.
If you've ever used Translator++ before, then the tool will immediately feel familiar, because I am using it's UI licensed under GPLv3.
But the actual translation process is very different from Dreamsavior's stuff.
Most outside credit there actually goes to Reddo9999, his code helped me a lot.
(We don't know each other, but his code is also licensed under GPLv3.)
Also includes the DSLR Translation engine to use whatever AI (LLM) you want as long as its api supports 'v1' or 'v4' requests.
(Pre-configured for a free LM Studio setup using Qwen3VL.)
As well as the SEP picture translation system to be able to translate picture based text offline in bulk.

Spoiler: Regarding Premium Features and Company Payment (Is SLR Translator really free?)

You don't have permission to view the spoiler content. Log in or register now.

Important Notes:
Press F1 with the tool open for tutorials on how to use this.
SLR will only function if you have a working SugoiV4 server running locally on the default port 14366.
You can visit

You must be registered to see the links

, or the F95 Sugoi thread to find out more about Sugoi.
The V9-V9.4 Toolkits are not compatible with SLR, but 9.5 works again.
DSLR does not require SugoiV4, but requires manual setup, read the manual.
SEP technically works on its own, but it's strongly recommended to increase the quality of the result by using a vision enabled LLM.
RTFM.

If you'd like to support development of this tool or my work in general you can donate here:

You must be registered to see the links

Developer: Shisaye
Version: 2.051
Requirements: Windows (64bit), At least 8GB of RAM.
For free local use of DSLR at least 4Gb of VRAM on a CUDA/VULKAN capable GPU.
For decent results with SEP at least 24GB of RAM or 16Gb of RAM and 8GB of VRAM on a CUDA/VULKAN capable GPU.

Installation:

Spoiler

You don't have permission to view the spoiler content. Log in or register now.

Changelog:
See attached "Changelog.txt".

Preview Screenshots:

Spoiler

You don't have permission to view the spoiler content. Log in or register now.

FAQ:
Q: A game is not working correctly after translation, or the translator has problems during the translation of a game, what do I do?
A: Please post the DLsite code of the game (or it's full name), a screenshot of the problem, and a description when exactly the problem occured. If appropriate please also include a save file to reproduce the issue in-game.
Please do not include any rule breaking content in your post.

Q: So this is just another way to run Sugoi on a game?
A: No, Sugoi is only used for basic dialogue. Most scripts, noises, menu buttons, etc., have pre-defined translations from a dictionary I've built. There's also hundreds of regex patterns fixing common quirks and issues with Sugoi.

Q: When I use SLR on a cell why do some parts remain Japanese and what is this SLRContextID?
A: If there's leftover Japanese that means those parts have preset translations, or are script commands that need to remain Japanese. The SLRContextID is a measure against de-duplication.
Just click the "Fix cells and check for errors" button and the Japanese that can be translated will be replaced and the SLRContextID will be removed. (The Japanese replacement only works in the Initial Translations column to prevent it from touching manual edits.)

Q: Translator++ translation constantly crash games, so this does the same?
A: This is not using T++ parsing or converting. I'm just using its UI. Even old VX/Ace converts and exports correctly in SLR Translator, and as a result this does not have the crashing issues T++ has. (But only if you actually follow the process outlined in the help menu and don't expect this to be an idiot proof one click translation tool.)
Also SLR Translator does not just group similar cells together causing scripts and dialogue to be handled the same. Tagging is actually accurate.

DOWNLOAD
SLR Translator

You must be registered to see the links

You must be registered to see the links

SHA-256 of the archive:
8137346faf026aee42f2f5236506d15ea342ba4234f842144f106ea2d4662a14

Additional Tools:
(Extractors, Editors, etc. Also includes a minimalist Sugoi Repack.)
(I did not make any of these.)

You must be registered to see the links

You must be registered to see the links

SHA-256 of the archive:
61bfb54dc700ecd875a0d28fd10d032058db4b901bc191ddbd2257008c926f3b
​

 

[Shisaye]

To everyone using SLR translator, just to say it again in a more clear fashion.

If you've made a translation, regardless if you think it's bad, regardless if you think it's too incomplete, heck even if it has minor crashing issues:
Please actually publish the translation.

SLR Translator was never meant for individual throwaway translations.
The point was to enable even someone with no coding skills whatsoever to keep the translation train rolling and get rid of the last bit of untranslated games, no matter how niche and hopeless they seem.

While I'm at a good pace, having made over 400 translations over the past 4 years, games still release every day, and there's still hundreds of untranslated ones out there that could at least use "some" translation.

If you wouldn't know where to post them or it seems like a really stupid process. Just dump them in the "mini releases" section of the anime-sharing (.com) translation section. I do not enforce any formatting rules there.
Just make a thread, name it after the game, and put your translation patch in there. You can obviously add more information, but you do not have to.
Heck, if you for some reason can't even be arsed to go to anime-sharing, just dump your translation in my translation collection thread or PM it to me and I'll make the thread for you. But please do not post anything in there that violates the rules of F95.

Also tell me about failed translations, because then there's obviously an issue with the tool that I need to fix. Don't just delete it and move on.

 

[Entai2965]

​

Best Mascot Ever.

Edit:
SLR Translator has a lot of optimizations based around Japanese to English translation + the Sugoi Offline Translator v4.0 NMT model. The Sugoi Offline Translator v4 NMT model is included in Sugoi Toolkit v6-v8+.

Using SLR Translator in its intended configuration requires:
1) The Sugoi Offline Translator v4.0 model in either

You must be registered to see the links

or in

You must be registered to see the links

.
2) Software that can run that model on either the CPU or GPU.

The PyTorch/Fairseq/original version of the model and a small flask server to run it are available from the Official Toolkit (~6.5+ GB), but FOSS alternatives are also available here for convenience, reduced size, better performance, improved compatibility, added cache, added UI, transparency, stability, etc.

I went ahead and bundled everything together in a Sugoi-Repackage to bootstrap the Sugoi Offline Translator v4.0 NMT model + SLR Translator as fast, as clearly, and as reliably as possible. The Sugoi-Repackage is already included under AdditionalTools.7z\apps\Sugoi-Repackage-CPU in the OP. Just double click on the .bat to set up the software and then add the CTranslate2 format model to the correct folder to begin using SLR Translator right away.

Spoiler: Sugoi-Repackage Installation

You don't have permission to view the spoiler content. Log in or register now.

For more detailed notes on the Sugoi-Repackage, see the

You must be registered to see the links

, expand the small summary below, and also read this.

Spoiler: Background information

You don't have permission to view the spoiler content. Log in or register now.

Edit2: This thread is to discuss SLR Translator. To discuss the repackage, please use the repackage

You must be registered to see the links

or the Sugoi thread.

 

[nicolasdesmond]

Can't open localhost

 

[Shisaye]

Can't open localhost

Localhost refers to your own computer.
What I meant is that you need to have SugoiV4 running in offline mode on the standard server settings.
(I've now changed the note to be less confusing.)

If you have no idea how any of that works, then you can just use the standard Sugoi toolkit by minshiba, run it in offline mode, and leave everything on default. It might be a bit slow, but it will do the job.

I just mentioned the port, because some of the more advanced Sugoi setups might use a different number, and then it will not properly communicate with SLR Translator.

 

[Silentce]

Good job on the tool. I plan on checking it out. My knowledge of coding sucks but I am eager to see how the process works. might make me start doing translations again as I could focus on editing the results instead of spending 6 years translating everything by hand lol.

 

[Shisaye]

Good job on the tool. I plan on checking it out. My knowledge of coding sucks but I am eager to see how the process works. might make me start doing translations again as I could focus on editing the results instead of spending 6 years translating everything by hand lol.

I'm planning to add proper documentation for everything, but I'm really bad at that stuff, so for now there's only tutorials for basic usage, and some explanations for error codes and cell tags. (Press F1 in the tool.)

I've tried to put explanations in the code everywhere, but it's a mess.

The most important bits are actually in the TransRedBatch and TransRedSugoi folders in www/addons. Specifically the "TranslationEngineWrapper.js" and the "transredbatch.js". That's where all the magic happens.

Not because that makes a lot of sense, but because I started with Reddo's stuff back then and never bothered to actually move it out of there.

But I obviously also made changes to the core parsers and even to stuff like rvpacker.
(As you know, all the normal Translator++ stuff is broken. I basically had to edit every single file at some point.)

 

[Shisaye]

Since I never had a thread in this section, yet, did anyone get a notification when I edited the OP for the 1.043 update and then 3 days later for the 1.044 update, or do I have to make a post each time I release an update?

 

[Silentce]

Since I never had a thread in this section, yet, did anyone get a notification when I edited the OP for the 1.043 update and then 3 days later for the 1.044 update, or do I have to make a post each time I release an update?

Gotta make new posts. updates to previous posts do not trigger notifications as far as I am aware.

 

[Shisaye]

Gotta make new posts. updates to previous posts do not trigger notifications as far as I am aware.

Odd choice, makes the "Watch Thread" function not super useful.
Oh well, I guess I spam new posts each time then.

 

[Shisaye]

I've released Update v1.045.

Main change is that it will now put a non breaking spaces in D_TEXT entries if they end on a number that is encased.
Because for some dumb reason D_Text accepts \V[n] as font size if there's a space in front of them.
Which means if there's a menu entry "Money \V[12]" Instead of printing "Money variable12" it scales the font size of the word Money.

Which is kinda funny, but I've fixed it now.

It probably only works with that variable type, but just to be safe I changed it for all encased numbers at the end. (It just makes the text a bit ugly when it happens, because the spaces are bigger.)

 

[Shisaye]

I've released v1.046.
Tagging related improvements and fixes, mostly related to the scripts context and plugins.js.

The Additional Tools package now includes a minimalist SugoiV4 installer. (Made by a certain 2965 pokemon ).

Edit: I may or may not have had a really dumb typo. Anyways there's v1.047 now.

 

[Shisaye]

Just released v1.048.
Biggest change is that I significantly improved my script for detecting and deleting empty objects and their staging data.
It should now consistently work regardless of project or settings.

 

[Shisaye]

Btw I completely forgot to mention, regardless of what I've changed in a new version, you can move over your staging data from the www/php/cache folder into the new version and it will retain all information it had (outside of your profile folder in Appdata).
That way old projects will still work as expected and you do not need to keep old versions of the tool.

I thought about offering update patches instead of always the whole thing again, but that just introduces another instance in which I could fuck something up, so I'd rather not.

 

[Shisaye]

I've released v1.049.
Fixed a problem with some old escaper patterns that was causing bad translations.
This actually makes a significant difference in translation quality for some games.

 

[Shisaye]

I've released v1.050 because sleeping is overrated.

Main changes are to make the error detection system more accurate and VX plugin stuff.
If you have used SLR Translator before v1.050, then you might want to delete your profile folder in "Appdata/Local/SLR Translator", so it applies the new default settings, unless of course you already made a bunch of changes to the settings and you want to keep them.
But I recommend changing these settings

To something more spicy like Request Character Limit 5000 and Maximum Batch Size 15000.
Otherwise translation will be really slow.


And yes, I've also just noticed the typo in the description... I'll fix it in the next update.

 

[Yuki-x]

Shisaye
Does your tool have the same feature/enhancement (for me is a flaw) of grouping all identical strings in one string with multiple references, as translator++?

 

[Shisaye]

Shisaye
Does your tool have the same feature/enhancement (for me is a flaw) of grouping all identical strings in one string with multiple references, as translator++?

It does do that, but for automated RPGM translation it's not a problem because It's not blindly collecting everything like Translator++ does. My parser is more selective.
It doesn't really make sense to make 30 cells with just the word "Yes" in it, to be processed one by one, if they are all choice boxes, and all in the same object.
This isn't really meant for manual translations.

I might make a toggle in the options menu at some point, but that's actually more annoying to implement than it sounds.

Edit: If you find an instance of SLR Translator actually grouping a cell that breaks the game if translated with one that needs translation, please tell me and I'll adjust the parser to not collect the untranslatable cell in the first place.
Edit2: I'm working on an experimental option to fully disable de-duplication of cells in v1.130. Working with LLMs that need context made me realize how much of an issue it is, but also how much dreamsavior baked it into the UI. It's actually really hard to get rid off.

 

[Shisaye]

Released v1.051.
Just some minor bugfixes.
I've also added a download mirror using wdho, which is probably not everyone's favourite host, but it seems like Pixeldrain is getting problems soon, so I should at least have some mirror and the host options are starting to be really limited...

 

[Shisaye]

I've released v1.052.
Fix for a niche crash and some minor translation improvements.