Localization: OK in Standalone, missing after packaging
I've created some translations in Localization Dashboard and set them up. They work correctly in Standalone game mode (I can change localization in-game via console commands), but after packaging it doesn't work. I have polish as my native language set up, but I want english to be default language after packaging. Here are my settings:
"Package default localization" is set to "en" and it works correctly when playing in Standalone mode (everything is in english), but in packaged game it starts in polish and I can't change the language in-game just like I can in Standalone mode.
asked Oct 19 '15 at 09:14 PM in Packaging & Deployment
I don't know solution for this problem but it is possible to bypass it. It is impossible to achieve with blueprint only but C++ code is quite easy.
Short version: use
1.File -> New C++ Class -> Blueprint Function Library, name of class basically doesn't matter from blueprint perspective.
2.In my case code looks like:
3.After compilation you'll be able to simply call your functions from blueprint
Call it after level
answered Oct 26 '15 at 03:48 PM
How would you treat it if you're not using the localization files for translation, but for text formatting and text storage?
How do you add them?
This is also happening to me. It works fine in play in Editor AND Standalone. However, I just launched it and packaged it and both have this string tables gone (I'm using the 4.18 String Table Assets btw) and thus not loaded.
answered Jan 06 '18 at 11:43 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here