You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2021. It is now read-only.
The library has no way to figure out whether a page-flip happened. This is necessary for tracking the priority of each layer (at least as we do now, a time-based tracking wouldn't require that).
I've deliberately ignored this for now and assumed a page-flip would happen on liftoff_output_apply. It probably doesn't matter that much, since we're interested in update frequency differences between layers, not the actual page-flip events. I'll leave this issue opened just in case this causes some unexpected issues.
The text was updated successfully, but these errors were encountered:
As an alternative, a drmCrtcGetSequence call at the beginning of liftoff_output_apply would allow us to know how many frames have been displayed since the last libliftoff invocation.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The library has no way to figure out whether a page-flip happened. This is necessary for tracking the priority of each layer (at least as we do now, a time-based tracking wouldn't require that).
I've deliberately ignored this for now and assumed a page-flip would happen on
liftoff_output_apply
. It probably doesn't matter that much, since we're interested in update frequency differences between layers, not the actual page-flip events. I'll leave this issue opened just in case this causes some unexpected issues.The text was updated successfully, but these errors were encountered: