Thanks for the contribution. setExternalId() was actually meant to be used in such edge cases. You are right about the memory consumption. It's almost doubled for a normal configuration. You can work against this by using either the Virtualizer (http://www.jpct.net/jpct-ae/doc/com/threed/jpct/Virtualizer.html) or by setting keepPixelData on a Texture to false. Both methods will still peak out at double the memory usage at reload time.

There are several reasons for keeping the pixels. One is, that the upload has to happen again on a context change. Context changes happen far less now than on older Android versions but they still might. In case they do, you have to make sure to upload your texture again yourself or you'll get garbage (or all white). Another reason is that I need the pixel data to calculate the mipmaps myself for some devices. On some older ones, the mipmap calculation is simply broken and doesn't work at all. And the last one is, that the texture isn't aware of the GL rendering context or thread. It's a simple container and it can be created in any thread you like. So you somehow have to buffer the data until the upload is feasible.

Depends on which renderer you are using. For the normal GL renderer, the work is done after World.draw(); The AWTGLRenderer renders in another thread, you can detect if it's done or not by using the IRenderHook.

A had a look at the batch size issue. It's a problem with the way in which batch sizes are calculated. It's only really obvious if the vertex count is a multiple of the batch size. I've fixed it, but I don't think that it requires a new version just for that. It looks strange in the log output, but it's not an actual problem.

No, setOrigin will have no effect in this case. repeatRendering() really just does that: It repeats the rendering. Any object manipulations outside of the shaders aren't possible at this stage.

I've never really used the repeatRendering()-solution myself, but I think that it should work this way. A shader can be applied to Object3Ds in multiple Worlds. That shouldn't be a problem.

Well, regarding wireframe on jPCT-AE, that how it is, I'm afraid. See, for example, here: http://www.jpct.net/forum2/index.php?topic=3562.0

addTriangle tries to find matching points in the model to reuse those, but if there are none and the triangle is basically "floating", then it will just create three new points. Also order doesn't matter. I don't see how it can be responsible for stray lines.