Known issues

---

• Please note that no specific problem was found yet on Windows platform, which is quite incredible ;-)

Please let us know when that happens, since it is certainly a matter of time...!

• Program locks on startup and takes 100% CPU, forcing use of a task manager to kill the JVM

This problem occurs systematically under Linux with some Java 5.0 environments : the MIDI initialization from Java fails and the JVM is stuck taking all the CPU.
Then you must issue a $ kill -9 <pid>  to end the Java process.

A: The only workaround is to install another JVM (e.g. Java 1.4.2) and run Super Slime Volley Ball with that version.
You may also disable the MIDI support using the -nomidi toggle in the command line, when running the Super Slime Volley Ball client.

• Things do not happen like said in the Instuctions section, windows are popping up erratically

Some strange behaviour happens sometimes under Linux : the program starts normally, but then windows are badly sized or their positions are messy.
Also some windows that should be there are simply missing, forbidding a correct execution of the game.

A: This was seen on my Mandrakelinux 10.0 system, with Java 1.4.2, and things get better when Java 5.0 is installed. If you are lucky enough to have Super Slime Volley Ball starting with Java 5.0, avoiding the MIDI bug, then everything should be right for you.
Else, try using latest release of Java 1.4 since they might have backported things to make it work.
Anyway, I suspect that Java 1.4 didn't have a good support throughout the different platforms for application that mixed AWT and Swing elements (as Super Slime Volley Ball does).