I've been a bit lazy with upgrading my LWJGL-installation from 0.7 to 0.8, but i finally did and jPCT works fine with it. Just to let you know in case you want to use 0.8 yourself.

Changes are documented here: http://www.jpct.net/changes.html

In addition, i finally replaced the jPCT-demo from the stoneage with a more current version. To be precise, the new jPCT-demo is simply the fps-demo from the examples-dir of the API-distribution bundled with LWJGL 0.7.

Have fun!

...i've managed to upload an updated version of it. Finally!
The new version uses jPCT 0.95 instead of the ancient 0.79 the old version was using.

I decided to release it today, albeit i haven't managed to include all the things i wanted to. Anyway, there always another version... :wink:

Changes can be found here: http://www.jpct.net/changes.html

In addition, i added a small chapter about optimizations to the manual and a new example is in that shows how to do something first person shooter like with jPCT.

Have fun!

The topic says it all (almost)...the change-log can be found here:

http://www.jpct.net/changes.html

As you can see, this version supports LWJGL 0.7. It comes with a slightly newer version of the LWJGL-DLLs (0.71a) than the last official release of LWJGL does.

Finally, here's a shot showing how the new RGB-scale option for Lights may look like...this is vertex lighting only and as you may have noticed, the colors are looking quite rich though.

Get it here: http://www.lwjgl.org/

Anyway, jPCT won't support it until 0.93 or 0.94. I'll wait some days before starting to port jPCT to 0.7, because quite a lot has changed and i want to see how things go first (well, that and i'm lazy... )

Some minor things like an improved collision detection performance for ray-polygon collisions and some cleanup work. A major addition is the possibility to now build yourself a VertexController to modify vertices of already constructed objects. This is something that wasn't possible in jPCT before. The usage of the VertexController may not be very intuitive, but i'm planning to add a demo of that. For now, look at this source code to see a sample implementation:

public class DemoVertexController extends GenericVertexController {

     int count;

     DemoVertexController() {
       count=0;
     }

     public void apply() {
       SimpleVector[] srcMesh=this.getSourceMesh();
       SimpleVector[] dstMesh=this.getDestinationMesh();

       int size=this.getMeshSize();

       for (int i=0; i<size; i++) {
         float z=srcMesh[i].z;
         float x=0.25f*(srcMesh[i].x+count);
         float sin=(float) Math.sin(x);

         dstMesh[i].z=sin*3f+z;
       }
       count++;
     }
}


Yeah right! The VertexController stuff may sound more complicated than it really is when it comes to implementing one (note that this implementation skips updating the vertex normals, which is not quite correct).

Use your new controller like this:


      IVertexController demoControl=new DemoVertexController();
      Object3D obj=Primitives.getPlane(20,5);
      myWorld.addObject(obj);
      obj.setTexture("texture");
      obj.build();
      obj.getMesh().setVertexController(demoControl, IVertexController.PRESERVE_SOURCE_MESH);


Note that the call to build() has to be placed before the getMesh() to make sure that the normals are calculated. This isn't mentioned in the current docs, so i'm mentioning it here.

The result will be a plane whose vertices are being modified by the VertexController in realtime. Can't show it in motion ATM, so here's a quick and dirty picture of it (not that it's very impressive but it may help to understand what a VertexController is supposed to do):