|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi folks,
I have been using megapov for a few days. Specifically, i am interested in
extracting the Intersection points using the post process options in
megapov. The code that i use was a hack of some samples available on the
net. I have attached it below.
#version unofficial MegaPov 1.2;
#include "pprocess.inc"
PP_Init_IPoint_Outputs()
global_settings {max_trace_level 5}
global_settings {
post_process {
function { f_output_ipoint_x(u,v) } // calculation of red component
function { f_output_ipoint_y(u,v) } // calculation of green component
function { f_output_ipoint_z(u,v) } // calculation of blue component
function { 1 } // calculation of transperancy component
save_file concat("pp_",output_filename(0))
}
}
The code works fine ... but the output is written to BMP, this doesn't allow
for negative values to be dumped (these are clipped to zero) and values
higher than 255 are also cutoff.
IS THERE a way to dump the Ipoint information in a ascii file ... any
suggestions/pointers on how to go about extracting the information ? I
appreciate any help in this. Thanks in advance.
some background info: I am using XP with the latest stable version of PovRay
and Megapov ...
Aswin
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 20 Jan 2006 13:02:09 EST, "aswch" <asw### [at] yahoocom> wrote:
> IS THERE a way to dump the Ipoint information in a ascii file ...
Yes, you don't post process for it. Just loop over trace() function within
script should be enough. HTH,
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX <abx### [at] abxartpl> wrote:
> On Fri, 20 Jan 2006 13:02:09 EST, "aswch" <asw### [at] yahoocom> wrote:
> > IS THERE a way to dump the Ipoint information in a ascii file ...
>
> Yes, you don't post process for it. Just loop over trace() function within
> script should be enough. HTH,
>
> ABX
Thanks for the pointer. Trace() definitely seems to be one possible way of
doing it .. although a bit tricky to register the ray orientations with
those used for rendering the image, as I would need information about the
focal length etc ...
Still, it seems to be a possible approach. Thanks.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|