Search Issue Tracker
Fixed
Votes
0
Found in [Package]
0.8.0-preview
Issue ID
LOC-126
Regression
Yes
[Localization] "No Translation Found Format" variable isn't used when an Entry Locale is empty
How to reproduce:
1. Open the user's attached "Test localization package 2" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
Expected results: In the Game view both "-------" text fields become "No translation found for 'Entry 1'"
Actual results: In the Game view both "-------" text fields become empty
Reproducible with: 0.8.0-preview, 0.9.0-preview (2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a6)
Not reproducible with: 0.7.1-preview (2019.4.15f1, 2020.1.14f1, 2020.2.0b12, 2021.1.0a6)
Notes:
- Changing languages can produce a broken variation of the No Translation Found Format text (can be seen when switching to the Spanish language in the user's project)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment