In article <3ca4d1af@news.povray.org>,
 "Rune" <run### [at] mobilixnetdk> wrote:

> > I forgot about that...well, the workaround is to scale
> > it down into the [0, 1] range in the function and scale
> > it back outside.
> 
> What do you mean? Using atan2() and tan(), or...?

Well, that's something I hadn't thought of...I was actually talking 
about doing something like having the function return x/TurbSclFact and 
using turb_x(x, y, z)*TurbSclFact, where TurbSclFact is some big value. 
Basically, move the problem somewhere where it probably won't bother 
you. As I said, it is a workaround...
Your idea of using atan2 and tan might work better though...

What I would really like is for patterns to return unclipped values. The 
clipping would be done by the waveforms, for example, "ramp_wave 0, 1" 
would repeatedly ramp from 0 to 1 as the input range increases. You 
would also be able to apply different waveforms to further modify the 
pattern output. Phase and frequency would also be waveform modifiers.

If you don't want to have to specify a waveform for every pattern, there 
could be a default waveform that would be overridden by user-specified 
waveforms...you could specify "no_waveform" or something to get the raw 
pattern output when you need it.

-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/

Post a reply to this message