





 
 




 
 


See example images posted in p.b.i
SkySim.inc is the macro, SkySimTestGround.pov is a simple example of a
scene using the macro.
Post a reply to this message
Attachments:
Download 'windows1252' (7 KB)
Download 'windows1252' (3 KB)


 
 




 
 


On 762013 13:51, scott wrote:
> SkySim.inc is the macro, SkySimTestGround.pov is a simple example of a
> scene using the macro.
Very good. Thanks very much indeed. Much better of course than the
simple example I gave :)
Thomas
Post a reply to this message


 
 




 
 


scott <sco### [at] scottcom> wrote:
> See example images posted in p.b.i
>
> SkySim.inc is the macro, SkySimTestGround.pov is a simple example of a
> scene using the macro.
Hello, I try your macro but I've got an error on line:
#local xyYtoR = function (x,y,Y){ (x/y* 3.2406 1.5372 + (1xy)/y *
0.4986)*Y/SkyMaxLuminance }
where Y seems undefined.
I am wrong?
Post a reply to this message


 
 




 
 


Le 130630 07:55, Fractracer a écrit :
> scott <sco### [at] scottcom> wrote:
>> See example images posted in p.b.i
>>
>> SkySim.inc is the macro, SkySimTestGround.pov is a simple example of a
>> scene using the macro.
>
> Hello, I try your macro but I've got an error on line:
> #local xyYtoR = function (x,y,Y){ (x/y* 3.2406 1.5372 + (1xy)/y *
> 0.4986)*Y/SkyMaxLuminance }
> where Y seems undefined.
> I am wrong?
>
Try calling the function this way:
xyYtoR(x,y,1)
This is a reason to NOT use "X", "Y" or "Z" as user variable names. It
can lead to some confusion.
Alain
Post a reply to this message


 
 




 
 


> Hello, I try your macro but I've got an error on line:
> #local xyYtoR = function (x,y,Y){ (x/y* 3.2406 1.5372 + (1xy)/y *
> 0.4986)*Y/SkyMaxLuminance }
> where Y seems undefined.
> I am wrong?
Y is one of the parameters for the function, so it becomes defined when
the function is called. What version of POV are you using? I've tried it
on 3.6 and 3.7 with no issues.
On 30/06/2013 18:14, Alain wrote:
> This is a reason to NOT use "X", "Y" or "Z" as user variable names.
> It can lead to some confusion.
I wouldn't normally do such a thing, but the colour space used by the
algorithm is Yxy. My POV version didn't complain or get confused about
using Y and y, so this makes the equations easier to read. I suppose I
could have used _Y or something.
Post a reply to this message


 
 




 
 


scott <sco### [at] scottcom> wrote:
> > Hello, I try your macro but I've got an error on line:
> > #local xyYtoR = function (x,y,Y){ (x/y* 3.2406 1.5372 + (1xy)/y *
> > 0.4986)*Y/SkyMaxLuminance }
> > where Y seems undefined.
> > I am wrong?
>
> Y is one of the parameters for the function, so it becomes defined when
> the function is called. What version of POV are you using? I've tried it
> on 3.6 and 3.7 with no issues.
>
> On 30/06/2013 18:14, Alain wrote:
> > This is a reason to NOT use "X", "Y" or "Z" as user variable names.
> > It can lead to some confusion.
>
> I wouldn't normally do such a thing, but the colour space used by the
> algorithm is Yxy. My POV version didn't complain or get confused about
> using Y and y, so this makes the equations easier to read. I suppose I
> could have used _Y or something.
It works (not fine but with no errors) when I change Y by z:
#local xyYtoR = function (x,y,z){ (x/y* 3.2406 1.5372 + (1xy)/y *
0.4986)*Y/SkyMaxLuminance }
I know this is not the good value but I try to see what happens.
I use v3.6 and v3.7 with the same result.
Post a reply to this message


 
 




 
 


> It works (not fine but with no errors) when I change Y by z:
> #local xyYtoR = function (x,y,z){ (x/y* 3.2406 1.5372 + (1xy)/y *
> 0.4986)*Y/SkyMaxLuminance }
> I know this is not the good value but I try to see what happens.
> I use v3.6 and v3.7 with the same result.
If you change the Y to z in the parameter list then just change the Y to
z in the equation too:
#local xyYtoR = function (x,y,z){ (x/y* 3.2406 1.5372 + (1xy)/y *
0.4986)*z/SkyMaxLuminance }
That should then work the same as the original version.
Post a reply to this message


 
 




 
 


scott <sco### [at] scottcom> wrote:
> > It works (not fine but with no errors) when I change Y by z:
> > #local xyYtoR = function (x,y,z){ (x/y* 3.2406 1.5372 + (1xy)/y *
> > 0.4986)*Y/SkyMaxLuminance }
> > I know this is not the good value but I try to see what happens.
> > I use v3.6 and v3.7 with the same result.
>
> If you change the Y to z in the parameter list then just change the Y to
> z in the equation too:
>
> #local xyYtoR = function (x,y,z){ (x/y* 3.2406 1.5372 + (1xy)/y *
> 0.4986)*z/SkyMaxLuminance }
>
> That should then work the same as the original version.
Thanks, I go to try this when my render in works will stop.
Post a reply to this message


 
 




 
 


> Thanks, I go to try this when my render in works will stop.
OK but I still find it odd you get an error when using Y as a parameter.
What is the exact error you get, can you copy and paste it here for us
to see?
If you copy the below code into an empty POV document (so just 1 line) 
does it work?
#local xyYtoR = function (x,y,Y){ x+y+Y }
Post a reply to this message


 
 




 
 


scott <sco### [at] scottcom> wrote:
> > Thanks, I go to try this when my render in works will stop.
>
> OK but I still find it odd you get an error when using Y as a parameter.
> What is the exact error you get, can you copy and paste it here for us
> to see?
>
> If you copy the below code into an empty POV document (so just 1 line) 
> does it work?
>
> #local xyYtoR = function (x,y,Y){ x+y+Y }
It work with a simple scene, I can't understand what's happens!!! With
sky_sim.inc ...
OOOPS!!! I've find, I have a variable declared Y... Excuse me...
Post a reply to this message


 
 




 