Expose encoder-owned texture rendering API without internal queue submit
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.3k
- Forks
- 300
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
`vello::Renderer::render_to_texture` currently takes a `wgpu::Device` and `wgpu::Queue`, records internally, and submits its own command buffer. This works for standalone rendering, but makes integration with larger compositors difficult because the compositor cannot keep Vello work inside its own frame command stream.
For UI/rendering frameworks that own frame scheduling, final blit, and presentation, it would be useful to have an API that records Vello rendering into a caller-provided `wgpu::CommandEncoder` without calling `queue.submit`.
However I am not sure if is this doable?
Contributor guide
No contributing guide indexed for this repository
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 examining the vello::Renderer::render_to_texture entry point and trace how it records work and submits through the wgpu::Queue. Determine how to expose equivalent recording through a caller-provided wgpu::CommandEncoder without queue submission, and verify that callers can include the work in their own frame command stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100