I have just tested the new scene viewer on my other PC and did not notice any freezes. Looks like I will have to install Ubuntu 10 to resolve all these issues people were having.
It’s good that you asked me to have a look a log. I found interesting thing:
I always open JMP with a default label, which appears when i install JMP.
The label has such execution:
/bin/sh “/home/mifth/jmonkeyplatform/bin/jmonkeyplatform”
And JMP freezes with the screen above.
When i tried to start JMP from console ./jmonkeyplatform - it works and does not freezes. I was so glad!
Then I tried to change label execution to:
/home/mifth/jmonkeyplatform/bin/jmonkeyplatform
And it did not freeze too!! Amazing!
I don’t know why, but possibly something is wrong with linux JMP executable? I mean jmonkeyplatform/bin/./monkeyplatform.
P.S. Log is not accessible on a startup.
Oh my… Somebody linux please investigate this…
Normen, I found another bug with material assignment to mesh in sceneviewer.
1 For example, i did lighting material with reflection. I assigned the material to mesh. Everything is ok.
2 I changed materiial and removed reflection. Then I assign the changed material to the mesh and save the mesh.
3 Then I try to open the mesh again. And I’ve got such a log:
…
…
Keyboard created.
Mouse created.
OGL: Waiting for display to become active…
OGL: Display is active!
OGL: Input has been reinitialized
Loaded material definition: Phong Lighting
All children removed.
All children removed.
Child (Sphere.001-ogremesh) attached to this node (Root Node)
Uniform g_CameraPosition is not declared in shader.
Uniform g_WorldMatrix is not declared in shader.
4 And when I try to move camera in scene viewer, so JMP freezes.
I removed reflection in material at all. But the reflection uniforms are stored…
I dont get it, whats the problem? You changed the shader source? Only the j3m is removed from the assetManager cache before applying the Material. I don’t wanna clear the whole cache on every little occasion so I guess in the future jMP will have to check what shader sources are used and clear these too from the assetManager (or the assetManager knows what j3md and shader sources are loaded by the j3m and clears those too when the j3m is cleared).
Alright guys, the canvas handling in lwjgl has received a major overhaul in the latest lwjgl svn version so I decided to add it to our jme3 svn version. The update is in the update center now so for all people who can update at the moment (the slowness/router problem is being investigated in) can update now and see if jmp and the jme3 canvas behave better (especially on Linux) now.
Cheers,
Normen
1 Like
Thank you for your efforts! I updated today, but I have the same issue with the scene viewer.
Plugins versions:
JMonkeyPlatform Core - Version: 0.12.1.7745.45
JMonkeyPlatform Core JME3 - Version: 0.8.1.7748
JMonkeyPlatform Core Libraries - Version: 0.8.0.7748
My log of Unexpected Exceptions:
1)
org.lwjgl.LWJGLException: X Error - disp: 0x423e0280 serial: 49 error: BadValue (integer parameter out of range for operation) request_code: 1 minor_code: 0
at org.lwjgl.opengl.LinuxDisplay.globalErrorHandler(LinuxDisplay.java:294)
at org.lwjgl.opengl.LinuxDisplay.nCreateWindow(Native Method)
at org.lwjgl.opengl.LinuxDisplay.createWindow(LinuxDisplay.java:447)
at org.lwjgl.opengl.Display.createWindow(Display.java:317)
at org.lwjgl.opengl.Display.create(Display.java:857)
at org.lwjgl.opengl.Display.create(Display.java:805)
[catch] at com.jme3.system.lwjgl.LwjglCanvas.createContext(LwjglCanvas.java:348)
at com.jme3.system.lwjgl.LwjglCanvas.restoreCanvas(LwjglCanvas.java:231)
at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:188)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)
at java.lang.Thread.run(Thread.java:662)
2)
java.lang.IllegalStateException: Keyboard must be created before you can poll the device
at org.lwjgl.input.Keyboard.poll(Keyboard.java:378)
at com.jme3.input.lwjgl.LwjglKeyInput.update(LwjglKeyInput.java:79)
at com.jme3.input.InputManager.update(InputManager.java:826)
at com.jme3.app.Application.update(Application.java:562)
[catch] at com.jme3.gde.core.scene.SceneApplication.update(SceneApplication.java:219)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:144)
at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:199)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)
at java.lang.Thread.run(Thread.java:662)
3)
java.lang.IllegalStateException: Display not created
at org.lwjgl.opengl.Display.update(Display.java:675)
[catch] at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:155)
at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:199)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)
at java.lang.Thread.run(Thread.java:662)
4)
java.lang.IllegalStateException: Display not created
at org.lwjgl.opengl.Display.processMessages(Display.java:632)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:174)
at com.jme3.system.lwjgl.LwjglCanvas.runLoop(LwjglCanvas.java:199)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:218)
[catch] at java.lang.Thread.run(Thread.java:662)
did you update after my post?
yes, just 10 minutes ago.
The issues fixed by the LWJGL team were deadlocks due to using AWT calls outside the EDT, this issue is not related.
1 Like
Thats realy cool!!! When the fixes will be comited to JMP? Thanks!
They have been committed, you tried them.
I updated this morning (7 hours ago) and tried to open JMP. There were the same Unxpected Exceptions. 
Yes, as I said you tried the fix already. @Momoko_Fan was just pointing out that your problem is apparently a different one.
aaa, I get you. Thank you for explanation. If you will need another testing, so I can easily make it. You are welcome. 
Please fix this issue, we, linux users, are sad because we cant use cool features like updated terra monkey!
I have no idea how to fix it honestly.
I can imagine one way would be to simply have the sceneviewer running as a separate window instead of a tab inside jMP
But where is the problem? Lwjgl or JMP-sceneviewer?
I don’t know. It seems like the issue might be in both jME3 canvas and LWJGL.
If you look it up you will see it is a quite common issue in Linux … I expect either jME3 or LWJGL are doing something that X Window System does not like, we just don’t know what.
Thanks for answering.
By the way, Alpha-2 had no such a problem. The problem has appeared from Alpha-3 of JMP.