This probably won't help you much, but I thought I would add my two-cents worth
.
If it seems that one or more of your resources are not getting loaded, I was trying to think of what kind of things might cause problems wherever you load your resources.
If you are loading resources using a file stream directly from a physical directory, be sure to use the "\\" directory divider if the files are local to a Microsoft OS, but "/" if the files are on a Linux OS.
If you are loading resources the other way, with one of the "getResource" methods (which it looks like that is what you are probably doing here), use "/" for sub-directories and print out a message when an exception gets caught. For example:
try
{
java.io.InputStream myFile = getClass().getClassLoader().getResourceAsStream( "models/box.jpg" );
}
catch( IOException e )
{
System.out.println( "Error loading resource file models/box.jpg" );
}
The only other advice I can think of is to temporarily make your applet as verbose as possible. Print out a message for each line, and display the contents of varriables when possible. Sometimes it seems like the simplest problems are the hardest ones to track down, and printing out a ton of messages often helps narrow down your focus.