INFO: Selected display mode: 800 x 600 x 0 @0Hz
Jan 10, 2012 2:11:35 AM com.jme3.app.Application handleError
SEVERE: Uncaught exception thrown in Thread[LWJGL Renderer Thread,5,main]
java.lang.UnsatisfiedLinkError: org.lwjgl.opengl.WindowsDisplay.nSetTitle(JJ)V
at org.lwjgl.opengl.WindowsDisplay.nSetTitle(Native Method)
at org.lwjgl.opengl.WindowsDisplay.setTitle(WindowsDisplay.java:442)
at org.lwjgl.opengl.Display.setTitle(Display.java:567)
at org.lwjgl.opengl.Display.createWindow(Display.java:312)
at org.lwjgl.opengl.Display.create(Display.java:873)
at org.lwjgl.opengl.Display.create(Display.java:782)
at com.jme3.system.lwjgl.LwjglDisplay.createContext(LwjglDisplay.java:133)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.initInThread(LwjglAbstractDisplay.java:113)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:205)
at java.lang.Thread.run(Thread.java:619)
It is actually more than half the time–and once the error shows up… it takes a restart of JME to (sometimes) fix the issue for a bit.
I keep a version of alpha 4 installed as well, to check against and continue non-render-dependent portions of the app I am working on. I have never seen this before beta… and can’t repro it in alpha 4. If that helps at all.
Eh… while I’m at it. I am also seeing this on the headless server at run time. And have seem it in windowed apps as well… when not getting the above error.
java.lang.ClassNotFoundException: com.jme3.scene.plugins.blender.BlenderModelLoader
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at com.jme3.asset.DesktopAssetManager.registerLoader(DesktopAssetManager.java:135)
at com.jme3.asset.AssetConfig.loadText(AssetConfig.java:74)
at com.jme3.asset.DesktopAssetManager.(DesktopAssetManager.java:88)
at com.jme3.system.JmeDesktopSystem.newAssetManager(JmeDesktopSystem.java:56)
at com.jme3.system.JmeSystem.newAssetManager(JmeSystem.java:87)
at com.jme3.app.Application.initAssetManager(Application.java:162)
at com.jme3.app.Application.initialize(Application.java:490)
at com.jme3.app.SimpleApplication.initialize(SimpleApplication.java:204)
at com.jme3.system.NullContext.initInThread(NullContext.java:85)
at com.jme3.system.NullContext.run(NullContext.java:128)
at java.lang.Thread.run(Thread.java:619)
Oh, you are using the nightly version? Thats really not recommended for the beta, we keep the stable version up to date with merges from trunk.
I did update to the last nightly, because of an issue with ATI Radeon cards and the version of the Lighting frag/vert file that is part of beta which made it impossible to use beta on my machine. However, both of these error were happening before I updated. I realize that I’ll probably have to wait until the next stable version to be released before using beta, but, thought I would report these two errors anyways.
@t0neg0d said:
Eh... while I'm at it. I am also seeing this on the headless server at run time. And have seem it in windowed apps as well... when not getting the above error.
java.lang.ClassNotFoundException: com.jme3.scene.plugins.blender.BlenderModelLoader
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at com.jme3.asset.DesktopAssetManager.registerLoader(DesktopAssetManager.java:135)
at com.jme3.asset.AssetConfig.loadText(AssetConfig.java:74)
at com.jme3.asset.DesktopAssetManager.(DesktopAssetManager.java:88)
at com.jme3.system.JmeDesktopSystem.newAssetManager(JmeDesktopSystem.java:56)
at com.jme3.system.JmeSystem.newAssetManager(JmeSystem.java:87)
at com.jme3.app.Application.initAssetManager(Application.java:162)
at com.jme3.app.Application.initialize(Application.java:490)
at com.jme3.app.SimpleApplication.initialize(SimpleApplication.java:204)
at com.jme3.system.NullContext.initInThread(NullContext.java:85)
at com.jme3.system.NullContext.run(NullContext.java:128)
at java.lang.Thread.run(Thread.java:619)
Usually this is just a WARN log. Did you leave that part out or is this killing your app?
It is not killing the app… and, as far as I can tell it has no effect once the app is running. I’m guessing it must have been a warning then. Sorry if I missed that 
@t0neg0d said:
It is not killing the app... and, as far as I can tell it has no effect once the app is running. I'm guessing it must have been a warning then. Sorry if I missed that :(
That's ok... I believe this was caused by the splitting up of the .jar files. The loader stuff needs to more gracefully deal with these missing plug-ins but I don't know what it takes to fix it... in the mean time, we get this nice warning stack trace freezing the console output in JMP. ;)