When the program is already running, each animation cycle gets progressively faster. It's probably not noticeable on the OpenGL renderer only because the hardware rendering already starts fast. Is there no way around this apart from delaying the execution, then?

I'm not sure what you mean be "animations" in this context. There's nothing that "warms up" especially when using the software renderer. The only thing that I can think of is the VM itself. It might take some time to get up to speed with compiling the bytecode into native, but apart from trying to influence that behaviour with some VM switched, there's no way to change this.

Is that something you can make the software renderer do? Because otherwise jpct goes through several loops of the animations before they're running at full speed.

It's still happening, only now it says, "Please try again. If you come back to this error screen, report the error to an administrator."

Under which circumstance? It can happen, that the provider has some hickups (happened in the past as well), but it shouldn't be a regular problem.

Your shiny message board's search engine isn't working. Keeps returning "database error."

Now all we need is support for a current lwjgl. ; )

Eventhing looks new and shiny now!

Thank you!! You're a lifesaver! I had set the far clipping plane very close and removed some of the objects to "kind of" solve this, but for my purposes is not ideal, I really needed to put more things in scene.

p.s.: Again! Can't forgive myself for not seeing that in the documentation.

There is a setting for max. objects (it's called differently for historic reasons though): https://www.jpct.net/jpct-ae/doc/com/threed/jpct/Config.html#maxPolysVisible