search

MillersvilleCS / MoleculeFlashcardsAndroid

2 stars 0 forks source link

Failed to create Shader on Game Screen load #5

Closed saschlac closed 10 years ago

saschlac commented 10 years ago

This is running on a Samsung Galaxy Player 4.0 running CM11. The game crashes when loading the game screen. The logger output the following messages:

04-08 14:16:31.227: I/ActivityManager(3979): Timeline: Activity_launch_request id:com.millersvillecs.moleculeandroid time:1042697
04-08 14:16:31.661: W/System.err(3979): com.millersvillecs.moleculeandroid.util.GraphicsException: Failed to create Shader
04-08 14:16:31.672: W/System.err(3979):     at com.millersvillecs.moleculeandroid.graphics.opengles.ShaderProgram.compileShader(ShaderProgram.java:79)
04-08 14:16:31.672: W/System.err(3979):     at com.millersvillecs.moleculeandroid.graphics.opengles.ShaderProgram.<init>(ShaderProgram.java:17)
04-08 14:16:31.676: W/System.err(3979):     at com.millersvillecs.moleculeandroid.AndroidRenderer.onSurfaceCreated(AndroidRenderer.java:135)
04-08 14:16:31.676: W/System.err(3979):     at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1503)
04-08 14:16:31.696: W/System.err(3979):     at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1242)
04-08 14:16:31.887: I/ActivityManager(3979): Timeline: Activity_idle id: android.os.BinderProxy@420d6b30 time:1043358
04-08 14:16:39.622: W/dalvikvm(3979): threadid=12: thread exiting with uncaught exception (group=0x41c83ce0)
04-08 14:16:39.625: E/AndroidRuntime(3979): FATAL EXCEPTION: GLThread 359
04-08 14:16:39.625: E/AndroidRuntime(3979): Process: com.millersvillecs.moleculeandroid, PID: 3979
04-08 14:16:39.625: E/AndroidRuntime(3979): java.lang.NullPointerException
04-08 14:16:39.625: E/AndroidRuntime(3979):     at com.millersvillecs.moleculeandroid.scene.SceneObject.render(SceneObject.java:39)
04-08 14:16:39.625: E/AndroidRuntime(3979):     at com.millersvillecs.moleculeandroid.scene.SceneNode.render(SceneNode.java:39)
04-08 14:16:39.625: E/AndroidRuntime(3979):     at com.millersvillecs.moleculeandroid.scene.Scene.render(Scene.java:15)
04-08 14:16:39.625: E/AndroidRuntime(3979):     at com.millersvillecs.moleculeandroid.AndroidRenderer.onDrawFrame(AndroidRenderer.java:112)
04-08 14:16:39.625: E/AndroidRuntime(3979):     at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1525)
04-08 14:16:39.625: E/AndroidRuntime(3979):     at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1242)
04-08 14:16:39.875: I/ActivityManager(3979): Timeline: Activity_idle id: android.os.BinderProxy@42080568 time:1051345
04-08 14:16:44.227: I/Process(3979): Sending signal. PID: 3979 SIG: 9
04-08 14:16:45.032: I/ActivityManager(4021): Timeline: Activity_idle id: android.os.BinderProxy@41f19af0 time:1056503
CMahaff commented 10 years ago

I'll pass this to Will, could be this Will? http://stackoverflow.com/questions/5221681/failing-to-compile-shader-known-to-be-good-on-android

That said, it could be that device having a problem. It's 4.0 build isn't official and it might not support opengl ES 2.0 properly, like devices that got the official update. I'll see what Will thinks though.

CMahaff commented 10 years ago

Device was running OpenGl 1.0 and was thus not compatible.