I had this code with version 6.31.4 comm for the ball and the physics was very good and realistic, including collision against models, maps and blocks (geometry).
Code:

---

PHENT_SETTYPE(MY,PH_RIGID,PH_sphere);
PHENT_SETMASS(MY,0.2,PH_SPHERE);
PHENT_SETFRICTION(MY,75);
PHENT_SETELASTICITY(MY,75,25);
PHENT_SETDAMPING(MY,50,75);
PH_SETGRAVITY(VECTOR(0,0,-386));  

---

However, after the update 6.40.5, even recompiling the maps and the whole level, now the physics is very unstable, the friction and roation of the ball its not normal, seems to glide on the ground (blocks and sprites).
Sometimes the ball bounces against models, maps and blocks, and sometimes (almost all the time), the ball stays close to the model for some time, but rotating on the collision point.
It seems to have a delay on the collision response. Please, how can i solve this problem (diferent solution than downgrade the engine)?

Maybe try something like setting this for your ball;

Code:

---

ph_setcontacts(vector(80000, 0,0), 0,0,0);

---

It helped me getting rid of some weird behavior,

Cheers

I already had tried so many combinations with ph_setcontacts and ph_setcorrections, i cant make it work in 6.40.5 version.
Unfortanly i have to downgrade to 6.31.4 version

Programming a ball does not require adjustments with ph_setcontacts. The default settings will do. The programming section of the 6.40 manual contains a small physics ball example - you can just use it as a template.

Could these problems be framerate related jcl?

By the way is it better to set my.polygon = on; or doesn't this have any influence?

Cheers

Yes, adding a force instead of a velocity, and using too small objects will indeed produce frame rate dependent behavior of physics. The fps_max problem mentioned by Ullillilia could also have played a role.

my.polygon has no influence on physics, it's for c_trace and c_move only.

Thanks for the answers, okey then I will remove my.polygon again heheheh,

Cheers