I agree with Tim.
FWIW the most common implementation read format, when reading
from the default framebuffer, is RGB565, which is why it was
chosen for WebGL. When reading from FBOs it is probably whatever
format the renderbuffer is, i.e. it will be dependent on both
application and implementation.
On 2010-11-01 21:09, Vladimir Vukicevic wrote:
Ah, I didn't realize that it could vary based on the bound framebuffer.If we want to change it I would prefer dropping implementation dependent read format and either only support RGBA8888 or require software conversion to support any format.
It was suggested that we fix the type because it was an odd implementation-specific variance that wasn't covered by an extension that could be queried.Â But that made sense when we weren't thinking of it as framebuffer-specific; since it does vary, then I agree that it doesn't make sense to fix it (since most everything with fbos is implementation-dependant anyway!).Â Happy to change them back.
begin:vcard fn:Mark Callow n:Callow;Mark org:HI Corporation;Graphics Lab, Research & Development adr:Higashiyama 1-4-4, Meguro-ku;;Meguro Higashiyama Bldg 5F;Tokyo;;153-0043;Japan email;internet:firstname.lastname@example.org title:Chief Architect tel;work:+81 3 3710 9367 x228 tel;fax:+81 3 5773 8660 x-mozilla-html:TRUE url:http://www.hicorp.co.jp, http://www.mascotcapsule.com version:2.1 end:vcard