![](/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) |
In the superpatch.doc on the pattern it says:
".... If present, the hf_gray_16 specifier causes POV-Ray to create an image
that adheres to the TGA 16-bit encoding for heightfield information. ...."
Is my interpretation of this correct? Next to the standard output, there will
also be made a bitmap containing only the heigth_field data.
If so, where is this file written and with what name?
If not, what is meant with the quote?
ingo
--
Met dank aan de muze met het glazen oog.
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) |
On Thu, 20 May 1999 14:23:49 +0200, ingo wrote:
>In the superpatch.doc on the pattern it says:
>".... If present, the hf_gray_16 specifier causes POV-Ray to create an image
>that adheres to the TGA 16-bit encoding for heightfield information. ...."
>
>Is my interpretation of this correct? Next to the standard output, there will
>also be made a bitmap containing only the heigth_field data.
>If so, where is this file written and with what name?
>If not, what is meant with the quote?
No, it doesn't write a file. The hf_gray_16 makes the generated heightfield
data accurate to 16 bits instead of just to 8. I'll try to change the line
quoted above to make this more clear in the next version.
I'm also looking at other ways to do this in the future, so the heightfield
is generated directly from the pattern data instead of going through an
internal bitmap representation first, so this may all change in the future
anyway. (for example, in the next version, mcb has created a "pigment"
pattern for isosurfaces and a planar warp, so you might not ever need to use
the pattern keyword again.)
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) |
>No, it doesn't write a file. The hf_gray_16 makes the generated heightfield
>data accurate to 16 bits instead of just to 8. I'll try to change the line
>quoted above to make this more clear in the next version.
Ah, Ok.
>I'm also looking at other ways to do this in the future, so the heightfield
>is generated directly from the pattern data ......
Sounds good,
thanks, Ron
ingo
--
Met dank aan de muze met het glazen oog.
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) |
You could have a look in the source I posted in p.t.s-f entitled
'Waterscape source' which shows the current usage ...
Bye for now,
Mike Andrews.
ingo wrote:
>
> >No, it doesn't write a file. The hf_gray_16 makes the generated heightfield
> >data accurate to 16 bits instead of just to 8. I'll try to change the line
> >quoted above to make this more clear in the next version.
>
> Ah, Ok.
>
> >I'm also looking at other ways to do this in the future, so the heightfield
> >is generated directly from the pattern data ......
>
> Sounds good,
>
> thanks, Ron
>
> ingo
> --
> Met dank aan de muze met het glazen oog.
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) |