Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
6000.4.0a1
Issue ID
UUM-101701
Regression
No
Play Mode button is shown in hovered state when saving a script and immediately clicking the Play Mode button to focus the Editor
Steps to reproduce:
1. Open the attached “bmw-car-sample.zip” project
2. Open the “DemoScene”
3. In the Project tab, open “Interaction/TouchCameraRotation.cs”
4. Change anything in the script
5. Save the changes and immediately click the “Play” button in the Editor
6. Observe the results
Expected result: Play Mode is entered
Actual result: The Play Mode button is highlighted as it was “hovered” over
Reproducible in: 2022.1.0a1, 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: macOS (Silicon M2), macOS (Intel)
Not reproducible on: Windows 11
Note: Reproducible on an empty project
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
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
This problem is affecting only some users, plus we tried to repro on 6.3 and 6.4 and it seems that the introduction of the new Customizable toolbar in 6.3 fixed that problem for more recent versions.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.