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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
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.