Probably the latest. Already late today so I'll check on it and prepare a test code tomorrow. Thank you so far and good night 

World.setcamerato (if this answers the question?)
Btw, using ES 2.0 if this is relevant.

This helps somewhat. I see it in one scene, but not in the next.
Do I have to do anything with the overlay when I switch cameras?

Egon, can you make a wild guess what could be wrong if an overlay is not visible? It should be rendered on world.renderscene, right?

Debug code:

if (arrow==null) arrow = new Overlay(man.world, fb, "arrow");
arrow.setNewCoordinates(50, 50, 200, 200);
arrow.setVisibility(true);


Still, no overlay

All I'm saying is that the least act of gratitude the users of the engine should show is letting the developer decide the order in which he adds stuff. We can make suggestions of course, but your comments sounded quite demanding to me. No offense meant.

People who demand features from a free engine that a solo guy is developing in his spare time, but are too lazy to even come to the forum to ask about these features, are the worst kind   

What do you need it for? Just for screenshots? There are easier ways for that
Most devices have a certain button combination or a gesture to capture the screen (google it), or if you are using Eclipse, switch to DDMS view, there you have a screen capture button.

You can't tell what memory a texture will take by looking at the file, which is compressed. Instead, the texture will take height*width*4 (if you have alpha) bytes.
So, make sure to use smaller textures.

Did you change the controls?

Put it all in the asset folder and make sure that you don't have any characters in the filename that Android doesn't like, which are quite a lot.

Thanks Egon. I only have width>=height, and I tested it on devices with a nice bandwidth of the big GPUs brands. It always worked, with the exception of this weird case on the top. So I guess it should be pretty safe. The game won't run on old or exotic devices anyway.

The black textures are actually non-square. Will try if changing that helps.
But, I am using the latest version and call setMipmap right after loading, so it's still a mystery anyway...

By the way, do you know of any way to detect if a device cannot display non-square, so I can add square ones as a fallback? I'd prefer not to make all textures square per default, e.g. with planet textures that would be very impractical.
And can the blackness also happen to textures that are only used for blitting?

I did setMipmap(true) after loading a texture. Strangely, it turned out black then. I don't get this - isn't mipmapping turned on by default anyway?

As this seems to be a relatively common issue, and it's pretty hard to figure out for a beginner, I have added a page to the Wiki under "Advanced topics" (did not want to add it to performance tips as those all seem to be for Android in general, not JPCTAE specific)
Hope that's ok!

The legs seem to be a little short for the rest of the body, but then, there are real people just like that
Looks good!