Search Issue Tracker
Fixed
Fixed in 1.4.3, 1.5.0-pre.2
Votes
0
Found in [Package]
1.4.0-exp.1
Issue ID
LOC-785
Regression
Yes
Localization String value search returns 0 string tables when no characters are given to search by
Reproduction steps:
1. Open the “MinProject” project
2. Open the “MyScene“ scene
3. Select the “MyObject“ GameObject
4. In the Inspector press on the “My Localized String“ field value
5. Observe the available string table entries
Expected result: “None”, “MyEntry1” and “MyEntry2” are available
Actual result: Only “None” is available
Reproduced in: 1.1.0, 1.4.0-exp.1 (2021.3.7f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4)
Not reproduced in: 1.0.5 (2020.3.37f1, 2021.3.7f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4), 1.1.0, 1.4.0-exp.1 (2020.3.37f1)
Reproduced on: Windows 10, macOS Monterey 12.0.1
Notes:
- Inputting a character (e.g. “M”) into the search field reproduces the expected result
- 2020.3 is not affected
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