ODE Physics[FTE or DP]

[Max_Salivan]

[Spike]

regarding fte vs dp, fte implements a slightly earlier version of dp's ode api, and thus omits the builtins (the fields+jointtype constants you have documented for dp should all exist in fte and work the same, but the builtins are stubs). just be sure to set sv_mintic and sv_maxtic to the same value or things can spontaneously go flying across the room - ode just needs a fixed tick rate.
fte will apparently try to dynamically link against an 'ode_double.dll' in win32 builds, 'libode1_64.dll' using the win64 build, or 'libode.so.1' on linux. If not found or incompatible, the physics_ode_enable cvar will be force-set-and-locked to 0.
fte provides ode clientside as well, while I've heard reports that dp's ode implementation is buggy if used from csqc. It may have since been fixed.

if you want to do special stuff like ragdoll, you'll need to combine it with the skeletal objects extension, ideally through csqc (note the end of my previous paragraph, sorry).
there is a simpler ragdoll alternative with fte that can give clientside ragdoll via purely ssqc, but I'm too lazy to document it, and its probably buggy anyway. :s

[Max_Salivan]

ahh,thanks,Spike,got it in FTE,just set physics_ode_enable to 1
i have ode_double.dll,but where i can find libode1_64.dll?

i am use only SSQC,but its works good

What should be
sv_mintic and sv_maxtic ?

[Cobalt]

Curious - if you set up a ded server with ODE physics enabled, do connecting clients also need this library on their side to take advantage? Have not ever seen an error preventing a client to connect without the proper library.

[Spike]

mintic and maxtic should be set to the same value, otherwise time differences can result in singularities and thus bounding, jiggling, or sudden explosions (yay!). 0.013 or so is a good choice for about 72fps.

cobalt, if the physics are used only by ssqc then only the server needs the extra ode dependancy.
if you're doing ragdoll and stuff, you're probably best to use ode in csqc instead due to reduced networking costs, and this requires ode libraries clientside.
a client will never be kicked, its just that physics_ode_enable will be readonly and set to 0, and all the ode movetypes won't do anything (same as you get serverside).
I believe DP is basically the same, but ode support in csqc is unsupported in DP (the cvar might be different too).

[Cobalt]

[Spike]

[Cobalt]