-
-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulkan and OpenGL GPU zones do not have accurate timing for me. #811
Comments
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: