https://bugs.freedesktop.org/show_bug.cgi?id=72600
--- Comment #6 from org.freedesk...@io7m.com --- I think the main issue here is that the ES3 context doesn't actually correctly identify itself as such. As described in the JOGL tracker, the problem is that JOGL first requests an ES2 context (and rejects the ES3 context that is actually returned, more on that in a moment), and then tries an ES3 context but rejects that because it doesn't have the correct type bits set. As for rejecting an ES3 context when an ES2 context is requested, that's actually rooted in: https://jogamp.org/bugzilla/show_bug.cgi?id=852 As you can see from my comments at the bottom of 852, I'm not convinced that ES3 and ES2 are incompatible either (my original statement made on the mailing list appears to be in error). As I said, evidently the context returned by Mesa on Intel drivers *does* correctly identify itself as ES3, so there appears to be an (albeit minor) bug on the AMD side. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
