FRAPS reports approximately 211 fps on average for the CopyTexSubImage version. The P-Buffer version says it can’t find the entry points for WGL_ARB_pbuffer. Oddly enough, the extension string is missing from the drivers I’m using. . .
to Ostsol:
Its impressive, 211fps for CopyTexSub. And for the render to texture, I 'll soon improve the extension detection mechanism.
I didn’t made it clear, but fps are written on a text console behind the GL window.
You just have to drag the gl window a bit, so you can see the fps. (I don’t know for sure what FRAPS calls a ‘frame’).
Furthermore, could you test what fps increase you get by turning off final render (hit B) ?
Ah. . . Well, it looks like FRAPS is pretty accurate, as it agrees with the value in the console window. Pressing ‘b’ increases the framerate to around 600 fps.
[This message has been edited by Ostsol (edited 12-01-2003).]
to Ostsol :
I’ve udated the detection of Render to Texture, you may try it now. I still hardly believe your 200+ fps . When I found only 5 fps on my gf3, I wanted to drop it… but if it works so well on radeon 9700, I may keep it.
Ah. . . Works perfectly, now. I get 108 fps normally, then 220 after pressing ‘b’. Quite a bit lower than the glCopySubImage version. . . It looks like the p-buffer version uses a much higher resolution render target, though, so perhaps the performance difference isn’t so strange.
Thank you all for your figures.
Yes, the CopyTex version is 128x128 instead of 512x512, because on my setup the full res CopyTex was soooo crawwwwwliing… I will post a high res version later this week.