nBodyGravity waitable object timing issue

Open
#843 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
computer-graphics

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.

Description

question samples

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.

Dominant language
C++
Stars
6.8k
Forks
2.2k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DirectX-Graphics-Samples

All issues in microsoft/DirectX-Graphics-Samples

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.