hi , on android i sometimes get this error and sometimes not!
I dont even use Vector4f or quaternion in my code
i think if the error comes it happens when i detach an appstate if that is helpful…
(On pc it works fine)
hi , on android i sometimes get this error and sometimes not!
I dont even use Vector4f or quaternion in my code
i think if the error comes it happens when i detach an appstate if that is helpful…
(On pc it works fine)
We need to see the exception stack trace.
See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for some general guidelines on problem reporting.
/AndroidHarness(23326): Exception thrown in Thread[GLThread 5794,5,main]
E/AndroidHarness(23326): java.lang.ClassCastException: com.jme3.math.Vector4f cannot be cast to com.jme3.math.Quaternion
E/AndroidHarness(23326): at com.jme3.renderer.android.OGLESShaderRenderer.updateUniform(OGLESShaderRenderer.java:657)
E/AndroidHarness(23326): at com.jme3.renderer.android.OGLESShaderRenderer.updateShaderUniforms(OGLESShaderRenderer.java:709)
E/AndroidHarness(23326): at com.jme3.renderer.android.OGLESShaderRenderer.setShader(OGLESShaderRenderer.java:890)
E/AndroidHarness(23326): at com.jme3.material.Material.renderMultipassLighting(Material.java:839)
E/AndroidHarness(23326): at com.jme3.material.Material.render(Material.java:1049)
E/AndroidHarness(23326): at com.jme3.renderer.RenderManager.renderGeometry(RenderManager.java:525)
E/AndroidHarness(23326): at com.jme3.renderer.queue.RenderQueue.renderGeometryList(RenderQueue.java:301)
E/AndroidHarness(23326): at com.jme3.renderer.queue.RenderQueue.renderQueue(RenderQueue.java:353)
E/AndroidHarness(23326): at com.jme3.renderer.RenderManager.renderViewPortQueues(RenderManager.java:765)
E/AndroidHarness(23326): at com.jme3.renderer.RenderManager.flushQueue(RenderManager.java:721)
E/AndroidHarness(23326): at com.jme3.renderer.RenderManager.renderViewPort(RenderManager.java:985)
E/AndroidHarness(23326): at com.jme3.renderer.RenderManager.render(RenderManager.java:1031)
E/AndroidHarness(23326): at com.jme3.app.SimpleApplication.update(SimpleApplication.java:251)
E/AndroidHarness(23326): at com.jme3.app.AndroidHarness.update(AndroidHarness.java:485)
E/AndroidHarness(23326): at com.jme3.system.android.OGLESContext.onDrawFrame(OGLESContext.java:332)
E/AndroidHarness(23326): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1464)
E/AndroidHarness(23326): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1218)
This should be fixed in the nightly build
i updated but nothing changed
How did you update?
It’s definitely fixed in last nightly, so you might have made a mistake
mhm… in the sdk was a bubble “25 updates available” i clicked on that and so on…
is there another way?
Are you on the nightly updates or stables?
mhm how do i update “nightly”?
dont know where the differance is…
oh ok
i read the manual and now it makes more sence to me
@TripleS said: oh ok i read the manual and now it makes more sence to me ;)
I think some of us just shed a little tear of joy…
…
mhm…
i updated now and now it seems that the mouse coordinates go wild !!!(on Android)
i press somewhere but my joystick appears somewhere else and if i go up with the finger the stick goes down…
This happens to me when I have several lights. When I have one light which is the only situation I tested, the error goes away.
how can i invers the mouseaxis?
and how can i detect if its neccesary? Is this now general that the mouse need to be inversed ? or is this only on my device like this?
if( the app is on android ){
mouse.inversAxis()
}
or how does this work??
In your Android source java file there are two lines:
mouseEventsInvertX = true;
mouseEventsInvertY = true;
You might want to tinker with them if you don’t find a more appropriate way to invert the axes.
At the time of the last stable update, the mouse coordinates for Android were the opposite of a mouse if you were using the simulated mouse events. This meant that users had to invert Y to get the touch coordinates to mimic mouse coordinates. A while ago the settings for invert X and Y were changed to have a default setting that matched the desktop mouse. Now, manually inverting the touch coordinates should not be necessary and the same app logic can apply to a desktop app or an android app.