Relax queue ownership transfer (TransferQ, ComputeQ flags)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 35
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Research if we can use manual resource queue ownership transfer via barriers. Right now the problem is we don't know in which queue resource will be used after frame queue recording and can't place ownership transfer barriers. Maybe this will be possible with frame graph.
For staging buffers we can use this hack:
#if GARDEN_DEBUG
BufferExt::getUsage(**stagingView) |= Buffer::Usage::TransferQ | Buffer::Usage::ComputeQ;
#endif
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 reading the queue ownership and barrier discussion in this issue, then inspect the frame graph proposal in issue 77 and the staging-buffer example using BufferExt::getUsage with TransferQ and ComputeQ. Done means establishing whether manual ownership transfer is feasible after frame queue recording and documenting the resulting approach or blocker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100