Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0f3
Issue ID
885865
Regression
Yes
The value of objects is shown different in the Editor and in the standalone
Reproduction steps:
1. Open the attached file "case885865-small.zip";
2. Open the scene "level1";
3. Build the project and open it;
4. Press "t" and observe the number of key collected (Built game value.jpg);
5. Come back to the project and enter Play mode;
6. Press "t" and observe the number of key collected (Value in the Editor.jpg);
Actual result: the number of key collected is different in the Editor (the number is 1) and in the built game (the number is 2 or 3).
Expected result: the number of key collected should be the same in the Editor and in the built game.
Note: If the built game shows the same number like in the Editor, try to build the project on the built game (repeat). Also, sometimes, when the text in Canvas -> KeyText is changed from "Key Collected: 1" to "Key Collected: 0", everything works fine.
Sometimes different behaviour happens, the key in the Editor is 2 or 3 and in the built game 1. Also, when the built game is opened again, the number of key is changing with each opening. According to the script, everything should work fine.
Reproduced with: 5.5.0b1, 5.5.0f3, 5.6.0b10, 2017.1.0a2
Not reproducible with: 5.4.4p3, 5.5.0a6
Regression introduced in 5.5.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment