<check_framebuffer_attachment:789>: Invalid texture format! Returning error!

I'm getting the following log entries for my application:


<check_framebuffer_attachment:789>: Invalid texture format! Returning error!
<check_framebuffer_object_status:1185>: Framebuffer color attachment incomplete. Returning GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT!
<check_framebuffer_object_status:1185>: Framebuffer color attachment incomplete. Returning GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT!
<check_framebuffer_attachment:789>: Invalid texture format! Returning error!
<check_framebuffer_object_status:1185>: Framebuffer color attachment incomplete. Returning GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT!
<check_framebuffer_attachment:789>: Invalid texture format! Returning error!

Followed by a crash, is there any way to change the framebuffer format?

Thanks,

Jon

 

Hey Masterfalcon,

Not sure you could, basically my release to the Gear S2 was going great until I got report of a crash on the 3G versions of the device, these use an Adreno GPU instead of a Mali, I have a feeling in Tizen builds you guys are only concerned for Mali because the Z1 and Z3 are Mali based I believe, and I think Adreno needs a different Framebuffer format. I tested on a 3G device I borrowed and thats where I see the above error, on a normal S2 and Classic it works fine. Although Gear S2 on here:

http://developer.samsung.com/remotetestlab/rtlDeviceList.action

Is the 3G version and does also exhibit the error above...but I'm guessing as you guys are only supporting the Z1 and Z3 I may be out of options...unless the option to disable the Framebuffer exists in someway?

Thanks,

Jon

 

Yes I do, I'll do you a repro and post the number here within the hour.

Thanks!

 

Here you go:
Case 763618

Do you know if they plan to support the watches in the future, on the other S2 and Classic it works flawlessly so I'm surprised Samsung aren't pushing it forward!