Add control for managing framebuffer clearing #732
Merged
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 adds the ability to decide whether to clear color or depth data (or both) on a framebuffer.
Prior to #607 we always cleared both. After #607 we only were clearing depth data. This had a negative impact on the "main" framebuffer used for rendering imgui where artifacts were preserved. This would appear whenever the game render space was not identical to the main window (like when using advanced resolution features).
With ability to clear things independently, we can now ensure that the main framebuffer is always cleared if the game is not rendered to it. This should resolve issues with the advanced resolution editor, without reverting anything needed by #607