Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
1000506
Regression
No
Frames advancing even though "WaitForEndOfFrame()" is used
Reproduction steps:
1. Open "WaitForEndOfFrame Bug.zip" project
2. Enter Play mode
3. Look at the 3 outputs in the Console window
Expected Result: The outputs "frame count" should be as follows: 0, 1, 1
Actual Result: The outputs "frame count" are as follows: 0, 1, 2
Reproduced with: 2018.2.0a1 (9dd3a0), 2018.1.0b7, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1, 5.6.5p2
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
- [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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.