For some odd reason for me the jMP seems to be very laggy and crashes often. I've tried two separate computers with two separate downloads of the jMP, and have the same result. I have tried undocking and exiting the explorer window and changing around my heap size, updated the platform, and set the jdkhome in the etc/jmonkeyplatform.conf file but it remains lagged at almost everything i do and crashes sometimes even when nothing is happening. At first I assumed it was because it was in alpha but then i heard from others using it and they said they where fine. Can anyone shed some light on this situation?
EDIT
I thought i had somehow fixed the problem by changing the jDK home to jdkhome=C:/Program Files/Java/jdk1.6.0_20 before i used backslashes; however, when i was creating a base class for my current game it froze and then crashed…
I have heard similar reports from another user… General strangeness and JDK path problems before. More input and reports are very welcome.
Backslashes in java properties files should always be double: c:\may path\my file.txt but most tools convert "normal" slash paths to the system native format. Maybe you could try with double-backslashes?
Cheers,
Normen
Well, some more input:
It does not start on Linux (Ubuntu 10.04 x64/KDE and Fedora/GNOME 12 x32, both up to date versions).
Well, it does start, but it's not reponsive for at least 10 minutes… you can hardly close it…
If you want more information, I could test it some other day 
btw… it works GREAT on Windows :-]
@tim8dev really hmmm… it freezes on both my laptop and my desktop and with either the 64 or 32 bit java
my conf file now reads//this was the line i took from my netbeans conf file and it just crashed I will attempt using double backspaces now…
netbeans_jdkhome="C:Program Files (x86)Javajdk1.6.0_20"
jdkhome="C:Program Files (x86)Javajdk1.6.0_20"
My installation appears to be freezing also. In this case, double click on an editor tab to temporarily maximize the window. When I double click again to minimize, the app locks-up. I kill the app, fire it up again, and try to resize the (still) maximized window; app locks. Also (as a data point), if I do not attemp to down-size the editor window, I can still change between editor tabs. Additionally, all other resource windows can be displayed (via their icon).
Hope this data is usefull.
OS: windows xp
stopwalve said:
My installation appears to be freezing also. In this case, double click on an editor tab to temporarily maximize the window. When I double click again to minimize, the app locks-up. I kill the app, fire it up again, and try to resize the (still) maximized window; app locks. Also (as a data point), if I do not attemp to down-size the editor window, I can still change between editor tabs. Additionally, all other resource windows can be displayed (via their icon).
The strange behaviour of the 3d canvas when changing window configuration is a known issue. A workaround is in place that restarts the canvas when that happens. However, some actions mess with the window config so much that the restart fails.
The strange behaviour of the 3d canvas when changing window configuration is a known issue. A workaround is in place that restarts the canvas when that happens. However, some actions mess with the window config so much that the restart fails.
I know this isn't specifically a GDE question, however is there a configuration file I can modify to have the IDE start in a default (non tab maximized) manner?
stopwalve said:
I know this isn't specifically a GDE question, however is there a configuration file I can modify to have the IDE start in a default (non tab maximized) manner?
I dont exactly know what you mean by "non tab maximized" but jMP should save its window configuration on exit and restore it again on startup.
I dont exactly know what you mean by "non tab maximized" but jMP should save its window configuration on exit and restore it again on startup.
Sorry for my lack of clarity. The editor widow(s) are begin restored as you stated. However, that's the issue. The IDE was closed down (killed) with the editor windows maximized. I cannot restore them to their orginal (non-maximized) size. If I try to do so (by double clicking the window tab), the IDE locks. My question is, is there a way to modify the saved window configuration prior to startup?
stopwalve said:
Sorry for my lack of clarity. The editor widow(s) are begin restored as you stated. However, that's the issue. The IDE was closed down (killed) with the editor windows maximized. I cannot restore them to their orginal (non-maximized) size. If I try to do so (by double clicking the window tab), the IDE locks. My question is, is there a way to modify the saved window configuration prior to startup?
I dont remember exactly right now but I think theres an option for that in the settings of jMP.
When you close jMP you currently have to make sure that the SceneViewer is the topmost component. If you dont the SceneViewer will not start up correctly on the next start, see this issue for details.
Cheers,
Normen
Many thanks.
I am not completely sure but I seem to have fixed the issue by deleting all previous versions of java on my laptop and desktop and though i first reinstalled the 64 bit versions of the jdk and jre it only seemed to work when i installed the 32 bit versions first of the jre then of the jdk. It then automatically started without me having to set the JDK home…it should also be noted that the downloaded standalone version reads as 32 bit in the taskManager. I am still not sure if this fixed the problem however the platform hasn't crashed or frozen for me since the night before…
Cheers