Skip to content
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

Frame images #96

Open
colinmarc opened this issue Mar 14, 2024 · 1 comment
Open

Frame images #96

colinmarc opened this issue Mar 14, 2024 · 1 comment

Comments

@colinmarc
Copy link
Contributor

The PDF mentions an API (FrameImage) for sending screengrabs to the server. Is that something that's possible to support in the rust client?

It is possible to attach a screen capture of your application to any frame in the main frame set. This can help
you see the context of what’s happening in various places in the trace. You need to implement retrieval of
the image data from GPU by yourself.
Images are sent using the FrameImage(image, width, height, offset, flip) macro, where image is
a pointer to RGBA32 pixel data, width and height are the image dimensions, which must be divisible by 4,
offset specifies how much frame lag was there for the current image (see chapter 3.3.3.1), and flip should
be set, if the graphics API stores images upside-down33. The profiler copies the image data, so you don’t
need to retain it

Thanks in advance!

colinmarc added a commit to colinmarc/rust_tracy_client that referenced this issue Mar 14, 2024
colinmarc added a commit to colinmarc/rust_tracy_client that referenced this issue Mar 14, 2024
colinmarc added a commit to colinmarc/rust_tracy_client that referenced this issue Mar 14, 2024
colinmarc added a commit to colinmarc/rust_tracy_client that referenced this issue Nov 30, 2024
@Dinnerbone
Copy link

I think this can be closed now? Added in #97

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants