KhronosGroup / KhronosGroup/Vulkan-Tools
On-Screen Frame Counter for vkcube
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 493
- Forks
- 202
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 4
Description
Downstream tools such as layers which display overlays are able to paint the current frame number but it would be useful at least as a check on them or to simplify the layer stack for the vkcube app to print it's idea of the current frame number into the framebuffer.
This would mostly be of interest as a visual confirmation for authors of tools which are able to take actions over specific frame ranges such as trace capture and replay that those tools selected the correct frames to operate on.
Of course the big issue would be, does the frame count start at zero or one?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the vkcube rendering and framebuffer update path, then trace where its current frame number is maintained. Define whether numbering starts at zero or one, display that number in the framebuffer, and verify visually that it advances consistently for frame-range tool checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100