Every class that extends jme3.app.SimpleApplication has properties that can be configured by customizing a com.jme3.system.AppSettings object.

Configure application settings in main(), before you call app.start() on the application object. If you change display settings during runtime, for example in simpleInitApp(), you must call app.restart() to make them take effect.

Note: Other runtime settings are covered in SimpleApplication.

Code Samples

Specify settings for a game (here called MyGame, or whatever you called your SimpleApplication instance) in the main() method before the game starts:

public static void main(String[] args) {
  AppSettings settings = new AppSettings(true);
  // ... other properties, see below
  MyGame app = new MyGame();

Set the boolean in the AppSettings contructor to true if you want to keep the default settings for values that you do not specify. Set this parameter to false if you want the application to load user settings from previous launches. In either case you can still customize individual settings.

The settings are saved based on the title of your game (default = “jMonkey Engine 3.x-stable”). This means that if you have not changed the default title, then remove a setting method call, your settings changes will remain in effect for all projects using the default title. To prevent this, set the title for your game or remember to change the settings back to their default and run the project again.

This example toggles the settings to fullscreen while the game is already running. Then it restarts the game context (not the whole game) which applies the changed settings.

public void toggleToFullscreen() {
  GraphicsDevice device = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice();
  DisplayMode[] modes = device.getDisplayModes();
  int i=0; // note: there are usually several, let's pick the first
  app.restart(); // restart the context to apply changes

To view your current settings, use the System class.

AppSettings settings = new AppSettings(true);


Table A: Video
Settings PropertyDescriptionDefault


Switch Video Renderer to OpenGL 1.1, OpenGL 2, or OpenGL 3.3. If your graphic card does not support all OpenGL2 features (UnsupportedOperationException: GLSL and OpenGL2 is required for the LWJGL renderer), then you can force your SimpleApplication to use OpenGL1 compatibility. (Then you still can’t use special OpenGL2 features, but at least the error goes away and you can continue with the rest.)

OpenGL 2


Set the color depth.
1 bpp = black and white, 2 bpp = gray,
4 bpp = 16 colors, 8 bpp = 256 colors, 24 or 32 bpp = “truecolor”.



How often per second the engine should try to refresh the frame. For the release, usually 60 fps. Can be lower (30) if you need to free up the CPU for other applications. No use setting it to a higher value than the screen frequency! If the framerate goes below 30 fps, viewers start to notice choppiness or flickering.

-1 (unlimited)


Set this to true to make the game window fill the whole screen; you need to provide a key that calls app.stop() to exit the fullscreen view gracefully (default: escape).
Set this to false to play the game in a normal window of its own.

False (windowed)

setHeight(480), setWidth(640)

Two equivalent ways of setting the display resolution.

640x480 pixels


Set multisampling to 0 to switch antialiasing off (harder edges, faster.)
Set multisampling to 2 or 4 to activate antialising (softer edges, may be slower.)
Depending on your graphic card, you may be able to set multisampling to higher values such as 8, 16, or 32 samples.



Set vertical syncing to true to time the frame buffer to coincide with the refresh frequency of the screen. VSync prevents ugly page tearing artefacts, but is a bit slower; recommened for release build.
Set VSync to false to deactivate vertical syncing (faster, but possible page tearing artifacts); can remain deactivated during development or for slower PCs.

60 fps


Set the number of stencil bits.
This value is only relevant when the stencil buffer is being used. Specify 8 to indicate an 8-bit stencil buffer, specify 0 to disable the stencil buffer.

0 (disabled)


Sets the number of depth bits to use.
The number of depth bits specifies the precision of the depth buffer. To increase precision, specify 32 bits. To decrease precision, specify 16 bits. On some platforms 24 bits might not be supported, in that case, specify 16 bits.
See What Is a Depth Buffer? and Z-buffering for a more in depth explanation.



Enables Gamma Correction.
If you’re starting a new project, use it, period. And don’t allow the player to turn it off.
See Gamma Correction or sRGB pipeline


Table B: Input
Settings PropertyDescriptionDefault


Respond to user input by mouse and keyboard. Can be deactivated for use cases where you only display a 3D scene on the canvas without any interaction.



Activate optional joystick support



Enable or disable mouse emulation for touchscreen-based devices. Setting this to true converts taps on the touchscreen to clicks, and finger swiping gestures over the touchscreen into mouse axis events.



Flips the X or Y (or both) axes for the emulated mouse. Set the first parameter to true to flip the x axis, and the second to flip the y axis.


Table C: Audio
Settings PropertyDescriptionDefault


Switch Audio Renderer. Currently there is only one option.



Enable 3D stereo. This feature requires hardware support from the GPU driver. See Quad Buffering. Currently, your everday user’s hardware does not support this, so you can ignore it for now.


Table D: Branding
Settings PropertyDescriptionDefault

setTitle("My Game")

This string will be visible in the titlebar, unless the window is fullscreen.

“jMonkey Engine 3.x-stable”

setIcons(new BufferedImage[]{
ImageIO.read(new File(" ")), …});

This specifies the little application icon in the titlebar of the application (unused in MacOS?). You should specify the icon in various sizes (256,128,32,16) to look good on various operating systems. Note: This is not the application icon on the desktop.



A custom splashscreen image in the assets/Interface directory which is displayed when the settings dialog is shown.


You can use app.setShowSettings(true); and setSettingsDialogImage("Interface/mysplashscreen.png") to present the user with jme3’s default display settings dialog when starting the game. Use app.setShowSettings(false); to hide the default settings screen. Set this boolean before calling app.start() on the SimpleApplication.

Toggling and Activating Settings

SimpleApplication methodDescription


Activate or deactivate the default settings screen before start()ing the game. If you let users use this screen, you do not need to modify the settings object. Note: Most developers implement their own custom settings screen, but the default one is useful during the alpha stages.


After you have modified the properties on the settings object, you apply it to your application. Note that the settings are not automatically reloaded while the game is running.


Every game calls start() in the beginning to initialize the game and apply the settings. Modify and set your settings before calling start().


Restart()ing a running game restarts the game context and applies the updated settings object. (This does not restart or reinitialize the whole game.)

Saving and Loading Settings

An AppSettings object also supports the following methods to save your settings under a unique key (in this example “com.foo.MyCoolGame3”):

  • Use settings.save("com.foo.MyCoolGame3") to save your settings via standard java.io serialization.

  • Use settings.load("com.foo.MyCoolGame3") to load your settings.

  • Use settings2.copyFrom(settings) to copy a settings object.


Provide the unique name of your jME3 application as the String argument. For example com.foo.MyCoolGame3.

    try { settings.save("com.foo.MyCoolGame3"); }
    catch (BackingStoreException ex) { /** could not save settings */ }
  • On Windows, the preferences are saved under the following registry key:

  • On Linux, the preferences are saved in an XML file under:

  • On Mac OS X, the preferences are saved as XML file under: