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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment