POV-Ray : Newsgroups : povray.general : Height_field help : Re: Height_field help Server Time
24 Feb 2024 23:53:14 EST (-0500)
  Re: Height_field help  
From: Kenneth
Date: 7 Mar 2023 01:55:00
Message: <web.6406df0c3575e8099b4924336e066e29@news.povray.org>
"Leroy" <whe### [at] gmailcom> wrote:
>
> I just found this in my docs...
>
> 3.4.7.6.1 Specifying an Image Map
> IMAGE_MAP:
>   pigment {
>     image_map {
>       [BITMAP_TYPE] "bitmap[.ext]" [gamma GAMMA] [premultiplied BOOL]
>  If the BITMAP_TYPE is not given, the same type is expected as the type
>  set for output.

For my previous test, I glanced over that last sentence but didn't pay
attention.

So I ran a bunch more simple tests in official v3.8.0 beta 1, with various
image_map and file-type suffixes, and intentionally mis-matched my render-file
output type-- JPEG image_map vs. Output_File_Type=N, etc. The tests all ran OK,
so it seems that the last sentence is no longer a requirement in v3.8xx.

But about the original macro here: I still cannot get it to run, despite
fiddling with various parts. I don't know if the following experiment is
helpful, but for the very beginning of the code, I added a few things to see
what would happen:

#macro Image(File)
 #local L=strlen(File);
 #debug concat("\n","L = ",str(L,0,3),"\n")
 #error
....
#end

Then, same as before...
#declare FileStr= "test image for hf png.png"
height_field{Image(Filestr)}

I half-way expected to at least get a #debug output for L=strlen(File), then a
halt to the whole process-- but no #debug message shows up, just the previous
error of "Cannot pass unitialized identifier as macro parameter..."

Leroy, does your macro *as written in this newsgroup thread* run OK on your own
system? (with the minor fix of the added parentheses, that is)


Post a reply to this message

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