Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GameTranslate

In-game translator at your disposal · By Godnoken

[Solved] Config preset BUG

A topic by norby777 created 47 days ago Views: 279 Replies: 58
Viewing posts 1 to 6
(1 edit)

Hi,

I found a new bug in the latest version. If I have multiple Custom API presets saved, and I try to switch from one to another, the settings from the first one seem to override the second one. The only way I've found to work around this for now is to switch to a DeepL or an Internal preset first, and then switch to the Custom API I want to use.

Developer

Hi mate,

Thank you! ⭐⭐ I noticed another load bug regarding Presets too. I am going to release a new alpha build tomorrow that will fix both bugs. I'm working on some basic localization at the moment so I just want to wrap that up before releasing the next build.

Okay. Thank you :)

Developer (1 edit)

Bug should now be all sorted. New 0.5.2-alpha.3 version released! :)

If you want to try the basic machine translation localization, it is in the General settings. But bear in mind, the quality is very low. I might look into doing translations with DeepL for the languages that are available there. I'll have to look into their commercial rules first though.

Yeah, thanks for fixing that bug! I completely forgot to mention yesterday that I found another one. It seems like the app doesn't save my language selections for the DeepL and Internal presets. I have to re-select the languages every single time I open it.

I also gave the basic machine translation localization a try, and it's definitely pretty basic :) On the big buttons, it actually translated the same word twice like, "save" appeared twice, but it's still okay and a good start.

Developer

Nice!

Oh. Okay, that's bad. Surprised I haven't noticed that 🫡

And yup! That's just the shortcomings of the internal models for you.. Most of the models are very broken in some areas. I'll probably change the ML translations for the next version.

Thank you for the quick feedback ⭐

Developer

Hiya mate!

I believe I have fixed that bug now as well in the new 0.5.2-alpha.4 version. I also updated almost all localization to be done by a LLM, which, as far as I can tell, drastically improved translations overall. Feel free to check it out!

Thank you :)

Hi,

Yeah, it looks good now, and the localization is a lot better, too.

Thanks! 🙂

Developer

Excellent 🙏🏼

Can't thank you enough!

(1 edit)

Hi,

My apologies, I think I missed this or just didn't notice it yesterday, but I'm afraid there's another bug.

When the app loads a saved DeepL preset, I'm unable to change the languages for the DeepL translation, the language options are grayed out.


The only way I've found to fix it is by deleting and re-pasting the API key. After that, it works normally.


Sorry once again. 😞

Developer

Heya!

I noticed this yesterday as well. Didn't have time to push any more changes so I left it. No worries! Thank you once again for reporting any bugs you find.

To 'enable' the source & target dropdowns, all I had to do was click the API key input and then click somewhere else. Maybe that works for you too?

(1 edit)

Okay, got it :) Yes, your method works too, and it's even better. Thanks! :)

(1 edit)

Hi,

Unfortunately, a couple of config preset bugs have reappeared with the new update.

The Deepl API key is not being saved into the config. For example, if I paste the API key into one Deepl config and switch to another Deepl config, it probably gives the same one, because if I delete the key and nothing is there, and I switch to the other Deepl config, that one is also empty, even though it shouldn't be. Since the key is no longer visible in the app, I can only assume this is happening due to the reasons mentioned above. When I exported the configs, the API key wasn’t included either. But interestingly, right after updating, when I first opened the app and noticed that config presets could now be exported (before you couldn’t, right?), I exported them straight away. In those first exported files, the API key was still there.

Also, before, you could only pick the languages once the API key was entered, but now you can pick them without one. Not sure if that’s a bug or just a change, but it's not an issue for me. :)

I also noticed a bug with the API encryption setting. It appears to be shared across all Deepl configurations. If I enable encryption in one Deepl config, it incorrectly shows up as enabled when I switch to another Deepl config, even if I never set it there.

I have a small UI request regarding the config preset field. Could you possibly make that field a bit larger? It's currently quite small, and when a config has a long name, the full name gets cut off, making them hard to distinguish, especially when multiple configs start with the same name. Alternatively, showing the full name when the mouse hovers over the field, or displaying the full name near the version number above, would also be a great solution.

Thanks :)

Developer

Heya!

The DeepL bug you mention is not a bug at all, this is the intention. All API keys are now stored in the same plain text file, until you encrypt them, and when you do, they are safely stored and trusted by your computer & your master password. All configs will use the same DeepL key.

If you are using multiple DeepL keys (sneaky sneaky..!), let me know, I can set it up so it is possible to use more than one.

Yes, exporting is new, as well as importing. The reason the API key existed in the config on the first launch was just because your configuration file had not been saved & updated yet before export.

You can only pick one if you have previously had the API key to authenticate during that session. This is not really intended however, I do want it to reauthenticate even the API key is changed/removed! :)

Yep! I'll fix that UI request, I agree it wasn't optimal. Thank you!! :)

Hi,

Thanks for clearing that up. I honestly thought it was a bug.

Yes, I do use more than one Deepl key, specifically two (ര ‿ ര ). That's why I brought this up, since I was running into issues with using two keys. It would be a huge help if you could get it working with multiple keys (˵ •̀ ᴗ •́˵)

Oh, got it.

And thanks so much for considering the UI request! ദ്ദി(˵ •̀ ᴗ - ˵ ) ✧

Developer

Eyup,

0.5.3-alpha.2 is now out! DeepL can now use 'custom' API keys too, exactly like the custom API. Fixed the UI request too, if I didn't understand it wrong.

Love the smiley haha. Gives me nostalgic feelings.

Besteht die Möglichkeit das ich einen Schlüssel für deepl bekomme kann?? Hab leider keine Kreditkarte und kann mir keinen free Account erstellen

Developer

Hi,

Unfortunately, we do not offer any API keys for DeepL ourselves.

I would recommend looking at this thread and instead use the Custom API solution.

https://itch.io/t/5352880/free-llm-api-resources-api-setup-guide

Sorry for the inconvenience.