Spoke to soon
I am having an issue with the textures. They are not tiling correctly. If I use a tile 32*32 the top left I set to 0,0 then to get set the texture from my 256*256. I use 1/256 * 32 0 depth tile which should give me the far edge of the first of my depth texture  tiles ??.
I am getting part of the next tile or some thing is alias ing the edge of the texture when it is displayed.
I think this may be something that I have not done. I have played around with the far edge but it always does the same thing unless it is a solid color and it covers at least 2 extra pixels around the 1st tile texture.
It basically looks like there are extremely thin lines or a shadow on the edge of each polygon.
Not the hypotenuse. Just the edges.
Dave

Yes a different colored texture based on height. It does not have to be so large that was just so that I could visualize the texture tile as it where. this is to show the depth of a channel like a topography. 16 *16 could work.
no problems I think.

Hi I resolved this by adding 3 textures of 0,0, size with different colors really simple and quick for a single texture object.
   tm.addTexture("conered", new Texture(0, 0, red));
      tm.addTexture("conegreen", new Texture(0, 0, green));
      tm.addTexture("coneorange", new Texture(0, 0, orange));

  if (channelDepth - reallocation.y < 1) {
      coneobj.setTexture("conered");

    }
    else if (channelDepth - reallocation.y < 2) {
      coneobj.setTexture("coneorange");

    }
    else {
      if (overlayBitmap != null) {
        coneobj.setTexture("conegreen");

      }
    }




I had this
tm.addTexture("platform", new Texture(0, 0, 0));
TextureInfo coneTex = new TextureInfo(tm.getTextureID("platform"));
    coneTex.add(tm.getTextureID("normals"), TextureInfo.MODE_MODULATE);
    tm.unloadTexture(fb, tm.getTexture("platform"));
    tm.replaceTexture("platform", new Texture(128, 128, red));


or
    tm.unloadTexture(fb, tm.getTexture("platform"));
    tm.replaceTexture("platform", new Texture(128, 128, green));

I just want to do this if possible.

 depthColor = green;
        coneobj.setAdditionalColor(depthColor);

Dave

My panel is a partial window into a huge 3900*2000 map of which each point contains a depth, each tile in the map  that contains  uniuqe data is 348*348 this size is the optimum size. They are placed into a 5*10 grid.
If try to create a panel the same size as the tile the task just takes to long and never seems to return (allocating lots of memory).
So my initial attempt failed so I reduced the panel down until it worked.
Any recommendations gladly considered.
So now I scroll the panel and then refresh it when new data is required. That works quite well.
The x and y are just pointers into my data set.
So when  y is 0 I then write to 2 vertex locations. E.g. top edge. So which other edges require special treatment.
I just need to know where there will be 2 vertices representing one coord so to speak.
For instance my array is 174*174
The first 384 values in the mesh represent the top edge.
So where are they other duplicates. Left edge or right edge both ?
Does the last line of their panel also require 2 vertices. I have not observed this.
Just my panel data appears scewed.
Thanks for your help.
One other question is it possible to change the color of each vertex simply?

Hi Thanks for the reply and example.
It still did not work as expected but it did give me a good idea of where I was going wrong. Here is my final working code for any one else who has this issue.

     m_channel = Primitives.getPlane(PLANESIZE, 10);
      m_channel.setAdditionalColor(new RGBColor(0, 0, 0));
      m_channel.rotateX(PI / 2);
      // m_channel.rotateMesh();
      // m_channel.clearRotation();
      m_channel.setSpecularLighting(true);
      TextureInfo ti = new TextureInfo(TextureManager.getInstance().getTextureID("channel"));
      m_channel.setTexture(ti);
      reTexture(m_channel, "channel", 5f);
      m_channel.disableVertexSharing();
      // enabling lazy transforms means do not transform this object in the future. Ok for the water
      // but nothing else
      // m_channel.forceGeometryIndices(true);
      m_channel.setCulling(true);
      m_channelController = new ChannelController();

      // Calc Normals must be done now otherwise the plane becomes a black texture.
      m_channel.calcNormals();

      // make sure to attach the controller before calling build() or otherwise, the object will be
      // compiled to static geometry and won't reflect any changes to the mesh.
      m_channel.getMesh().setVertexController(m_channelController, false);
      m_channel.build();
      // Deform the channel do this as a background task
      UpdateMapTask task = new UpdateMapTask(bathyfiles, m_channel, m_shipGpsLat, m_shipGpsLong);
      task.execute();
       m_world.addObject(m_channel);

and in the async background task
@Override
  protected String doInBackground(Void... params) {
    List<Tile> tiles = bathyFiles.getTileset(shipgpslong, shipgpslat);
    Logger.log(m_tag + " updating map to new coords " + shipgpslat + " lat " + shipgpslong
        + " long");
    bathyFiles.buildMapWindow(tiles, shipgpslong, shipgpslat);
    channel.getMesh().applyVertexController();
    channel.touch();
    return null;
  }So the issue was no normals had been calculated when I ported from your example because I had textures.
The root cause was I was doing this more than once.
 channelMesh.setVertexController(controller, false);
which I think was breaking (creating a new link) to the mesh.
Dave

I have updated the code snippet above to show the changes you recommend. It now displays the first planemesh as it should.
However when I try to update the mesh nothing happens it is as if it is compiled to a static geometry. As you suggested in your first response.
If I do not apply the mesh in the first updatetask the mesh stays flat as it should. then the next time I call the updatetask with a flag to update the mesh. it still stays flat.
putting the build just before I add the plane to the world does not display the plane.
Dave


 

I am having an issue applying a vertex controller to a plane. Once I have added it to the world.
I update the plane in an async task it works fine the first time (this is done  just before i add the object to the world), but the second time even though it succeeds there is no visible change to my plane.
Is there anything else I need to do to get the new mesh to appear  instead of the old mesh.
I tried touch but that did nothing.
My next test is to apply a second vertex before I add the object to the world.
Any thoughts or explanation on why the second apply does not work .lazy transformations are off.
Dave