microsoft / microsoft/DirectX-Graphics-Samples
nBodyGravity waitable object timing issue
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.8k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
Is it just me or is the nBodyGravity sample's "compute rate" ( i.e. speed at which particles get updated) abnormally fast? When I get rid of the waitable object the particle speed goes back to normal, even though in both cases vsync makes the app run at the monitor refresh rate.
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 reproducing the nBodyGravity sample with and without the waitable object while vsync is enabled, then compare the particle update timing and compute rate. Done means identifying why the waitable-object path changes the apparent update speed and confirming consistent behavior at the monitor refresh rate.
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