Skip to content
This repository was archived by the owner on Dec 6, 2020. It is now read-only.

Properly make use of frame index #87

Open
MeineZ opened this issue May 31, 2019 · 2 comments
Open

Properly make use of frame index #87

MeineZ opened this issue May 31, 2019 · 2 comments
Assignees
Labels
being worked on Issue is being worked on by the development team bug Something isn't working

Comments

@MeineZ
Copy link
Collaborator

MeineZ commented May 31, 2019

Properly make use of the frame index in the renderer to avoid lagging behind 3 frames. As of right now, it seems like the Wisp viewport is one frame behind on Maya.

For example, it starts with a black screen even though it already rendered a frame. However, this frame is still in the back buffer and not presented to the screen. As soon as a new update is detected this frame is shown and the next frame is rendered, though, it's not presented yet.

Making use of the frame index properly fixes this issue.

Very noticeable when zooming in and out very fast.

@MeineZ MeineZ added the bug Something isn't working label May 31, 2019
@tntmeijs tntmeijs added the being worked on Issue is being worked on by the development team label Jun 5, 2019
@tntmeijs
Copy link
Member

tntmeijs commented Jun 7, 2019

Frame indexing has been implemented by #95.
Will look into this and texture deallocation next.

@sainsay
Copy link
Collaborator

sainsay commented Jun 25, 2019

Lag has been reduced significantly in #129

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
being worked on Issue is being worked on by the development team bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants