|
![](/i/fill.gif) |
Warp <war### [at] tag povray org> wrote:
> Geoff Wedig <wed### [at] darwin epbi cwru edu> wrote:
> : So, anyone know why this is the way it is?
> This is what I have wondered as well. The only reason I can think of
> is memory saving.
> As this is not currently really necessary double precision could be feasible.
> You can change the SNGL type to double (in frame.h) and see if it helps.
Yeah, but that'll change things in lots of other places. I don't want to
make that kind of global switch. I could just change it in the mesh code,
but I don't know the code very well, yet, and worried that it'd introduce
subtle bugs.
What I'm probably going to do is simulate using doubles. After the
simulation is done, I can copy them into the float vector that the mesh
uses. That way, I get the advantages of the extra precision when it's
necessary, but don't have to worry about it later.
Geoff
Post a reply to this message
|
![](/i/fill.gif) |