Well, I ran the experiement...

1.) it does work, though apparently the FBO texture ends up upside
down with relation to all my other textures, so I had to do a little
correction for that
2.) it does increase the frame rate, but not substantially
3.) it does look worse (a 256x256 FBO is not too awful.  128x128 is
horrid)
4.) it consumes extra memory (for the FBO buffer(s))

on a Moto Droid I, my reference scene

Without FBOs, rendering to full screen: about 20 fps
With FBOs, rendering to 128x128: about 28.5fps
With FBOs, rendering to 256x256: about 26.2fps
With FBOs, rendering to 32x32: about about 30 fps  (clearly unusuable,
of course, unless you wanted a illusion of out of focus)

512x512 is not on the table as you get an out of memory condition with
high regularity

I still have to try it on the Eris (my problem phone), but overall, I
don't think the result really justifies the feature.

I'm pretty sure the fill rate I save with the smaller render target is
lost with the render of the background quad with that texture on it.
Perhaps if I had a clever way to jam the texture (and stretch it
nicely) into the colorBuffer directly...

On Sep 12, 1:12 pm, Samsyn <[email protected]> wrote:
> My apologies if this is a stupid question...
>
> Might I get a net frame rate improvement if I did something like this:
>
> * create an FBO of resolution less than the full phone screen
> dimensions (user-selected quality vs speed option)
> * do most of my scene rendering into that FBO
> * then the 'real' (full screen) render would either use the FBO as the
> starting background color buffer contents, or render it (probably
> orthographically) as a single quad.
> * then probably add UI/Text decoration on top of that, where the
> resolutions really benefits.
>
> And, is there some egl glue (I am a glSurfaceView kinda dood) that
> would automagically do something like this in the first place?
>
> Or am I being naive to think the GPU could do its work faster if it
> was rendering to a lower resolution target?
>
> And would the phone with the worst fill rate also be the phone that
> doesn't support FBOs in the first place?
>
> After reading the OpenVR info (thanks again, Lance) I think I might
> get some improvement by breaking some huge triangles into smaller
> ones. I have some (water layer, in particular) that are so large they
> probably get processed by every tile of the screen.
>
> Thanks for any insights,
>
> - Dan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to