![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
While the x and z dimensions of the contained_by box are obviously up to me,
how do I work out what (sensible) values to use for the y dimensions of, for
example, the following:
#declare MountFunc = function{"ridgedMF" <0.9, 2, 5, 0.75, 2>}
#declare MBase =
isosurface{
function { y - MountFunc(x,0,z) * min(2, max(0.125,(sqr(x/5) +
sqr(z/5)))) }
eval
max_gradient 50
contained_by{box{<-20,-1,-20>,<20,15,20>}}
texture{MBaseTex}
}
--
"To stop children being afraid of the dark, try to fill their daylight hours
with as much terror as possible"
www.tomandlu.co.uk
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Tom Melly" <tom### [at] tomandlu co uk> wrote in message
news:3ad5b7d6@news.povray.org...
> While the x and z dimensions of the contained_by box are obviously up to
me,
> how do I work out what (sensible) values to use for the y dimensions
Trial and error. HTH ! ;-)
--
Scott Hill
Software Engineer.
NC Graphics (Cambridge) Ltd.
Web : http://www.ncgraphics.co.uk
E-mail : sco### [at] ncgraphics net
ICQ : 110661991
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Scott Hill" <sco### [at] ncgraphics net> wrote in message
news:3ad5c206@news.povray.org...
>
> Trial and error. HTH ! ;-)
... a phrase that I always find faintly worrying. Is there really no better
way? Anyone, someone?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tom Melly <tom### [at] tomandlu co uk> wrote:
> "Scott Hill" <sco### [at] ncgraphics net> wrote in message
> news:3ad5c206@news.povray.org...
>>
>> Trial and error. HTH ! ;-)
> ... a phrase that I always find faintly worrying. Is there really no better
> way? Anyone, someone?
Well, how'd you come up with the rmf parameters in the first place? I've
found no way to do that either, short f trial and error, so.... *shrug*
Geoff
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
If I understand your question correctly you are looking for sensible
proportions of vertical to horizontal dimensions? I find a y dimension
10-20% of the xz dimension works as an average good start for scaling
height fields. Ultimately trial and error prevails.
Abe
Tom Melly wrote:
>
> While the x and z dimensions of the contained_by box are obviously up to me,
> how do I work out what (sensible) values to use for the y dimensions of, for
> example, the following:
>
> #declare MountFunc = function{"ridgedMF" <0.9, 2, 5, 0.75, 2>}
> #declare MBase =
> isosurface{
> function { y - MountFunc(x,0,z) * min(2, max(0.125,(sqr(x/5) +
> sqr(z/5)))) }
> eval
> max_gradient 50
> contained_by{box{<-20,-1,-20>,<20,15,20>}}
> texture{MBaseTex}
> }
>
> --
> "To stop children being afraid of the dark, try to fill their daylight hours
> with as much terror as possible"
> www.tomandlu.co.uk
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |