"Kenneth" <kdw### [at] gmailcom> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 26.10.2018 um 05:41 schrieb Anthony D. Baye:
> > > It seems to me that the engine used to throw an error when this happened...
> > ...
> > > Version 3.8.0-alpha.9606898.unofficial
> >
> > That's on Linux, I presume?
> >
> > POV-Ray does produce a warning if the second operand compares /equal to
> > zero/.
> > [etc]
> >
>
> For what it's worth, in POV-Ray for Windows v3.7.1 beta 9, I see the same
> results as Anthony's original image-- the misplaced orange dot and the missing
> hexagons at the top.
>
> The only error messages I get are the expected ones: A missing assumed_gamma,
> and the #version directive not being the first statement in the scene.
>
> (By adding #version 3.71 , I get the same results, except for a quality
> difference in the renders. But no *new* warning message.)

I've got it working.  There are a couple lines in the IPoint macro that "Fix"
the problem (at least until offsets get really big) by ensuring that the slope
is never undefined.

I'm sure there's a method for finding intersections of two lines that isn't
vulnerable to this problem, but I haven't figured it out yet.

Regards,
A.D.B.

Post a reply to this message