ptitSeb
ptitSeb
So, it's some kind of gamma issue? How do you know wich version is correct?
I've just tested on my Pandora, and while I noticed an issue with the transparency issues (weapon in hand, but also some flowers), I have witnessed any red-ish issue with...
I tried with latest gl4es (1.1.2) and didn't reproduced any bugs on my side (it was a quick test). Also, just to note, implementation of VBO in gl4es halped speedup...
Ah damn, right. I haven't looked at the right thing when testing! I still need to investigate this one.
I need the actual shader sources. Use `LIBGL_LOGSHADERERROR=1` to get shader sources (before and after transformation) that fail compilation or linking.
I see it's cycling on a glX call... Try with this: a001dc33825fa2624a385670ed1c1ce2a113267e I think it should help.
The replay in torcs works for the menu, but crashes once replay the "in-game" part for me.
enabling extension is fine, but happens when the extension is not supported? a workaround for `GL_EXT_shader_non_constant_global_initializers` is not trivial to write.
Well, that trace has been done with gl4es too, not with Mesa, that can help.
I played the trace on my regular PC and apitrace crashed at the same point. So the problem is not in the apitrace replay but in the recorded trace itself....