Hi there,
I just discovered jME3 today and downloaded the SDK. It’s pretty cool!
However, there’s an issue I’m having and it occurs after running anything. If I run one of the examples and then hit escape or close the application in any other way, within 10 seconds of closing I get an error saying that Java has quit working and it always ask if I want to send the error report to Miscrosoft or not. It happens every single time.
I’m running Windows 7 Home Premium 64-bit andI have JDK 7installed and Java 7 update 3 on my system, both 64-bit. Is this a common problem or am I just missing something? I also can’t seem to install updates for jME3 but it says that may just be a server error.
This isn’t a horrible problem, everything still works as it’s supposed to, it’s just annoying having to wait to close a dialog claiming that Java stopped working every time I run something.
If anyone can help me figure out what’s up, I’d greatly appreciate it!
Did you update the SDK to the latest stable version (Help->Check for updates)? This is a known issue in lwjgl and has been (mostly) solved in the latest updates. I heard of some people still having issues at times but I think that was due to old openal.dll / lwjgl.dll files lying around.
Uh, did you click “disable plugins” when you got a warning about the JDK at the start? This should only happen if you somehow have the main jme plugins (SDK-Core etc) disabled. (And are you sure all firewall/antivirus software etc. is informed and you internet works for that matter)?
Heh, didn’t even think about checking the firewall!
I went in and added jMonkeyEnginePlatform to the “Allowed programs” section of the firewall and now it seems to be downloading and installing all 23 updates! I’ve been waiting for like 15 minutes for it to finish, which I hope is good news.
Halfway through downloading I checked “Run in Background” to test out some more sample applications, and now when I close them I don’t get the error message anymore, so it must be working already. 
Thanks, normen!
@coffeecoder said:
Halfway through downloading I checked "Run in Background" to test out some more sample applications, and now when I close them I don't get the error message anymore, so it must be working already. :) Thanks, normen!
During the update? Sounds a bit scary as they should only be unpacked after download but good you got the updates working ^^
Arrrgh. Got to 99% and then I started getting the errors again and another message saying that the server may be down. To verify, I completely disabled the firewall and it still didn’t work (although the downloading process went much faster with it disabled). Can anyone else verify if the server is down or if I’m just incredibly unlucky at the moment? Maybe I should reinstall JDK?
Hm, I’d just restart and retry, maybe keep the window open idk… We had some server issues some time ago but they seem to be gone since we moved the server…
Er, to be clearer it didn’t install the plugins at all. I got the same message as before in one of my previous posts.
BTW, is there a way to edit my posts?
@coffeecoder said:
BTW, is there a way to edit my posts?
Join the "jMonkeyEngine SDK" group (button all the way on top, its not there for me anymore :)).
Found the problem!
jME3 doesn’t seem to play nice with JDK 7+, so I installed JDK 6u32 and it worked instantly; updates installed, no more error messages, and perhaps most interesting of all is how much faster the examples run. Previously, they weren’t running any faster than 999 FPS, but now I’m getting 3000+! And I only have a 550 Ti so that’s really encouraging (let’s just hope I don’t fry this sucker!).
Thanks again normen!
If they weren’t running faster than 999 then it was that you hadn’t upgraded. They were running faster than that but there was a bug where no greater than 999 FPS would be reported.
I find this odd. I’ve had JDK 7 since it’s been out and never had a problem.
@pspeed said:
If they weren't running faster than 999 then it was that you hadn't upgraded. They were running faster than that but there was a bug where no greater than 999 FPS would be reported.
Ah, that would explain why even though the FPS reports 3000+ they don't seem ANY faster than previously reported. :P
@madjack said:
I find this odd. I've had JDK 7 since it's been out and never had a problem.
Which version of JDK 7 do you have? I was using update 3, 64-bit. Perhaps you're using an older version that works better? Either that or something else was wrong and I managed to fix it in-between removing JDK 7 and installing JDK 6.
Well, I’ve had it since it’s been out, thus there wasn’t any update at that time. But I’ve upgraded at each upgrade without any problem.
Right now I’m using JKD 7.0 x64 and afaik I’ve got the update 4 installed too.
Just to point something out>>>
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7077696
This has been a bug since forever, so i wouldnt use jdk x64 for a while until they fix it, of course its low priority to them, but it is a bug in the jdk where it uses ipv6 by default for doing stuff with ftp, which the windows firewall finds weird and blacklists you. Oracle claims its not the expected behavior of the OS since its not blocked for ipv4.
Hope that helps, ive been running into this issue too. Also there seems to be a flag you can set to force it to do ipv4 by default, which might fix this problem on jmonkeys side.
UPDATE: forgot to mention you are running into this problem because of 2 factors, you are using 64 bit windows, and you are using 64 bit version of jdk 7. I have heard that it works fine on x86, switching to jdk6 will help, either 64 or 86 is fine. Ironically enough if you arent doing anything with ftp this isnt even a problem, but unfortunately netbeans uses ftp to do updates, so if you can live without them you probably will never have this problem.
Again, I’m using JDK x64 7u4 on Windows 7 x64 and I haven’t had any problems. (For once I’m not the one having issues and before anyone says it was caused by that issue, it wasn’t).
Anyway, hopefully that can be worked around for those that have it.
I get the same issue as you about the “java crashing after you close the game” and have had it for about 6 months? Both on my laptop and new sexy desktop. Both 32/64 bit windows and java 6/7
@wezrule said:
I get the same issue as you about the "java crashing after you close the game" and have had it for about 6 months? Both on my laptop and new sexy desktop. Both 32/64 bit windows and java 6/7
I also have that, although it happens a lot less than a couple of months ago. Anyway, that's a known LWJGL problem. It doesn't have anything to do with JME or the SDK themselves.