android - Differences rendering a gradient using a FBO in GLES2 and GLES3 -


i'm using jogl part of cross platform app. i'm requesting gles2 gl profile used.

i've got fbo bound , content drawn it, before unbinding & drawing backing texture screen - pretty standard draw-to-texture stuff.

i've got 3 different types of drawing i've tested far, block colour shader, gradient shader, , texture shader. of these working far when drawn default frame buffer across devices.

hardware involved in tests:

linux laptop: renderer: mesa dri intel(r) sandybridge mobile. version: opengl es 3.0 mesa 10.1.3. gl profile: glprofile[gles2/gles3.hw].

android samsung galaxy s3: renderer: mali-400 mp. version: opengl es 2.0. gl profile: glprofile[gles2/gles2.hw].

android samsung tab 4: renderer: mali-t628. version: opengl es 3.0. gl profile: glprofile[gles2/gles3.hw].

when testing rendering texture using fbo, i'm getting odd behaviour gradient shader only, , on galaxy tab 4. happens don't visual result drawing content of fbo, not clear colour used clear fbo before drawing gradient - , said gradient work under other circumstances.

furthermore, galaxy tab 4 gives same correct consistant results if draw block colour shader or texture fbo & draw fbo content default frame buffer.

so big question - why doesn't gradient draw fbo work on tab 4? hunch it's gles3 implementation on tab 4 regarding frame buffers, i'm @ loss of go here.

whereas galaxy s3 uses gles2 , normal gl_framebuffer component, tab 4 running gles3 , uses gl_draw_framebuffer , gl_read_framebuffer - remember it's fine drawing block colour or texture fbo, gradient doesn't show up. said, odd..

thanks reading.


Comments

Popular posts from this blog

python - No exponential form of the z-axis in matplotlib-3D-plots -

php - Best Light server (Linux + Web server + Database) for Raspberry Pi -

c# - "Newtonsoft.Json.JsonSerializationException unable to find constructor to use for types" error when deserializing class -