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

fix framebuffer invalidation #36

Open
shakesoda opened this issue Mar 22, 2020 · 0 comments
Open

fix framebuffer invalidation #36

shakesoda opened this issue Mar 22, 2020 · 0 comments
Assignees
Labels

Comments

@shakesoda
Copy link
Owner

upon trying to use it again, and looking at how it is implemented, I realized that as-is the view invalidation flag can't work for most cases.

it should be able to throw out the data after resolving msaa, and there should be a way to indicate in a more granular way which attachments you don't care about. right now, it throws them all out on binding the next framebuffer if you've set this flag, which generally just gives you a corrupted render.

@shakesoda shakesoda added the bug label Mar 22, 2020
@shakesoda shakesoda self-assigned this Mar 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant