POV-Ray : Newsgroups : povray.advanced-users : <no subject> : Re: <no subject> Server Time
19 Apr 2024 18:37:59 EDT (-0400)
  Re: <no subject>  
From: clipka
Date: 14 Sep 2018 13:13:08
Message: <5b9bec24$1@news.povray.org>
Am 14.09.2018 um 12:28 schrieb Bald Eagle:

>> What you're multiplying is YVal, not U.
>> What you're debug-outputting is YVal rounded to 0 decimals, not YVal
>> (nor U, for that matter).
> 
> Well what I'm comparing the loop integer to is max(0, U*Ustep) [see far below],
> and it's crapping out right out of the gate.

Well, that's not the code you posted.

...

> My #debug output - those are macros - it's rounding to 3 decimals (see above),
> the 0 is a flag for +/- "\n".

Sorry, my bad. Skimming over the code, I had recognized the structure
typical for a `#debug` with invocations of `str()`, not realizing you
invoked something else entirely.

Still, 3 decimals is far below the precision of POV-Ray's float equality
tests.


Given your code, I'm pretty confident UArray[0].y will be 0, but from
the salami slices(*) of code you've posted so far, I can't say the same
for YVal; no post in this thread shows me how that value is computed, so
I don't trust it.

(* I hate to provide support for salami code, by the way. It means that
all I have to go by is "dry" code review, which for a meaningful answer
requires high attention to detail, and even then false assumptions or
misunderstandings may creep in and interfere. Give me a minimal complete
scene file to toy around with anytime, where I can easily verify my
assumptions and understandings by adding more `#debug` lines as I go
along. Providing such a scene may be more work on your side, but
probably saves as much work on mine, leaving more time for me to do
other POV-Ray related stuff.)


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.