By the way is there any trick to "track" a GL error to find the object triggering it? (apart deleting objects until you find the one)
cyrille henry escribió:
Matteo Sisti Sette a écrit :
cyrille henry escribió:
you try to get value from the stack when it is empty.
you can have such error when using glPopMatrix without using glPushMatrix...
First of all thank you for helping.
I never explicitly use these functions, that is, I never use [GEMglPopMatrix] nor [GEMglPushMatrix].
I guess [separator] has something to do with pushing and popping from that matrix, but shouldn't its push and pop operations always automatically "match"?
yes, it should
Whay kind of anomaly in a patch can cause a call to a pop without a "matching" push?
save your patch. simplify it until it did not print this error. You can then find the cause of this inappropriate pop...
Do you think it is unrelated to the use of shaders?
i never saw a shader doing this kind of error. you can easily test this if you remove the shader from the rendering pipe...
c
Btw is that the only stack that can underflow?
Thanks
why do you always send your mail to the pd list AND gem-dev? this 2 lists are for different purpose, and people on Gem-dev are also on pd-list.
Oh sorry about that. Maybe I shouldn't; I'll stop doing that right now. Since there isn't (to my knowledge) a "gem-list", specific to gem but not to developing, I thought I'd send gem-related questions to gem-dev too... You make me realise it is unnecessary and probably inappropriate, if most people in gem-dev are also on pd-list.