You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
FIFO and FIFO_RELAXED for Vulkan are displaying old frames out of order, causing jitter. This happens if my monitor is set to 144hz, but if I lock it to 60 in windows it doesn't happen. I found this while working on my Bevy game, and was able to reproduce it in the Boids example. The Bevy reproduction even shows the frame count rendered on screen and you can see it go 3317, 3319, 3321, 3320. In the Boids gif attached below, it goes 1,2,3,4,3,5, no skipping a frame outright.
Repro steps
Run Boids example.
It can be harder to tell vs normal frame pacing issue, so it can make it easier to record and review to footage frame by frame
Expected vs observed behavior
Expected: To not see a frame repeated after a newer one has been shown.
Observed: Frames going backwards.
Description
FIFO and FIFO_RELAXED for Vulkan are displaying old frames out of order, causing jitter. This happens if my monitor is set to 144hz, but if I lock it to 60 in windows it doesn't happen. I found this while working on my Bevy game, and was able to reproduce it in the Boids example. The Bevy reproduction even shows the frame count rendered on screen and you can see it go 3317, 3319, 3321, 3320. In the Boids gif attached below, it goes 1,2,3,4,3,5, no skipping a frame outright.
Repro steps
Run Boids example.
It can be harder to tell vs normal frame pacing issue, so it can make it easier to record and review to footage frame by frame
Expected vs observed behavior
Expected: To not see a frame repeated after a newer one has been shown.
Observed: Frames going backwards.
Extra materials
![Old_frame](https://private-user-images.githubusercontent.com/3324533/340377006-32070c5e-5b8e-4e82-a853-6e3b91d7b675.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2NTYwNjUsIm5iZiI6MTcxOTY1NTc2NSwicGF0aCI6Ii8zMzI0NTMzLzM0MDM3NzAwNi0zMjA3MGM1ZS01YjhlLTRlODItYTg1My02ZTNiOTFkN2I2NzUuZ2lmP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjlUMTAwOTI1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MWE0YzEyZGEyMjE1ZmIxZTkyZGNiMDZlNjM4YWM0Y2QyZDFiMTQyNWYyYmFiNjYxMjkyNWRmYTA2ODZkYzEyNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.WB4NbW7R42Akn6wyYtuEASoh6UrI5ng0HDPv4SmUSpk)
![Old_frame_3](https://private-user-images.githubusercontent.com/3324533/340377025-0f889883-a8c5-498d-a90e-b378e53ecf03.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2NTYwNjUsIm5iZiI6MTcxOTY1NTc2NSwicGF0aCI6Ii8zMzI0NTMzLzM0MDM3NzAyNS0wZjg4OTg4My1hOGM1LTQ5OGQtYTkwZS1iMzc4ZTUzZWNmMDMuZ2lmP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjlUMTAwOTI1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YThkZjU0NjMxOGVjZjg4Mjk0NGM0ZjIwMTQ2Yjc2ZjM4Y2FkZDZkNDdiZjY1NGUzNGRiMzBkNzg2OGU4MzIwMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Ne0Z5yHzcEW3tDhmE_sMvE9IscCCR6ojcRQ-CAq_YG4)
Trying to find other people running into this issue and I found this. https://forums.blurbusters.com/viewtopic.php?t=13358. 0 idea if it's useful.
Platform
Windows 11 build 22631, Nvidia 4090 running 555.99. Found on wgpu 0.17.2 and 0.20.1
The text was updated successfully, but these errors were encountered: