ShuriZma
/
pcsx2
mirror of https://github.com/PCSX2/pcsx2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

gsdx ogl: explain better previous clear vs framebuffer comment

This commit is contained in:
Gregory Hainaut 2016-05-16 16:49:18 +02:00
parent 08f7bd2dc3
commit 99476f4b13
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
plugins/GSdx/GSDeviceOGL.cpp
View File

@ -526,9 +526,12 @@ void GSDeviceOGL::ClearRenderTarget(GSTexture* t, const GSVector4& c)
if (T->HasBeenCleaned() && !T->IsBackbuffer())
return;
// Performance note: potentially T->Clear() could be used. However the render target
// will be used right away as the render target. So in all case, FBO must be binded
// and the texture attached too. So using the old/standard path is better.
// Performance note: potentially T->Clear() could be used. Main purpose of
// Clear() is to avoid the framebuffer setup cost. However, in this context,
// the texture 't' will be set as the render target of the framebuffer and
// therefore will require a framebuffer setup.
// So using the old/standard path is faster/better albeit verbose.
GL_PUSH("Clear RT %d", T->GetID());