Vulkan Semaphores
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.6k
- Forks
- 2.4k
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
For the vulkan interop samples there seems to be an issue with semaphore signals. If you simply comment out the signal from cuda side, it makes no difference and the program runs normally.
In theory it should halt the program because it's waiting on that signal during rendering. So it seems with Vulkan-Cuda interop the exported semaphores do nothing.
This is on Windows 10, latest driver for GTX 970 .
Edit: Timeline semaphores work ok, that's a good enough workaround for me.
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 Vulkan interop samples and tracing the CUDA semaphore signal and Vulkan rendering wait paths. Reproduce the behavior on Windows 10 with the reported GTX 970 setup, then verify that binary semaphore signals affect execution as expected while preserving the stated timeline-semaphore workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100