Posted by Pete on Feb 29, 2016; 9:49am
URL: https://forum.jogamp.org/GL-INVALID-OPERATION-after-calling-ShaderState-glUniform-tp4036347p4036382.html

All sorted - turns out indeed I was doing something silly.

I was reusing the same matrix GLUniformData between different shaders - as each shader referenced the model and viewprojection matrices via the same name I'd gone along with the assumption this was ok, especially as it was working on my primary dev machines.

But! This was only by chance, because my machines driver impl of glGetUniformLocation was return the same value for these two matrices in each shader. On the borken machines - guess what - it didn't, and hence the booms.

I'm re-working now to address the problem. Thank you for listening to my ramblings! Its nice to know there are people who care :)