Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0b2
Issue ID
828402
Regression
No
If field stays selected after Play Mode is stopped the value does not change back
Reproduction Steps:
1. Create new project
2. Select any float field (for example Camera's Transform position x field)
3. Select the current value (it has to be highlighted)
4. Note don't press anywhere
4. Play the scene
5. Change the same field value
6. Leave the field selected/active and stop the play
7. Press somewhere (for example, Game View) to lose focus of that field (do not focus on something else)
8. Notice that value changed back to the one before Play
9. Select the field again
10. Notice that it changes again to the value changed while Play
Expected behaviour: Values changed during play are changed back after stop
Actual result: Values are changed back, but wrong ones are displayed
Reproduced on versions: Unity 5.3.4f1, 5.3.6p4, 5.4.0p4, 5.5.0b2, 2017.2.0p1, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment