Ok that will probably work.  I will give it a go when I get back from holidays

Is it possible to make a ground plane wrap back on itself. My plane is large but not large enough to hold all of my  map at once. So I have to re build my vertex map when I move over 700 m  to display the current modified plane.
It would be ideal if the right edge connected to the left edge like a cylinder and the bottom connected to the top.
So I would only need to update areas beyond the clipping range in the direction I am traveling. This is an old method to reduce the amount of processing needed to update a map/plane.
Eg if I am moving up the map I would update y max line then y max -1 then -2
Where the map is x*y .
If going right update xmin then xmin+1
For num vertical lines
if y goes thru 0 y =ymax
If x >xmax x=0
So we just update the Poly's in the direction of travel.
Other techniques???

my ouya is on version 4.1.2 so that one looks better.
I still see a slight jerk in my propeller motion. I need a better way of animating the propeller smoothly that does not get any timing glitches.
I am not used to not having a sync to frame refresh interrupt to do all my animations.  Still learning learning the java techniques.
Dave

This device is no longer waiting for the request it is going flat out since the 4.4.2 update I think.
public class AnimationTask extends TimerTask {
    public void run() {
      VesselRenderer.animate = true;
      timer.schedule(new AnimationTask(), 40);
      VesselView.openGLView.requestRender();
    }
  }

here is the log just with the collision check that causes the pause the world.
12-18 08:27:04.654: I/jPCT-AE(29576): 27fps
12-18 08:27:05.664: I/jPCT-AE(29576): 33fps
12-18 08:27:06.684: I/jPCT-AE(29576): 37fps
12-18 08:27:07.704: I/jPCT-AE(29576): 37fps
12-18 08:27:08.714: I/jPCT-AE(29576): 26fps
12-18 08:27:09.734: I/jPCT-AE(29576): 27fps
12-18 08:27:10.734: I/jPCT-AE(29576): 36fps
12-18 08:27:11.744: I/jPCT-AE(29576): 38fps
12-18 08:27:12.754: I/jPCT-AE(29576): 38fps
12-18 08:27:13.774: I/jPCT-AE(29576): 37fps
12-18 08:27:14.774: I/jPCT-AE(29576): 37fps
12-18 08:27:15.784: I/jPCT-AE(29576): 38fps
12-18 08:27:16.804: I/jPCT-AE(29576): 38fps
12-18 08:27:17.814: I/jPCT-AE(29576): 38fps
12-18 08:27:18.924: D/dalvikvm(29576): GC_FOR_ALLOC freed 8445K, 13% free 73872K/84676K, paused 143ms, total 143ms
12-18 08:27:18.934: I/jPCT-AE(29576): 37fps
12-18 08:27:19.944: I/jPCT-AE(29576): 38fps
12-18 08:27:20.974: I/jPCT-AE(29576): 38fps
12-18 08:27:21.994: I/jPCT-AE(29576): 36fps
12-18 08:27:22.994: I/jPCT-AE(29576): 38fps
12-18 08:27:24.024: I/jPCT-AE(29576): 38fps
12-18 08:27:25.034: I/jPCT-AE(29576): 35fps
12-18 08:27:26.034: I/jPCT-AE(29576): 25fps
12-18 08:27:27.034: I/jPCT-AE(29576): 26fps
12-18 08:27:28.044: I/jPCT-AE(29576): 28fps
12-18 08:27:29.044: I/jPCT-AE(29576): 25fps
12-18 08:27:30.054: I/jPCT-AE(29576): 31fps
12-18 08:27:31.054: I/jPCT-AE(29576): 27fps
12-18 08:27:32.064: I/jPCT-AE(29576): 25fps
12-18 08:27:33.074: I/jPCT-AE(29576): 36fps
12-18 08:27:34.094: I/jPCT-AE(29576): 38fps
12-18 08:27:35.114: I/jPCT-AE(29576): 32fps
12-18 08:27:36.114: I/jPCT-AE(29576): 32fps
12-18 08:27:37.134: I/jPCT-AE(29576): 27fps
12-18 08:27:38.134: I/jPCT-AE(29576): 35fps
12-18 08:27:39.174: I/jPCT-AE(29576): 30fps
12-18 08:27:40.174: I/jPCT-AE(29576): 32fps
12-18 08:27:41.194: I/jPCT-AE(29576): 38fps
12-18 08:27:41.564: D/dalvikvm(29576): GC_FOR_ALLOC freed 8200K, 13% free 73864K/84676K, paused 145ms, total 145ms
12-18 08:27:42.214: I/jPCT-AE(29576): 33fps
12-18 08:27:43.254: I/jPCT-AE(29576): 32fps
12-18 08:27:44.264: I/jPCT-AE(29576): 29fps
12-18 08:27:45.264: I/jPCT-AE(29576): 30fps
12-18 08:27:46.264: I/jPCT-AE(29576): 29fps
12-18 08:27:47.274: I/jPCT-AE(29576): 26fps
12-18 08:27:48.274: I/jPCT-AE(29576): 31fps
12-18 08:27:49.294: I/jPCT-AE(29576): 33fps
12-18 08:27:50.294: I/jPCT-AE(29576): 38fps
12-18 08:27:51.304: I/jPCT-AE(29576): 37fps
12-18 08:27:52.324: I/jPCT-AE(29576): 38fps
12-18 08:27:53.334: I/jPCT-AE(29576): 38fps
12-18 08:27:54.354: I/jPCT-AE(29576): 38fps
12-18 08:27:55.364: I/jPCT-AE(29576): 38fps
12-18 08:27:56.374: I/jPCT-AE(29576): 38fps
12-18 08:27:57.394: I/jPCT-AE(29576): 38fps
12-18 08:27:58.404: I/jPCT-AE(29576): 38fps
12-18 08:27:59.424: I/jPCT-AE(29576): 38fps
12-18 08:28:00.434: I/jPCT-AE(29576): 38fps
12-18 08:28:01.444: I/jPCT-AE(29576): 38fps
12-18 08:28:02.374: D/dalvikvm(29576): GC_FOR_ALLOC freed 8191K, 13% free 73865K/84676K, paused 145ms, total 145ms
12-18 08:28:02.454: I/jPCT-AE(29576): 32fps
12-18 08:28:03.454: I/jPCT-AE(29576): 26fps
12-18 08:28:04.464: I/jPCT-AE(29576): 27fps
12-18 08:28:05.474: I/jPCT-AE(29576): 35fps
12-18 08:28:06.504: I/jPCT-AE(29576): 38fps
12-18 08:28:07.514: I/jPCT-AE(29576): 34fps
12-18 08:28:08.524: I/jPCT-AE(29576): 26fps
12-18 08:28:09.534: I/jPCT-AE(29576): 38fps
12-18 08:28:10.564: I/jPCT-AE(29576): 26fps
12-18 08:28:11.574: I/jPCT-AE(29576): 25fps

Version 4.4.2 nexus 7 and an ouya cube

No collision listner
Recursion set to 1
I am sort of cheating with the collision detection I have rectangle object as a child of my ship. I also have cylinder object as a child of the ship I move the rectangle in the opposite angles to the ship which gives me an easy way to detect the lowest depth of the ship at any point on the rectangle, when I check for a collision by moving my cylinder around the ship hull. As the ship could be in any rotation the cylinder must also stay in the correct rotation.
It works fantastic for a few lines of code.

Is there any other way to create a lets call it a text character layer over the 3d view. When I designed an Arcade Board in an Asic I created an 8*8 character map that was the first layer ( hi score points player level info etc) then 2 * 16*16 background layers. I just pointed the index (texture pointer) in the map to the correct character to display.
So if you like a plane with a custom character texture of say 64 characters . The same as I have done for my depth plane. but with alphanumeric's rather than textures. It would have to support transparency.
Before the days of 3D rendering chips. :-)

This would resolve all the memory re use issues in my case and it would be incredibly quick and would not require any bitmap and canvas draw rubbish.

Dave

 

I am using overlays to place some text on the 3d view .if I do not apply the effect GC is firing about 1 time in 25 seconds. I normally call apply 1 time per second. And GC is firing almost every second causing a pause of 100 ms which even pauses my async tasks as well.
I am running at 25 fps with plenty of spare CPU. It frees around 8000k in 100ms.
Any ideas how to stop the memory being allocated and deallocated.
Dave