Experimental integration with Achoreographer #703
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternative to #674.
It has significantly better latency performance, with a few peculiar behaviours I can't quite reason about. In particular, it seems to like falling back to 45 fps, but not consistently. More experimentation is needed, I think.
Overall, for the amount of code, the latency reduction is excellent. With this:
Total latency: ~33ms-43ms
vs without this:
Total latency. Highly variable: ~43ms-53ms
In both of these cases, 16ms is due to compositing, and ~10ms is due to rendering. That is, this integration still leaves some latency on the table, because the callback arrives at vsync, but our rendering doesn't take all of the time the next compositing time.