Here's an odd problem: when you choose PICT format for the output in 
MacMegaPOV(and my personal compile as well), every line in the 
post-processed image is off by one. The bottom line is garbage, the top 
line is missing, and all lines are moved up by one. This offset might 
also occur with image_maps, etc, but I have not tested that yet.(I 
rarely use images in my scenes, and usually use PNG or TGA format when I 
do)

-- 
Christopher James Huff - Personal e-mail: chr### [at] yahoocom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://chrishuff.dhs.org/
TAG Web page: http://tag.povray.org/

Post a reply to this message

In article <chrishuff_99-3B043C.08465925042000@news.povray.org> , Chris Huff
<chr### [at] yahoocom>  wrote:

> Here's an odd problem: when you choose PICT format for the output in
> MacMegaPOV(and my personal compile as well), every line in the
> post-processed image is off by one. The bottom line is garbage, the top
> line is missing, and all lines are moved up by one. This offset might
> also occur with image_maps, etc, but I have not tested that yet.(I
> rarely use images in my scenes, and usually use PNG or TGA format when I
> do)

It might be that some MegaPOV code counts from 1 to image height.  Make sure
that when MegaPOV calls MacFile_ReadLine the parameter line_number starts
with 0, not 1.  Then fix the MegaPOV code (not the sysmacpict code as a 0
base is required for it to work with other POV-Ray code).  You do not notice
this problem with other formats because PICT images cannot be loaded line by
line and therefore need a working line counter, while other formats may not
even use it.


      Thorsten

Post a reply to this message

In article <3905c5a7@news.povray.org> , "Thorsten Froehlich" 
<tho### [at] trfde> wrote:

> It might be that some MegaPOV code counts from 1 to image height.  Make sure
> that when MegaPOV calls MacFile_ReadLine the parameter line_number starts
> with 0, not 1.  Then fix the MegaPOV code (not the sysmacpict code as a 0
> base is required for it to work with other POV-Ray code).  You do not notice
> this problem with other formats because PICT images cannot be loaded line by
> line and therefore need a working line counter, while other formats may not
> even use it.

Actually it needs to be -1, not 0 (as MegaPOV sets it).  Just set the inital
line number in DoPostProcess to tmp = -1 .  This is required because the
reading functions are responsible for incrementing the line number.  For the
other formats it just does not matter as they don't use this line number
anyway.  Note that this requirement is based on the function
Read_Rendered_Part in POV-Ray 3.1.


     Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:

> 
> Actually it needs to be -1, not 0 (as MegaPOV sets it).  Just set the inital
> line number in DoPostProcess to tmp = -1 .  This is required because the
> reading functions are responsible for incrementing the line number.  For the
> other formats it just does not matter as they don't use this line number
> anyway.  Note that this requirement is based on the function
> Read_Rendered_Part in POV-Ray 3.1.
Will be fixed in MegaPov 0.5. Thanks!

Smellenbergh(s)
 
-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message