Chris Huff wrote in message ...
>In article <8FE01D1B3markwagner17gtenet@204.213.191.228>,
>mar### [at] gtenet (Mark Wagner) wrote:
>
>> Features that might make a future version:
>>  * Colour curve post-processing to replace the infinite-light hack
>
>I am going to make a post_process filter which uses a spline to adjust
>color values...is this what you are talking about?


Yes.

>
>>  * Random rendering order
>
>You mean it picks a random pixel each time? Another thing that might be
>nice: some kind of "progressive" antialiasing, that renders the image
>without antialiasing and then makes several "refinement" passes.


That's going to be part of the system, since I can't do antialiasing with
just one pixel.

>
>>  * A polynomial parser to allow polys to be written as "3x^5+2xy+z-1"
>>  etc.
>
>Couldn't you use isosurface functions? I haven't had a look at your
>patch yet, so I don't really know what this is for...


I don't have it implemented yet, but this will be for the "poly" object
type.  It's much easier to enter a formula for a 7th-order polynomial as a
formula than as a string of a hundred coefficients.

>
>>  * Improved "quality" command-line options
>
>I hope command line options aren't necessary for this...you should be
>able to specify all options in the scene file. Or are you talking about
>changing the "Render Quality" option syntax?


Yes, render quality options.  I'm going to make it possible to turn specific
things on and off -- specifically, these will be available in version 0.2:
 +QQ = use quick colors
 +QA = use area lights -- cancels +QF
 +QF = use ambient only -- cancels +QA, +QM
 +QS = calculate shadows
 +QM = use reflection -- cancels +QF
 +QL = use refraction
 +QN = use normals
 +QV = use media?

>>  * Improved splines
>
>I would suggest using one of the spline patches...less duplicate code,
>more standardized, etc...


This is going to be an improvement on the spline{} syntax.

Mark

Post a reply to this message

Mark Wagner wrote in message
<8FE01D1B3markwagner17gtenet@204.213.191.228>...
>Announcing.....SkyPOV 0.1!


A Windows binary is available at:
http://www.geocities.com/rengaw03/download/wskypov.zip


Mark

Post a reply to this message

I tried to use the link provided but geocities said
that page was not available. I tried .../rengaw03/download/
and HAL invited me to go back.

sniff..... I so wanted to see this version.... sniff

Mark Wagner wrote:
> 
> Mark Wagner wrote in message
> <8FE01D1B3markwagner17gtenet@204.213.191.228>...
> >Announcing.....SkyPOV 0.1!
> 
> A Windows binary is available at:
> http://www.geocities.com/rengaw03/download/wskypov.zip
> 
> Mark

Post a reply to this message

In article <3a025559$1@news.povray.org>, "Mark Wagner" 
<mar### [at] gtenet> wrote:

> >I am going to make a post_process filter which uses a spline to adjust
> >color values...is this what you are talking about?
> Yes.

I will send you the code as soon as it is tested.


> >You mean it picks a random pixel each time? Another thing that might be
> >nice: some kind of "progressive" antialiasing, that renders the image
> >without antialiasing and then makes several "refinement" passes.
> That's going to be part of the system, since I can't do antialiasing with
> just one pixel.

Good. :-)


> I don't have it implemented yet, but this will be for the "poly" 
> object type.  It's much easier to enter a formula for a 7th-order 
> polynomial as a formula than as a string of a hundred coefficients.

Oh, I thought this was for something else...this seems rather redundant, 
since you can just use isosurfaces to do the same thing, and 
often(usually?) with faster rendering.


> >I would suggest using one of the spline patches...less duplicate code,
> >more standardized, etc...
> 
> This is going to be an improvement on the spline{} syntax.

Oh...
Ok, what improvements are you thinking of? More spline types, the 
ability to choose what kind of spline to use at evaluation time?

By the second, I mean something like this:
#declare Spline = spline {...the usual spline stuff...}

#declare Val1 = Spline(XVal);
#declare Val2 = Spline(XVal, cubic_spline);
#declare Val3 = Spline(XVal, linear_spline);

