It's there! It's very similar to the pre-release versions that i've posted in some threads. Anyway, here are the changes:

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

Have fun!

Quote from: "raft"maybe gmail is down for that moment and forum engine doesnt retry it  :?:

Maybe. It's on a shared server and i don't have access to the mailer's logs, so i don't really know.

Quote from: "raft"
btw, sometimes forum engine doesnt notify about replies

Works for me all the time...couldn't possibly be your spam filter or something?

BTW: If you want to modify existing objects' textures on a per polygon base, you can use the PolygonManager which you can obtain from an Object3D by calling getPolygonManager();

You can assign different textures to an Object3D with either the 3DS loader (as you you've already mentioned) or with the addTriangle(...)-method in Object3D. Because you are writing a loader, i assume that you are already using one of those. Simply change to one with a textureID as parameter and you should be fine.

Why don't you open your own thread for your project? Looks cool btw.
Are you using jPCT's ellipsoid collision detection for this? If so, a deadlock should never happen...the ellipsoid collision detection is a collision avoidance algorithm, so it doesn't really care if used on objects which are already intersecting. There is some code (2 lines to be exact) to try to push such entities out of the intersection but due to the nature of the algorithm, this may or may not work. But there should be no real deadlock. The entities should be able to move out of this situation on their own.

In jPCT, the camera is defined by its position and a rotation matrix, not by "look at" and "up" vectors. If you want the camera to "tilt", just do a rotateZ(<float>) on it. This will work even if it's not aligned with the worlds z-axis.

Yes, billboarding has nothing to do with perspective projection. About mixing 2D blitting and 3D graphics, you may have already noticed from reading the other threads about this, that it has some problems....i may be possible in one way or another, but not exactly fun IMHO.
Using billboarded, textured planes for the sprites may result in problems with the software renderer, because you have to set the billboarded objects to transparent (at a high value, for example 6) and the software renderer handles this slightly different for performance reasons. So using OpenGL, the sprites will most likely look fine but using software, the may look a bit too dark. I just wanted to mention this in case you are wondering.

Quote from: "manumoi"Is there a specific reason you choosed to do all your processing on your server? My own approach is to separate processing. Each clients will do collision detection... etc and send periodically its new position to the server... The server will maintain a collection of object position and it will send that collection to clients... It is more or less oriented on a grid topology:  each node/client participates to the processing...I think if the number of clients grow, the performance should not differ that much. So is there something that made you choose to centralize your processing?

Depending on how you are implementing the collision detection, this may cause trouble IMO. Imagine entity A on client a move towards entity B (standing still on a) and entity B on client b moves towards A (standing still on b). Locally, this is no problem. On a, you correct the movement of A to not run into B and on b, you correct B's movement to not run into A. a and b are then sending the result back to the server. But then, A and B may cover the same space.
Have a look:

What exactly do you mean by "align with z-axis"? The camera is aligned with the the z-axis by default. If you want to align it with the z-axis of an (rotated) object, there is an align()-method in Camera. If you want to align it with any vector, you can do something like this:

// Look up
camera.setBack((new SimpleVector(0,-1,0)).getRotationMatrix().invert3x3());

But it's cheaper to do the rotations directly on the camera instead of aligning it afterwards. Or did i get you wrong?

About the message: You are right. I've avoided this until now, because i don't really see it as an error. But i'll add a one-time warning once you are exceeding the limit (to not spam the console with such messages).

The basic idea behind jPCT is to keep things simple, so it should be suitable for beginners. It tries to hide all the "don't care" stuff from the user...something that others don't IMHO.
If it's suitable for you and what you have in mind...i don't know. You can do billboarded objects and you may emulate sprites with that. You can't do parallel projection, it's always perspective. This may or may not work for your project.

Hope this helps.

This usually happens if the awt event dispatch thread bails out for some reason, i.e. it's not the cause of a problem but the consequence. There should be another exception of some kind (for example in an overridden paint() method). Try to log StdErr into a file if you are having problems to spot this on the console (i.e. 2>myfile.txt)

Quote from: "raft"i'm afraid Egon will kick our asses as this is not a swing-awt forum :roll:

No no...feel free to discuss this topic here. I just can't contribute to this thread...all i'm getting when i'm using Swing are grey rectangles... :oops:

Quote from: "rolz"- fixed concurrentModification exception

Are you sure? I've downloaded the new client, but i'm still getting the same exception: Exception in thread "AWT-EventQueue-0" java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
at java.util.AbstractList$Itr.next(Unknown Source)
at aD.a(Unknown Source)
at aD.paint(Unknown Source)
at java.awt.GraphicsCallback$PaintCallback.run(Unknown Source)
at sun.awt.SunGraphicsCallback.runOneComponent(Unknown Source)
at sun.awt.SunGraphicsCallback.runComponents(Unknown Source)
at java.awt.Container.paint(Unknown Source)
at y.paint(Unknown Source)
at y.update(Unknown Source)
at sun.awt.RepaintArea.updateComponent(Unknown Source)
at sun.awt.RepaintArea.paint(Unknown Source)
at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

The client.jar is dated 2005-07-25 11:17. Is that the most current one?

Could be that Config.maxPolysVisible is set to low so that some polygons are being discarded. Try to increase this value (before creating a World) and see if it helps.