[ODE] OPCODE vs. double
DjArcas
djarcas at hotmail.com
Sun Jul 6 10:43:03 2003
This is a multi-part message in MIME format.
------=_NextPart_000_01DB_01C343EE.9315C220
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The simplest solution is to create your 3d device with =
D3DCREATE_FPU_PRESERVE when your program requires great accuracy, IE a =
physics system. There is a performance hit, at least theoretically - =
I've not seen anything change on my system, and I'm chunking a lot of =
polys at the screen. Changing ODE's accuracy to cope with something that =
D3D can be told NOT to do doesn't seem like the best solution, IMO.
----- Original Message -----=20
From: "Timothy J. Wood" <tjw@omnigroup.com>
To: <ode@q12.org>
Sent: Sunday, July 06, 2003 6:19 PM
Subject: [ODE] OPCODE vs. double
>=20
>=20
> I'm sort of worried since I've seen people on this list mentioned=20
> that D3D breaks their simulation (since it gets rid of the extra=20
> precision by default), but then OPCODE requires single precision.
>=20
> So, what's going to give? Are we just supposed to abandon double=20
> support in ODE or should OPCODE be made to work with double for when=20
> you need precision more than space? Can ODE be made to lose less=20
> precision in floats (seems unlikely)? Other solutions?
>=20
> -tim
>=20
> _______________________________________________
> ODE mailing list
> ODE@q12.org
> http://q12.org/mailman/listinfo/ode
>
------=_NextPart_000_01DB_01C343EE.9315C220
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>The simplest solution is to create your =
3d device=20
with </FONT><FONT face=3DArial size=3D2>D3DCREATE_FPU_PRESERVE when your =
program=20
requires great accuracy, IE a physics system. There is a performance =
hit, at=20
least theoretically - I've not seen anything change on my system, and =
I'm=20
chunking a lot of polys at the screen. Changing ODE's accuracy to cope =
with=20
something that D3D can be told NOT to do doesn't seem like the best =
solution,=20
IMO.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>----- Original Message ----- </FONT>
<DIV><FONT face=3DArial size=3D2>From: "Timothy J. Wood" <</FONT><A=20
href=3D"mailto:tjw@omnigroup.com"><FONT face=3DArial=20
size=3D2>tjw@omnigroup.com</FONT></A><FONT face=3DArial =
size=3D2>></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>To: <</FONT><A =
href=3D"mailto:ode@q12.org"><FONT=20
face=3DArial size=3D2>ode@q12.org</FONT></A><FONT face=3DArial=20
size=3D2>></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sent: Sunday, July 06, 2003 6:19 =
PM</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Subject: [ODE] OPCODE vs. =
double</FONT></DIV></DIV>
<DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT =
face=3DArial=20
size=3D2>> <BR>> <BR>> I'm sort of worried since =
I've seen=20
people on this list mentioned <BR>> that D3D breaks their simulation =
(since=20
it gets rid of the extra <BR>> precision by default), but then OPCODE =
requires single precision.<BR>> <BR>> So, what's =
going to=20
give? Are we just supposed to abandon double <BR>> support in =
ODE or=20
should OPCODE be made to work with double for when <BR>> you need =
precision=20
more than space? Can ODE be made to lose less <BR>> precision =
in floats=20
(seems unlikely)? Other solutions?<BR>> <BR>> -tim<BR>> =
<BR>>=20
_______________________________________________<BR>> ODE mailing =
list<BR>>=20
</FONT><A href=3D"mailto:ODE@q12.org"><FONT face=3DArial=20
size=3D2>ODE@q12.org</FONT></A><BR><FONT face=3DArial size=3D2>> =
</FONT><A=20
href=3D"http://q12.org/mailman/listinfo/ode"><FONT face=3DArial=20
size=3D2>http://q12.org/mailman/listinfo/ode</FONT></A><BR><FONT =
face=3DArial=20
size=3D2>> </FONT></BODY></HTML>
------=_NextPart_000_01DB_01C343EE.9315C220--