OpenGL multi texture corrupts evas object on device
OpenGL multi texture corrupts evas object on device
BY 04 May 2019Native Application Development
Hi,
I’m working on a watch face that has some OpenGL ES 3.0 drawn on a image surface and som other ordinary image objects for the watch face for exampel the hour and minute hands. It works perfect on the emulator and on device as longa as I only has one texture loaded in OpenGL.
As soon as I start using a second or more textures in OpenGL then all other object are turned in to black boxes on my Gear S3 but are ok on the emulator except if the original image is twice as big or bigger as the one I want to show on the screen, really weird bug.
Edje images are also turned in to black frames.
The second texture and the images works ok in the emulator. As a workaround I have made all the images with twice the size and it works ok except when I do evas_map_util_rotate for the second hand and the angel is 0 degrees or 360. It works all the way around for all other angels but not for 0 where the image get black with alpha 1. Very annoying!
If I remove specular in above then all works as normal on both emulator and my device a Gear S3.
I shrunk the OpenGL textures just to see if it was a memory problem but it did not have any effect and the OpenGL stuff works ok on the device.
This is the rotate source that doesn’t work for 0 degrees:
OpenGL multi texture corrupts evas object on device
Hi,
I’m working on a watch face that has some OpenGL ES 3.0 drawn on a image surface and som other ordinary image objects for the watch face for exampel the hour and minute hands. It works perfect on the emulator and on device as longa as I only has one texture loaded in OpenGL.
As soon as I start using a second or more textures in OpenGL then all other object are turned in to black boxes on my Gear S3 but are ok on the emulator except if the original image is twice as big or bigger as the one I want to show on the screen, really weird bug.
Edje images are also turned in to black frames.
The second texture and the images works ok in the emulator. As a workaround I have made all the images with twice the size and it works ok except when I do evas_map_util_rotate for the second hand and the angel is 0 degrees or 360. It works all the way around for all other angels but not for 0 where the image get black with alpha 1. Very annoying!
The fragment shader:
If I remove specular in above then all works as normal on both emulator and my device a Gear S3.
I shrunk the OpenGL textures just to see if it was a memory problem but it did not have any effect and the OpenGL stuff works ok on the device.
This is the rotate source that doesn’t work for 0 degrees:
I do not know what to do with the multi texture problem and it is a mayor bug.
Has anyone else manage to use multiple textures and also used evas image object without any problems ?
/Christian
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio