Is there any download for JME NB plugins such as model converter? Because I’ve already set up my workflow over “normal” NB and don’t want to do this all over again with SDK’s NB IDE (as it is based on that), plus I am low on disk space (old 80gb HDD as my 1TB one fried)
Just add the SDK’s modules link to the plugin settings’ “Configuration of Update Centers”.
Nightly: http://jmonkeyengine.com/updates/nightly/3.0beta/plugins/updates.xml
Stable: http://jmonkeyengine.com/updates/stable/3.0beta/plugins/updates.xml
jMonkeyEngine SDK User Contributions : http://jmonkeyengine.com/updates/contributions/updates.xml
NOTE that I’m not responsible if there’s a screw up. You do this on your own accord. Those might break your installation. You have been warned.
Better yet, RMA that fried HD or get a new (real harddrive) one.
I don’t think reanimating this harddrive will do something. It was literally fried up (both electronics and discs) so I’ve thrown it away (tried to get data from data recovery company, but they wasn’t able to help) and I don’t have money for new HDD right now.
Also when doing update from my NB 7.0.1 installation on stable plugins (won’t risk nightly), I’ve got nice 403, though loading very same url (http://jmonkeyengine.com/updates/stable/3.0beta/plugins/updates.xml) into browsers load it fine. Strange. DRM, perhaps?
@dariuszg-jagielski said:
I don't think reanimating this harddrive will do something. It was literally fried up (both electronics and discs) so I've thrown it away (tried to get data from data recovery company, but they wasn't able to help) and I don't have money for new HDD right now.
Doesn't matter how it was fried. Unless it's your fault, the manufacturer should honor its warranty. Even if it's your fault, you send it back feigning ignorance. :P
Also when doing update from my NB 7.0.1 installation on stable plugins (won't risk nightly), I've got nice 403, though loading very same url (http://jmonkeyengine.com/updates/stable/3.0beta/plugins/updates.xml) into browsers load it fine. Strange. DRM, perhaps?
DRM? You kidding me right? This isn't UbiShit. :facepalm:
It's possible the way the SDK polls or the answer it expects are different from the way Netbeans does it. I guess you'll have to wait until @normen comes around and read this thread.
This DRM thing was a joke, don’t get nervous. I just have strange sense of humor. And my HDD was 3 months after warranty ended when it was fried, so…
It looks like the requests are never even making it to our server. If I go to that URL in a browser the request shows up in the Apache logs… if I try to access it from NB 7.1 it gives me the 403 error.
Edit: So @normen has reminded me that the requests are being blocked by Cloudflare if the HTTP request headers aren’t modified before being sent to the server.
Update:
Try using the update URL with the .org domain: http://hub.jmonkeyengine.org/updates/stable/3.0beta/plugins/updates.xml
Thanks, it works!
I strongly recommend not installing the plugins in a normal netbeans install and using the SDK, the plugins are not meant for NetBeans.
Weird, I’ve thought it is just NB with plugins (wiki states that it is build upon NetBeans, which I assume are plugins). Anyway, it destroyed my installation (had to reinstall NB, upper side is that I’ve upgraded from 7.0.1 to 7.1.2), so I guess you’re right.
Anyway, performance with .obj models and .mtl materials is good enough, so I think I don’t need j3o/j3m for now (and opposite to what Tutorial says, it DOES run from inside of jar, it’s just matter of adding assets directory to list of source packages (project’s properties->Sources->add folder in upper side (Source packages folders), select assets dir))
…which the tutorial says as well but we don’t make you do things to suffer but because you have less issues on the way to a complete game. Its just better for various reasons to use j3o files in-game.