Search Issue Tracker
Fixed
Fixed in 1.5.x
Votes
1
Found in [Package]
1.5.5
Issue ID
LOC-1237
Regression
No
Localization Package has integration issues when used with Visual Scripting Scene Variables and custom Nodes
Reproduction steps:
1. Open the attached “IN-107815.zip” project
2. Open the “SampleScene”
3. From the Hierarchy, select the “SceneVariable” GameObject
4. In the Inspector, find the “Variables” Component
5. Click on the dropdown next to “Value” property
6. Select any String from the Search pop up
7. Observe the “Value” property
Expected result: The String gets selected
Actual result: The value remains as “None (String)”
Reproducible with: 1.5.2, 1.5.5 (6000.0.55f1, 6000.2.0f1, 6000.3.0a4)
Couldn’t test with: 2022.3.64f1 (Could not downgrade)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Every once in a while the String does get correctly selected, but creating a new Variable always reproduces the issue
- Similarly, trying to use a Localized String in a custom node: it’s not possible to set a default value, and you only get a connector (unlike types such as String). This can be observed in the “TestGraph.asset”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment