Alright people, I still couldn't solve the problem. As I will be busy these days, i have to put it aside for a while. But i do come up with a workaround to cover up the problem (somehow, with my fuzzy head ). Actually sliding occurs even if the recursion is 1, but the strength is very weak (i.e. after a few units of sliding, the cam will bump out of walls). But I cannot make it too high because my camera will keep shaking when the cam gets nearer to the char. I might be wrong because my code actually comes from the car example, whereby some camera smoothing is applied. Alas, i think the problem only comes when the camera slided to a point where it gets too near to the character, so I added a threshold of my own ==> if the actual distance between cam and char after collision is less than the threshold, the camera will stop moving, so i can prevent my camera from both jumping out of my wall, and from shaking when getting too near. It works without problems, but the outcome and the effect is quite different from that in karga LOL. I will accept my way as a workaround atm, until I have more time.

But to be honest - If you have never tried the collision system in jME, you will never realize how easy you can implement collision in jPCT. Hence appreciate whatever you do in jPCT.

LOL, take your time mister . Everyone is absolutely patient.

Nope, it didn't work. But I think it's my problem understanding the issue (Mathematically ).

Take a look at this graph:


When the cam is orbiting and finally meet a wall, it will slide towards the target. This one is already working. But the problem is when the cam continue sliding (until it gets very close to the char), it suddenly goes to the location where my red arrow is pointing to (i.e. return to the original orbiting track).

Actually the problem is not with the collision algorithm, but with the parameters. Firstly, in this case you cannot simple use a camera constant to define the direction because the direction is always not around an axis. Secondly, I dunno how to determine the speed in this case.

Alright, solved, the board is simply not thick enough lol.

Every time i export my object/save my scene to .max or .3ds, if the name of the object is longer than 8 characters, it will be truncated. Anyone knows whether this limitation is reinforced by the tool (i.e. 3d max) or by the document standard?

Alright, i still haven't solved the problem though, but i think i got some more understanding about the issue. My camera is not first person!!! . It is an orbiting camera, so when the camera orbits the object, the velocity is not around a simple axis. Then does it mean that i should use this version:

public boolean checkCameraCollisionEllipsoid(SimpleVector direction, SimpleVector ellipsoid, float moveSpeed, int recursionDepth)

Unfortunately im not specialized in maths stuff. How do I get the correct "direction" parameter, would it be camPos.calcSub(oldCamPos);

Generally this method works without problem. But sometimes if my camera moves too fast, it will still bump out of walls/ceilings.

I'm sure this can be solved by changing some of the values in the parameters, so what to adjust?

FYI: Im using this version:

public boolean checkCameraCollisionSpherical(int mode, float radius, float moveSpeed, boolean slideMode)