Allow clearing backbuffer after finishing CanvasGroup
This avoids an issue where having multiple CanvasGroups overlap would create a weird artifact
This commit is contained in:
parent
1baefceaba
commit
4765e5fa64
2 changed files with 4 additions and 0 deletions
|
@ -300,6 +300,8 @@ void RasterizerCanvasGLES3::canvas_render_items(RID p_to_render_target, Item *p_
|
|||
}
|
||||
|
||||
canvas_group_owner = nullptr;
|
||||
// Backbuffer is dirty now and needs to be re-cleared if another CanvasGroup needs it.
|
||||
backbuffer_cleared = false;
|
||||
}
|
||||
|
||||
if (backbuffer_copy) {
|
||||
|
|
|
@ -1475,6 +1475,8 @@ void RendererCanvasRenderRD::canvas_render_items(RID p_to_render_target, Item *p
|
|||
}
|
||||
|
||||
canvas_group_owner = nullptr;
|
||||
// Backbuffer is dirty now and needs to be re-cleared if another CanvasGroup needs it.
|
||||
backbuffer_cleared = false;
|
||||
}
|
||||
|
||||
if (backbuffer_copy) {
|
||||
|
|
Loading…
Reference in a new issue