Search Issue Tracker
Fixed
Fixed in 1.5.8
Votes
1
Found in [Package]
1.5.7
Issue ID
LOC-1252
Regression
No
Local variable uses Global variable when both have the same name in Localization
Reproudction steps:
1. Open the attached “IN-114583.zip” project
2. Open the “BUG-1682014” scene
3. Enter Play mode
4. Observe the second line of text in the Game view
Expected result: The second line of text is “This player name is Jake”
Actual result: The second line of text is “This player name is John”
Reproducible with: 1.5.1, 1.5.7 (6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Note:
- Also reported in Discussions https://discussions.unity.com/t/local-variable-uses-global-variable-if-it-has-the-same-name/1682014
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Add comment