Another wild idea that might be useful: allow splines to be used as 
color maps. :-)

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message

"Mr. Art" wrote:
> 
> I tried to use the link provided but geocities said
> that page was not available. I tried .../rengaw03/download/
> and HAL invited me to go back.
> 

Ditto

-- 
Margus Ramst

Personal e-mail: mar### [at] peakeduee
TAG (Team Assistance Group) e-mail: mar### [at] tagpovrayorg

Post a reply to this message

Chris Huff wrote in message ...
>In article <3a025559$1@news.povray.org>, "Mark Wagner"
><mar### [at] gtenet> wrote:
>
>> >I am going to make a post_process filter which uses a spline to adjust
>> >color values...is this what you are talking about?
>> Yes.
>
>I will send you the code as soon as it is tested.


Thanks!

>> >I would suggest using one of the spline patches...less duplicate code,
>> >more standardized, etc...
>>
>> This is going to be an improvement on the spline{} syntax.
>
>Oh...
>Ok, what improvements are you thinking of? More spline types, the
>ability to choose what kind of spline to use at evaluation time?
>
>By the second, I mean something like this:
>#declare Spline = spline {...the usual spline stuff...}


I'm going to be removing the limit on the number of points in a spline, and
making it possible to use the points from one spline as the basis for
another spline, like:

#declare Spline2 = spline{ Spline 1,<2,2,2> etc.}

Right now you can't do that.

--
Mark

Post a reply to this message

Margus Ramst wrote in message <3A03A18D.FDFBCBF0@peak.edu.ee>...
>"Mr. Art" wrote:
>>
>> I tried to use the link provided but geocities said
>> that page was not available. I tried .../rengaw03/download/
>> and HAL invited me to go back.
>>
>
>Ditto


How odd.  I just downloaded it successfully from that address.  Was it
giving you a "file not found" error, or some other error message?

Mark

Post a reply to this message

Try the links from my POV-Ray downloads page to see if they work for you.

http://www.geocities.com/rengaw03/povray.html


--
Mark

Post a reply to this message

Mark Wagner wrote:
> 
> Try the links from my POV-Ray downloads page to see if they work for you.
> 

Got it.
As far as I know Geocities doesn't like direct download links originating from
non-geocities addresses. Since your home page is also at Geocities, a link from
there will work.

-- 
Margus Ramst

Personal e-mail: mar### [at] peakeduee
TAG (Team Assistance Group) e-mail: mar### [at] tagpovrayorg

Post a reply to this message

In article <3a03ab54$1@news.povray.org>, "Mark Wagner" 
<mar### [at] gtenet> wrote:

> >I will send you the code as soon as it is tested.
> Thanks!

I'm having a hard time getting it to work though...I suspect the problem 
is in my parsing code, though I'm not sure why it is misbehaving. 
Anyway, this is the syntax I am planning to use(I am currently working 
on the first form):
curves {rgb RED_SPLINE, GREEN_SPLINE, BLUE_SPLINE}
curves {red RED_SPLINE}
curves {green GREEN_SPLINE}
curves {blue BLUE_SPLINE}
curves {gray GRAY_SPLINE}
(got a better name for the last one? "all"?)

When I add color space conversion filters, you will be able to adjust 
other types with these filters(convert to another color space, modify 
the correct channel, convert back to rgb).


> I'm going to be removing the limit on the number of points in a spline, 

There is a limit? I hadn't noticed...


> and making it possible to use the points from one spline as the basis 
> for another spline, like:
> #declare Spline2 = spline{ Spline 1,<2,2,2> etc.}
> Right now you can't do that.

I noticed the Parse_Spline() function had the ability to take an 
identifier to create a copy of the spline, but also had a bug which made 
that useless when no new points were defined. I think it was intended to 
work the way you describe, allowing new points to be inserted.

Also, it would be useful if you could access the control points, with 
functions that behave similar to the array functions and an array-like 
syntax.

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message