Standalone Usage

This covers SquirrelJME Standalone, for general usage see Usage.

SquirrelJME's Standalone JAR requires at least a Java SE 8 virtual machine. For most systems, it may be downloaded from the following locations:

Generally SquirrelJME will work best with at least a Java 8 virtual machine.

The JAR file squirreljme-standalone.jar may be run by running the following:

When run, it should start the launcher and provide a list of available programs.

Command Line Usage

Any reference to squirreljme should be interpreted as java -jar squirreljme-standalone.jar in the usage documentation.

Common Issues

STANDALONE ISSUE?: Try running with either or both of the options -Xclutter:debug and/or -Xemulator:hosted.

UI Freezing/Broken on macOS?: Try running with the following command java -XstartOnFirstThread -jar squirreljme-standalone.jar, as this forces OpenJDK and derivatives to have the Cocoa event loop on the first thread, which is required for it to work correctly.

Inconsistent Audio Playback on -Xemulator:hosted?: Using the Hosted environment which uses the host Java SE JVM, the virtual machine performs JIT compilation depending on which code is actively being used often. As such when it decides to optimize the audio playback specific code, there will be stutters and inconsistencies.

java.lang.NoClassDefFoundError on -Xemulator:hosted?: Using the Hosted environment which uses the host Java SE JVM, the JVM itself is very likely to be very up-to-date especially if you have Java 17 or greater installed. Backwards compatibility with versions of Java 8 and earlier are not guaranteed. It is recommended to switch to SpringCoat (-Xemulator:springcoat) or NanoCoat (-Xemulator:nanocoat) to use any software which relies on older behavior.