1: How does light affect system resources? Do different kinds of light drain on FPS more than others?
2: Is memory freed up when you detach light or a model from the rootNode?
3: why does the SDK crash every five minutes on linux? I dualboot Arch & windows, I hate to use windows for development because its slow, everything crashes all the time & I just don’t like the desktop environment, I find gnome3 (a linux environment) to be much more efficient for development. I’m being forced to use windows more & more because almost everytime I open the material editor, occasionally when I open the SceneComposer or when I create a new terrain the SDK just closes. My buddy uses Ubuntu & he gets even more crashes (from what I’ve heard). Also, when I can get the material editor open, I can’t change any of the check boxes in additional RenderState, it wrks on windows though. I’m not moaning, just wondering if & when you will get more support for linux?
Thanks.
1 For each light any affected object is rendered once. (so 10 lights 10 renderings)
2 ressources are normal garbagecollected as for every java program.
3 I cannot tell you why the sdk is instable on linux, maybee @normen can, otherwise you could use any ide out there(but will of course not have the features of the sdk)
Ok thanks, for 1, does like directionalLight drain more FPS than ambient?
Ambient light really isn’t a light at all. I think you can only have one and I believe it’s combined with one of the other passes. So, no… but without some other light an ambient light doesn’t do anything.
…and if you don’t use real lighting (ie: just an ambient light) then you might as well be using the unshaded material anyway.
i’m not working on linux currently but did it for a while a agree with you about dev productivity but it’s a point of view and not the subject.
quickly 3 things i guess you can check :
- your video driver (do you use standard driver available in a stable repository or the latest available in an unstable repo ? I guess on Arch you need to compile lot of things, maybe look at the compile option regarding your system… is your fps ok on an opengl application outside the Jme3 SDK ?)
- openGL option of the Jme3 SDK are available in “ToolsOptions at OpenGL tab”, maybe you can try with these options
- Your JDK : do you use OpenJDK or the Official one suplied by Oracle ? What is your jdk version ?
Hope this will help ++
@javagame said:3: why does the SDK crash every five minutes on linux? I dualboot Arch & windows, I hate to use windows for development because its slow, everything crashes all the time & I just don't like the desktop environment, I find gnome3 (a linux environment) to be much more efficient for development. I'm being forced to use windows more & more because almost everytime I open the material editor, occasionally when I open the SceneComposer or when I create a new terrain the SDK just closes. My buddy uses Ubuntu & he gets even more crashes (from what I've heard). Also, when I can get the material editor open, I can't change any of the check boxes in additional RenderState, it wrks on windows though. I'm not moaning, just wondering if & when you will get more support for linux?
LWJGL historically hasn't been super happy on Linux.. We've been looking into instability issues both on our end and keeping track of what LWJGL figures out. @Momoko_Fan has put in many frustrating hours tracking through the issues, he'd be best equipped to explain exactly what's going on.
Have you got any IDE logs from when it crashes? They might help people identify what is going on…
@soaring Arch uses a package manager called ‘pacman’, all packages are on a rolling release, so anything unstable is usually put up right way. Also, isn’t the openJDK project officially supported by Oracle (I’m using OpenJDK 7)?, thanks for the tips.
@sbook I know you guys probably have quite alot to do, I’m sure me and most other users don’t mind using windows or other IDEs most of the time. At least now I know what’s going on.
@zarch What are IDE logs and how do I get them 0.0
It will be on your hard drive somewhere as well although you might need to dig around a bit to find it, I doubt JME3 has modified the location although I’ve not looked myself. Essentially it’s Netbean’s console output. With any luck it will show an exception or stack trace or similar from whatever is causing the crash.