|
|
Playing for first time with the new function image type, and being so bad
closing sentences, I tried to parse this code:
height_field{
function 128,128{
pigment{
bozo
color_map{
[0.00 rgb 0]
[1.00 rgb 1]
}
/* here is missing a closing bracket */
}
translate -.5
}
And got :
Parse Error: No matching } in '{', translate found instead
When it should read:
Parse Error: No matching } in 'function', translate found instead
...isn't?
P.S.: Also, it sometimes hanged POV when the editor tried to highlight the
line containing the error (which was not highlighted when POV hanged).
Jaime Vives Piqueres
POV-Ray for Windows 3.5 beta 1
W98SE on AMD Athlon 1.2Ghz, 256MB SDRAM, >50Db CPU fan.
Post a reply to this message
|
|
|
|
By the way, I think it should be made clear in the documentation that using
a pattern in an image function is more efficient than using a pigment.
Why? Because a pattern creates a b/w image while a pigment creates a color
image, which is (I suppose) 3 times bigger (ie. it takes 3 times more memory).
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
|
|
news:3b9ca618@news.povray.org...
> By the way, I think it should be made clear in the documentation that
using
> a pattern in an image function is more efficient than using a pigment.
> Why? Because a pattern creates a b/w image while a pigment creates a
color
> image, which is (I suppose) 3 times bigger (ie. it takes 3 times more
memory).
Ah! Yes, I see: 6.1.6.1. Not read this before, I was only converting an old
"pigment_pattern" from megapov.
(I read the docs "on the fly"). But you are right: a quick test revealed
that it uses half the memory needed with a pigment (not 1/3, tough).
Thanks!
Jaime
Post a reply to this message
|
|