PlayN 1.4 and OpenGL

[GoogleCodeExporter]

Hi all.
My team is using PlayN for project. In the past our project was basing on PlayN 
1.3 and worked fine. But after change to 1.4 version we caught a very strange 
problem. Only on two workstations java(desktop version) project can't start to 
work correctly. Each of them have video card as Radeon HD 6450 and other PC's 
have different from this. This problem linked only with video card HD 6450, 
because after I switched to on-board video adapter my project started 
succesfully.

I researched source code in debug mode and I see one problem.
class org.lwjgl.opengl.GL20
static native int nglGetUniformLocation(int program, long name, long 
function_pointer);
return -1; but input parameters are more then "0"

Windows 7, JDK 1.6_33, adapter drivers: 8.803.0.0 ( native ATI )

P.S. I will attach stacktrace in future.

Original issue reported on code.google.com by mihail.k...@gmail.com on 2 Aug 2012 at 6:27

[GoogleCodeExporter]

java.lang.NullPointerException
 at playn.core.gl.QuadShader$QuadCore.prepare(QuadShader.java:140)
 at playn.core.gl.GLShader.prepareTexture(GLShader.java:114)
 at playn.core.gl.ImageGL.draw(ImageGL.java:99)
 at playn.core.gl.ImageLayerGL.paint(ImageLayerGL.java:112)
 at playn.core.gl.GroupLayerGL.render(GroupLayerGL.java:165)
 at playn.core.gl.GroupLayerGL.paint(GroupLayerGL.java:160)
 at playn.core.gl.GroupLayerGL.render(GroupLayerGL.java:165)
 at playn.core.gl.GroupLayerGL.paint(GroupLayerGL.java:160)
 at playn.core.gl.GroupLayerGL.render(GroupLayerGL.java:165)
 at playn.core.gl.GroupLayerGL.paint(GroupLayerGL.java:160)
 at playn.core.gl.GL20Context.paintLayers(GL20Context.java:74)
 at playn.java.JavaGraphics.paint(JavaGraphics.java:163)
 at playn.java.JavaPlatform.run(JavaPlatform.java:258)
 at playn.core.PlayN.run(PlayN.java:47)
 < on load of my project >

Original comment by mihail.k...@gmail.com on 2 Aug 2012 at 7:32

[GoogleCodeExporter]

Hello,
I had the same problem with a Radeon 5700. I updated the drivers (the last 
v12.6, date : 2012-06-28), and the problem disappeared.

Original comment by xavier.b...@gmail.com on 13 Aug 2012 at 12:16