POV-Ray : Newsgroups : povray.general : Height_field help : Re: Height_field help Server Time
26 Apr 2024 02:11:34 EDT (-0400)
  Re: Height_field help  
From: Leroy
Date: 6 Mar 2023 18:40:00
Message: <web.640678e43575e8097f7263c5f712fc00@news.povray.org>
"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Leroy" <whe### [at] gmailcom> wrote:
>
> >  #if(Bs="tga") tga File #end
> >  #if(Bs="bmp") bmp File #end
> >  #if(Bs="pgm") pgm File #end
> >  #if(Bs="png") png File #end
> >  #if(Bs="ppm") ppm File #end
> >  #if(Bs="jpg") jpeg File  #end
> >  #if(Bs="exr") exr File #end
> >  #if(Bs="hdr") hdr File #end
> >  #if(Bs="gif") gif File #end
> >  #if(Bs="iff") iff File #end
> >  #if(Bs="tif") tiff File  #end
>
> AFAIK, you don't need any of this stuff any more, because POV-Ray automatically
> determines the file type, and so those keywords can be omitted.

I do! my version 3.7.0.RC7.mevc10.sse.win323.7 will let you do this

plane{z,0 pigment{image_map{"Uimage.tga"}} finish{ambient 1}}

but not this :

#declare I_File="Uimage.pgm";

plane{z,0 pigment{image_map{I_File}} finish{ambient 1}}
             OR
#declare PigM=function{pigment{image_map{I_File once}}}
             OR
#declare PigM=function{pigment{image_pattern{I_File}}}

I'm comparing function to image_map height_fields. I needed the macro so I would
have to rewrite the file I'm using for each height_field.

My version 3.7 for my 64bit running on win10 Acts the same.

I can write the file string directly into both of the functions above, But I was
trying  not to do that.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.