Quick answer: After changing culture, re-evaluate FText on visible widgets (rebuild or re-set bound text) so the new language is pulled from the string tables.

Calling SetCurrentLanguageAndLocale relocalizes future text but not widgets already on screen in Unreal. Refreshing them fixes it. Here is how.

How to fix it

1. Refresh open widgets after the change

After SetCurrentLanguageAndLocale, re-set the text on visible widgets or rebuild the affected UMG so cached FText values re-resolve from the active culture.

2. Use property bindings or FText source keys

Bind text properties so they re-evaluate, or hold the namespace/key and re-fetch via the string table on a locale-changed event rather than storing a resolved string.

3. Verify the culture actually applied

Confirm FInternationalization::SetCurrentCulture succeeded and the target locale's data is packaged, since a failed culture set leaves text unchanged with no error.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.