Can RealityScan's translation work be accomplished by modifying XML resource files?

124c9bfe252546968e9cad6c04f4068f · July 21, 2026, 2:53pm

During my use of RealityScan on Windows, I noticed that the translation completeness for my country’s language is quite low. At the same time, I discovered UI language files such as “RealityScan_2.2\languages\en-US” within the RealityScan folder. Therefore, I speculated that I could translate the contents and align the IDs from the source language (i.e., US English) files to ensure the translation results would work properly.

However, during actual testing, I encountered the following issue:

I modified the XML language files within “RealityScan_2.2\languages\zh-CN”.

Taking one field as an example:
An algorithm for mosaicing-based orthographic projection.

This field contains the attributes comment=“0” and translation=“false”, which I assumed indicated that it was pending translation.

I referred to the XML file in US English and made modifications:
An algorithm for mosaicing-based orthographic projection.

And ultimately obtained the following result:
基于马赛克的正交投影算法。

However, after saving and restarting the RealityScan program, I found that my modifications did not take effect.

I checked files such as languages.xml and languagesMY.xml within the RealityScan folder but did not find the reason for the translation failure. I then cleared RealityScan’s cache and reloaded it, but the changes still did not take effect.

At this point, I began to suspect that modifying XML files might not be sufficient to complete the translation work, and that the XML files might actually be for display or backup purposes only. Therefore, I tested with the source language file “RealityScan_2.2\languages\en-US”, and modifying its content also did not take effect properly.

I would like to know how I should complete the translation work in this situation. Should I decompile RealityScan to translate it? But I feel that would be much more difficult and require significantly more effort. Or is there something wrong with my translation approach that is causing the failure?

David_RealityScan · July 22, 2026, 9:21am

Hi @124c9bfe252546968e9cad6c04f4068f ,

As a workaround, you can try launching RealityScan in TranslatorMode via the command-line interface (CLI) using the -translatorMode argument.

Here is how to set it up:

Create a .bat file containing the path to your RealityScan executable.
Add the -translatorMode flag to the launch command line.
Run the .bat file to launch the application.

Once RealityScan opens, all UI elements and icons will display their corresponding string IDs next to their names. These IDs map directly to the localization files located in RealityScan_2.2\languages\.

Hope this helps! Please let us know if you run into any issues.

124c9bfe252546968e9cad6c04f4068f · July 23, 2026, 9:03am

Thank you for your suggestion. Although it didn’t actually work, I discovered that the issue wasn’t with the format of my modifications. Instead, based on the command line you provided, I found that the translation localization files that RealityScan uses are actually located at:

C:\ProgramData\Epic\RealityScan\LanguagePack\languages\

I need to make my changes in that path for them to take effect. Previously, I had mistakenly assumed that the application was reading from the languages folder located in the tool’s source file directory.