|
![](/i/fill.gif) |
Chris Huff wrote in message ...
>Maybe a specialized sort of isosurface function could also be useful. It
>would have additional variables(r, g, and b at least), and the filter
>would take 3 of them, one for each channel. Maybe the syntax could also
>be set up so if only one is specified, it is used for all 3 channels.
>Hmm, some of these could also be good effects for textures...what do you
>think of that idea? "texture_process"? :-)
How about a post-process that will run a pov-script macro? It would allow
the user to create any custom post-process filter that they need, and would
be completely platform-independant. The disadvantage to this is that it
wouldn't be very fast, but,for most post-processing, that wouldn't matter.
Mark
Post a reply to this message
|
![](/i/fill.gif) |