Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird behavior for "animometer" with render bundles #155

Open
Synxis opened this issue Dec 20, 2021 · 1 comment
Open

Weird behavior for "animometer" with render bundles #155

Synxis opened this issue Dec 20, 2021 · 1 comment

Comments

@Synxis
Copy link

Synxis commented Dec 20, 2021

This match a behavior I encountered on my own tests : when running the animometer sample, with render bundles and a numTriangles at 200,000, the render frequently glitches. This seems to be some kind of data-race, as the slower the frames, the less this effect appears (this notably makes it very difficult to record).

Anyway, I attached a video taken with my phone to show it, here is the environment:

  • NVIDIA Quadro T1000
  • Windows 10 (20H2, build 19042.1348)
  • Chrome 99.0.4777.0 canary (64 bits)

I don't know whether this is a bug in the sample, in chrome, in my gpu or in another part of my computer, I'll continue to search.

render-bundles-glitch.mp4
@kainino0x
Copy link
Collaborator

This looks like a frames-out-of-order bug (e.g. sometimes the compositor is showing an old frame instead of the current one). Maybe somehow related to backpressure, like if the system gets behind on frames, it triggers an issue where we don't recycle frames properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants