"OpenGL ES not in 0"

[davidmaxwaterman]

Hi,

When I run our player, which works fine on the N93 and N95, on a 3250, it displays the message :

"
App. closed:
Player
OpenGL ES not in 0
"

Anyone any idea what this message is about?

Max.

[davidmaxwaterman]

I'm still having this problem, if anyone has any ideas....

[malmrose]

I've never seen that message before, but N93 and N95 have OpenGL ES 1.1, whereas the 3250 has OpenGL ES 1.0. Could you be trying to use 1.1 features?

[ocr_iwan]

i encountered said error message when SizeChanged() was called by the api framework, with SizeChanged calling glViewport(), and OpenGl beeing initialized in a different thread, or by a static function (at least as far as i remember).

[davidmaxwaterman]

i encountered said error message when SizeChanged() was called by the api framework, with SizeChanged calling glViewport(), and OpenGl beeing initialized in a different thread, or by a static function (at least as far as i remember).

I finally got to the point where I had to fix this problem, and it turns out you were correct. I had a 'setwindowsize()' function that was making opengles calls - it was being called by the ui code, of course. This worked fine on OpenGL ES 1.1, but not 1.0. I changed it to set a flag, and moved the opengles calls to the part of the code that did the swapbuffers(), and put an 'if ( flag )' around it.

Just to clear up this thread