POV-Ray : Newsgroups : povray.general : save hf pattern ? : Re: save hf pattern ? Server Time
5 Aug 2024 18:24:58 EDT (-0400)
  Re: save hf pattern ?  
From: Rafal 'Raf256' Maj
Date: 30 Sep 2002 16:44:08
Message: <Xns9299E70BBF523raf256com@204.213.191.226>
Christopher James Huff <chr### [at] maccom> wrote in
news:chr### [at] netplexaussieorg 

> That won't work. The user would have to delete the file every time
> they changed something.

no - read below,
 
>> whitespaces/comments, to get "ID" of this pattern "x+y+z*sin(x*10)"
> Not possible, the function could easily depend on things you couldn't 
> detect this way, and different functions could result in the same 
[...]

all variables are changed into literal values, like :
x *sin(y)*power + clock  into :
x*sin(y)*1.5+0.1333


>> + render time is not about 10:00 but about 0:10 
> Render time is not affected at all. Total time including parse might
> go from 10 minutes to 9 minutes 30 seconds.

no. Very basic pattern that I used to create mountains, parses 15 sec. on 
1500x1500


>> + we can run .pov %100 automaticly
> No improvement. You could automate it now, in fact several scenes do 
> this already, using the animation feature. Or you could use a
> (platform dependant) shell script. There are lots of other
> possibilities, you are trying to solve a non-problem.

wouldn't adding 1 keyword be easier/nicer/more comfortable for users then 
writting scripts ? What if linux user want's to give it to un-expirienced 
windows suer (with fast machine) or vice-versa ?
 
>> + HF's will be recalculated only if needed
> Saving a tiny amount of time. A solution without a problem.

no. Did You try any complex pattern function yet ? That would generate 
realy nice mountains ? Or wait, I will post litte example soon.

>> + users HDD space will not wasted by outdated cache files
> But it will.

only if user wants to do so. I.e. I want to spare some of 60 GB HDD to 
increase rendering/parsing speed.

> into an extremely complex 

save .tga of 2d array of height_field - is this extremly complex for You ?

> unpredictable, unportable, 

why ? I agreee .tga is better then raw data.

> wasteful 

?
 
-- 
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M


Post a reply to this message

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