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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment