Search Issue Tracker
Fixed
Fixed in 1.0.5
Votes
1
Found in [Package]
1.0.5
Issue ID
LOC-530
Regression
No
[Localization] Smart String's local variable references get lost when entering Play Mode
Reproduction steps:
1. Open the attached project "Repro" from the google drive link
2. Select the "AppliedLocalVariables" GameObject
3. In the Inspector window locate the "Local Variables" section and in the "Object Reference" field add the "Main Camera" GameObject
4. Select the "NotAppliedLocalVariables" GameObject and do the following like in step 3.
5. Enter Play Mode and notice that the "Object Reference" in the "NotAppliedLocalVariables" GameObject is the same
6. Inspect the "AppliedLocalVariables" GameObject in Play Mode
Expected result: "Object Reference" in the "AppliedLocalVariables" GameObject is "Main Camera"
Actual result: "Object Reference" in the "AppliedLocalVariables" GameObject is "None"
Reproducible with: 1.0.3, 1.0.5 (2021.2.5f1, 2022.1.0a16)
Not reproducible with: 1.0.5 (2022.1.0b1)
Could not test with: 1.0.5 (2019.4.33f1, 2020.3.25f1) (Various project errors when downgraded)
Notes:
-Leaving Play Mode results in the "Object Reference" to lose the specified GameObject and stays "None"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Resolution Note (fix version 1.0.5):
Issue is no longer reproducible in 2021.2.6f1 or 2022.1.0b1.