On Windows and Linux make sure you have the latest driver installed. Make sure its the one supplied by the card manufacturer and not just the OS-default one. On OSX, make sure you have the latest update for your MacOS.
On some Linux and Windows systems, the SDK might perform unstable and quit with native VM crashes or “x” errors. There are a few things one can try to remedy those issues.
First of all theres the new “OpenGL” settings page in the SDK global settings where you can enable the “Heavyweight Canvas”, which solved some issues for some people. The settings panel can be found under
on Windows and Linux and in the main menu (or by pressing Apple-Comma) for MacOSX.
If you cannot start the SDK, edit the file
config/Preferences/com/jme3/gde/core.properties in the SDK settings folder (see above). If it doesn’t exist, create the file including all folders. Add the line
use_lwjgl_canvas=true. To try OpenGL1 compatibility mode (works for both canvas settings) add
The OS-built-in look and feel might cause issues, you can change the LAF by using the appropriate command line switch (or add it to the [app folder]/etc/jmonkeyplatform.conf file, without the “- -” prefix).
If you have problems updating the SDK, try deleting all files from
[settings folder]/update/download depending on your system (see below for the settings folder location).
If you are on Linux, check if the user you run the SDK with has access to the files in
jmonkeyplatform/jdk/bin and that they are executable.
If the SDK starts to become sluggish and / or slow or you get unexpected freezes of the application, you can try deleting the cache folder at var/cache in the settings folder (see below for the location of the settings folder). Do this while the SDK is not running, then restart the SDK.
To completely remove and/or reinstall the SDK it is vital that the settings folder is deleted too. The location can be seen through the “about” menu and is as following for the different OS's:
To see or post the error output of the SDK in the forum, you can find the log of the application in the settings folder above too, the file is called
When an exception happens in the SDK, a small warning sign appears in the lower right corner of the main window. Double-click it to open a window that allows you to see the exception stack trace. When posting about issues in the forum, always post the stack trace along with a description of what happens and how it can be reproduced.
You can install another JDK for use with the jMonkey SDK. You then have to specify the location manually.
Go to your jMonkeyEngine SDK installation directory.
Mac users right-click jMonkeyApplication.app (which actually is a directory) in the Finder and select “Show package contents”.
Navigate to the
Mac users navigate to
Open the file
jmonkeyplatform.confin a text editor.
Change the following line and enter the path to the JDK:
If you’re behind a proxy or special network settings, try :
Disable your network connection.
Launch jme sdk (may wait 30s/1min for timeout).
Setup “manual proxy settings” (for some reason the “Use System Proxy Settings” option doesn’t work on some Linux distributions)
Discussion of the problem.