[ODE] Collision detection of rapidly moving objects
Gary R. Van Sickle
g.r.vansickle at worldnet.att.net
Wed Aug 28 17:36:01 2002
This is a multi-part message in MIME format.
------=_NextPart_000_0027_01C24ECA.117DE9A0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message
Also, are doesn't the following two functions mean the same?
dBodyAddForce(body, fx, fy, fz) and dBodyAddForceAtPos(body, fx, fy, fz,
0, 0, 0)
Yes, but dBodyAddForce(body, fx, fy, fz) has much less work to do. All it
has to do is a vector addition, while dBodyAddForceAtPos(body, fx, fy, fz,
0, 0, 0) has to do a bunch of matrix math to split the force into a linear
force and a torque component, even though in this case the torque==0.
--
Gary R. Van Sickle
Brewer. Patriot.
------=_NextPart_000_0027_01C24ECA.117DE9A0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D960482107-13082002><FONT face=3DArial size=3D2><SPAN=20
class=3D111145714-14082002></SPAN></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV><SPAN class=3D960482107-13082002><FONT face=3DArial =
size=3D2><SPAN=20
class=3D111145714-14082002></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=3D960482107-13082002><FONT face=3DArial =
size=3D2><SPAN=20
class=3D111145714-14082002>Also, are doesn't the following two =
functions=20
mean the same?</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D960482107-13082002><FONT face=3DArial =
size=3D2><SPAN=20
class=3D111145714-14082002></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=3D960482107-13082002><FONT size=3D+0><SPAN=20
class=3D111145714-14082002><FONT face=3DVerdana>dBodyAddForce(body, =
fx, fy, fz)=20
<FONT face=3DArial color=3D#800080 size=3D2>and</FONT> <SPAN=20
class=3D960482107-13082002><SPAN=20
class=3D111145714-14082002>dBodyAddForceAtPos(body, fx, fy, fz, 0, 0, =
0)=20
</SPAN></SPAN></FONT></SPAN></FONT></SPAN></DIV><SPAN=20
class=3D960482107-13082002><SPAN class=3D111145714-14082002>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D111145714-14082002><SPAN=20
class=3D960482107-13082002><FONT face=3DArial size=3D2><SPAN=20
=
class=3D111145714-14082002></SPAN></FONT></SPAN></SPAN></FONT> </DIV=
></BLOCKQUOTE>
<DIV dir=3Dltr><SPAN class=3D111145714-14082002><SPAN =
class=3D960482107-13082002><FONT=20
face=3DArial size=3D2><SPAN class=3D111145714-14082002><SPAN=20
class=3D471443000-29082002><SPAN class=3D960482107-13082002><FONT =
size=3D+0><SPAN=20
class=3D111145714-14082002><FONT face=3DVerdana>Yes, =
but dBodyAddForce(body,=20
fx, fy, fz) has much less work to do. All it has to do is a vector =
addition, while <SPAN class=3D960482107-13082002><SPAN=20
class=3D111145714-14082002>dBodyAddForceAtPos(body, fx, fy, fz, 0, 0, 0) =
has to do=20
a bunch of matrix math to split the force into a linear force and a =
torque=20
component, even though in this case the=20
torque=3D=3D0.</SPAN></SPAN></FONT></SPAN></FONT></SPAN></SPAN></SPAN></F=
ONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr><SPAN class=3D111145714-14082002><SPAN =
class=3D960482107-13082002><FONT=20
face=3DArial size=3D2><SPAN class=3D111145714-14082002><SPAN=20
class=3D471443000-29082002><SPAN class=3D960482107-13082002><FONT =
size=3D+0><SPAN=20
class=3D111145714-14082002><FONT face=3DVerdana><SPAN =
class=3D960482107-13082002><SPAN=20
class=3D111145714-14082002></SPAN></SPAN></FONT></SPAN></FONT></SPAN></SP=
AN></SPAN></FONT></SPAN></SPAN></SPAN></SPAN> </DIV>
<DIV dir=3Dltr><SPAN class=3D960482107-13082002><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D471443000-29082002> </SPAN></FONT><FONT face=3D"Times New =
Roman"=20
size=3D2>--<BR>Gary R. Van Sickle<BR>Brewer. Patriot.=20
</FONT></FONT></SPAN></DIV></BODY></HTML>
------=_NextPart_000_0027_01C24ECA.117DE9A0--