@normen said: Okay cool, I just didn't expect many people to have that already because we didn't officially announce it yet :)
Yeah, I wanted to make sure it wasn’t something that would be fixed with the latest version. With 4.3 and opengl es 3.0 I figured there would be some updates. 
@Blockhouse said: @iwgeric Here's the crash log after the nightly build. Still using ConfigType.BEST.
Well, the error code from the GPU explains why all 0’s were being logged instead of the selected config.
I’ve got a couple of ideas that I want to try, but I don’t want to commit changes to try out some ideas. I will probably package up a jme3-android.jar for you to try with some different code in this area.
In order to include the custom jar, you’ll need to create a global library in Netbeans (ie sdk) and point it to the new jar file. Also, there will be a target you’ll need to add to build.xml to replace the standard jme3-android.jar with the new one during the build process of your project. Example below:
[java]
Adding custom libraries for android.
[/java]
If this is something you can do, then I’ll package up a new jar file for you to try.
@iwgeric:
I put more error checking in so you actually see the error where it happens. Should be available in today’s nightly.
@iwgeric said: Link to temporary jME3-android.jar file
That did it! Thank you very much for all your efforts.
That’s good. I’ll need to fix it for real and commit it, but at least we now know what needs to be done.
It is interesting that you appear to be the only one having the issue (at least that I’ve heard of). Do you happen to have an hdmi cable connected from the device to a monitor or anything similar?
For some reason with your device, the system is using an EGLDisplay that is not the default display. Not sure why, but that is why the exception was happening.
Can you think of anything about your hardware configuration that might explain that?
I have used an hdmi cable connected to the tablet in the past, but not currently. We do use this app connected via hdmi when it is deployed.
The tablet is connected to my computer via usb cable, and is in developer mode. Those should be the only out of the ordinary configurations.
Feel free to use the temp jar file for now until I can get an official patch committed.
Thanks for the good information and testing.
Will do. Thanks again.
@Blockhouse said: Will do. Thanks again.
I went ahead and committed a partial update that will at least take care of your issue. This will allow me to take some more time to clean up this area better.
Please take a look at the nightly tomorrow to see if the new committed fix takes care of your issue. After you update the sdk tomorrow, don’t forget to remove the target you added to build.xml so that you go back to using the jME3-android.jar that will be built tonight.
Thanks again for helping us debug this one.
@iwgeric said: I went ahead and committed a partial update that will at least take care of your issue. This will allow me to take some more time to clean up this area better.Please take a look at the nightly tomorrow to see if the new committed fix takes care of your issue. After you update the sdk tomorrow, don’t forget to remove the target you added to build.xml so that you go back to using the jME3-android.jar that will be built tonight.
Thanks again for helping us debug this one.
I got a new crash with the latest nightly:
I removed the target from the build.xml, and I believe it’s pulling the new jME3-android.jar. Possible I did something else wrong?
@Blockhouse said: I got a new crash with the latest nightly: http://pastebin.com/zYM2191sI removed the target from the build.xml, and I believe it’s pulling the new jME3-android.jar. Possible I did something else wrong?
I must appologize. You did the right thing, but it appears that the build failed last night so you got the update from 2 nights ago which was only the additional debug that @Momoko_Fan committed.
I’m not sure it the build issue was fixed or not, so I’ll let you know when the build completes successfully. For now, you’ll have to put the target back in and use the jar I sent.
Sorry again for the wasted effort.
@iwgeric said: I must appologize. You did the right thing, but it appears that the build failed last night so you got the update from 2 nights ago which was only the additional debug that @Momoko_Fan committed.I’m not sure it the build issue was fixed or not, so I’ll let you know when the build completes successfully. For now, you’ll have to put the target back in and use the jar I sent.
Sorry again for the wasted effort.
No problem, I’m in no rush to push out the update.
@Blockhouse said: No problem, I'm in no rush to push out the update.
It looks like the nightly updates are building again if you want to give it a try. (again, don’t forget to remove the target in build.xml)
@iwgeric said: It looks like the nightly updates are building again if you want to give it a try. (again, don't forget to remove the target in build.xml)
Sorry it took me a little while to get back to you. I’m still getting a crash. I believe everything is updated to 3.0.1?
Unfortunately, you’re not using the latest update somehow.
Can you look at the plugins menu of the SDK and tell me what version it says the jMonkeyEngine3 Library is?
Here is what mine says:
@Blockhouse said: @iwgeric, my fault. All runs perfectly. Thanks again for all your work!
Just FYI, There was an update for Stable last night to bring the engine to 3.0.3. I put in some of the changes to remove this issue so you don’t have to run with Nightly.