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
When making a GPU bound application, the framerate drops, but still on both Vulkan and OpenGL, the results of the draw calls / command buffer timings are super short. As if nothing is timed.
Vulkan:
Any chance that the timestamps I'm getting out of both APIs are correct, but the results are badly displayed in the Tracy timeline? It doesn't seem to matter how much stuff you push onto the command buffer, it stays always just that short-lived zone of work.
The text was updated successfully, but these errors were encountered:
mcourteaux
changed the title
Vulkan GPU zones do not have accurate timing for me.
Vulkan and OpenGL GPU zones do not have accurate timing for me.
Jun 6, 2024
Hmm, I just checked for OpenGL manually with printf-debugging... The query counter I get back from OpenGL indeed show 2ms, whereas the frame time is 42ms. Is this a synchronization issue, or a driver bug? Or am I misinterpreting what the query counters should represent?
OpenGL:
When making a GPU bound application, the framerate drops, but still on both Vulkan and OpenGL, the results of the draw calls / command buffer timings are super short. As if nothing is timed.
Vulkan:
Any chance that the timestamps I'm getting out of both APIs are correct, but the results are badly displayed in the Tracy timeline? It doesn't seem to matter how much stuff you push onto the command buffer, it stays always just that short-lived zone of work.
The text was updated successfully, but these errors were encountered: