|
![](/i/fill.gif) |
Tim Cook <z99### [at] bellsouth net> wrote:
> The problem is basically in how computers handle numbers. They can't
> easily do very small and very large (or normal and extremely large)
> numbers at the same time.
Actually the reason why the object disappears is not floating point
inaccuracy but because POV-Ray drops the object if it's too far away.
Naturally POV-Ray does this in order to avoid the accuracy problems,
but it's not the accuracy which is dropping out the object but POV-Ray.
There's a reason for this: It's very possible that if POV-Ray didn't
drop the object, it might render with bad artifacts.
See http://tag.povray.org/povQandT/languageQandT.html#largescaleproblems
for details.
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
![](/i/fill.gif) |