Notices


Reply
Thread Tools
Posts: 313 | Thanked: 1,373 times | Joined on Aug 2016 @ Estonia
#11
As you can see at the end of https://github.com/mapbox/mapbox-gl-native/issues/10029 , Mapbox GL developer suggested that MapboxGL hits memory bottleneck on Jolla 1.

Unfortunately, the callbacks designed to help with the debugging of openGL errors were introduced only in the latest standard, not available for J1 either.

So, if you needed an excuse to go out and get a newer device for SFOS - here it is.
 

The Following 3 Users Say Thank You to rinigus For This Useful Post:
Posts: 229 | Thanked: 959 times | Joined on Oct 2013 @ France
#12
Originally Posted by rinigus View Post
As you can see at the end of https://github.com/mapbox/mapbox-gl-native/issues/10029 , Mapbox GL developer suggested that MapboxGL hits memory bottleneck on Jolla 1.
Alright. At least we tried ! Thanks for the time you spent on this.

Originally Posted by rinigus View Post
Unfortunately, the callbacks designed to help with the debugging of openGL errors were introduced only in the latest standard, not available for J1 either.
Just to understand, what do you call a "standard" in this context ? A version of the mapbox GL renderer ? Of the Qt API for Mapbox GL ? Something else ?
 

The Following 3 Users Say Thank You to Zeta For This Useful Post:
Posts: 313 | Thanked: 1,373 times | Joined on Aug 2016 @ Estonia
#13
Originally Posted by Zeta View Post
Alright. At least we tried ! Thanks for the time you spent on this.

Just to understand, what do you call a "standard" in this context ? A version of the mapbox GL renderer ? Of the Qt API for Mapbox GL ? Something else ?
I looked a bit into it and this is a what I found regarding opnGL debugging https://blog.nobel-joergensen.com/20...ng-glgeterror/

To debug properly, we need OpenGL ES API Version 3.2 and use https://www.khronos.org/registry/Ope...Callback.xhtml (blog post continuation)

Alternatively, you could use glGetError, as explained in the blog post.

As for API versions, OpenGL ES 3.0 corresponds to Android 4.3 (https://en.wikipedia.org/wiki/OpenGL_ES)

So, out of luck here as well on older devices like J1
 

The Following 5 Users Say Thank You to rinigus For This Useful Post:
Posts: 229 | Thanked: 959 times | Joined on Oct 2013 @ France
#14
Originally Posted by rinigus View Post
I looked a bit into it and this is a what I found regarding opnGL debugging https://blog.nobel-joergensen.com/20...ng-glgeterror/

To debug properly, we need OpenGL ES API Version 3.2 and use https://www.khronos.org/registry/Ope...Callback.xhtml (blog post continuation)

Alternatively, you could use glGetError, as explained in the blog post.

As for API versions, OpenGL ES 3.0 corresponds to Android 4.3 (https://en.wikipedia.org/wiki/OpenGL_ES)

So, out of luck here as well on older devices like J1
Thanks for the answer, I understand now that you were talking of the OpenGL standard.
Interesting to see that debugging is a first class citizen on the newer versions.
 

The Following User Says Thank You to Zeta For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 02:57.