You mean a method that takes an array of vertices and creates the triangles from that like you do in your code "by hand"? No, there is no such thing ATM. I may add it, if it's really needed.
Alpha or transparency is only supported on a per Object3D base. That's mainly a tribut to the software rendering.
The order of the vertices that form a triangle counts, because it's used for backface culling. If your order is wrong, the triangle will de visible from the other side.
About the tiled terrain...i would say that it doesn't matter. jPCT will take care of the vertex sharing itself, you don't have to worry about it.

What happened to your server? It seems to be down for some days now... :cry:

I had to delete your last post (and mine too) because somehow my answer appeared in your question

Anyway, what i mean about the framerate is, that you wouldn't ask this question if your framerate would be constant, because it wouldn't be a problem then.

Config.farPlane should do the trick. Unless you are using fog with has to be adjusted separately using the setFogParameters()-method in World. It's also possible that you are scratching the maximum polygon count. In that case, adjust Config.maxPolysVisible. You have to do this before instantiating a World.

Naja, etwa so:

SimpleVector p=...;// Der Punkt, auf den das Objekt gerichtet werden soll
SimpleVector la=p.calcSub(obj.getTransformedCenter());
Matrix m=la.getRotationMatrix();
obj.setRotationMatrix(m);

Habe ich jetzt aber nicht getestet...

Quote from: "EgonOlsen"

.

I think that somthing is worng with the code of the engine

Very very unlikely. jPCT takes whatever name you give it to load the file and that's all it does. If anything goes wrong with loading your files, it's most likely your own fault.

It Should work, but it doesnt, its okay if I send you all the folder with all the files so you can check it please!!!!!!  

You may do that if it's not too large. I'm on a modem connection right now.

The collision detection methods implemented on the engine clases should be more intuitives to use, and should be possible to get information from them.

You can get all the information you want by implementing the CollisionListener interface and attaching your CollisionListener to the objects in question.
Furthermore, don't judge collision detection on the ray-polygon-methods you are currently using...they are oooolllldddd. The spherical and elliposoid methods will give you a corrected SimpleVector that you can apply to you moving entity directly to avoid a collision.