By the way, perhaps you should mention in the page the exact rendering
settings you will be using to render the images (the command-line options
should suffice).
  If you have a fast machine, I propose rather good-quality settings
(mainly with regard to antialiasing, something like "+a0.1 +am2").

  And you perhaps might like to add a restriction of the type "the image
should not take more than <n> hours to render with these settings in
a <computer type>".

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message

On Sun, 08 Feb 2004 22:13:05 +1100, Paul Bourke <pdb### [at] swineduau>
wrote:
> Consider the POVRay Short Code Contest round 3 (SCC3) open!

Great!

> The beginnings of the www page is here
>    http://astronomy.swin.edu.au/scc3/
> It will evolve as time goes on. If you have any suggestions,
> corrections, complaints (surely not), then feel free to
> email me or post them here for debate.

I think idea of 'examples' page should be done in form of directing to
previous rounds rather then separate page page. I wonder if it would be
possible to create:
    http://astronomy.swin.edu.au/scc1/
    http://astronomy.swin.edu.au/scc2/
I'm sure neither Chris Cason (who holds its previous domain) nor Greg would
protest.

Btw rendering with Linux: This is a first beta of 3.6, not Nth. While I do
think it is good quality, I think you should consider verification of rendered
image with poster before publication on voting page. There is always
possibility that Windows owners could see different rendering than Linux
owners due to nature of beta test phase of development.

ABX

Post a reply to this message

On Mon, 09 Feb 2004 11:11:05 +0100, ABX <abx### [at] abxartpl> wrote:
> There is always
> possibility that Windows owners could see different rendering than Linux
> owners due to nature of beta test phase of development.

Sorry for excluding Mac users ;-)

ABX

Post a reply to this message

Warp wrote:
> 
>   And you perhaps might like to add a restriction of the type "the image
> should not take more than <n> hours to render with these settings in
> a <computer type>".
> 

Please don't be too strict there, my current WIP takes about 5 hours at 
320x240, no aa on an Athlon 1GHz.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 11 Jan. 2004 _____./\/^>_*_<^\/\.______

Post a reply to this message

Christoph Hormann <chr### [at] gmxde> wrote:
> Please don't be too strict there, my current WIP takes about 5 hours at 
> 320x240, no aa on an Athlon 1GHz.

  Well, I think he has to put some upper limit for practical reasons.
If each entry would take 24 hours to render (at 800x600 with antialiasing),
rendering all the entries would take as many days as there are entries... :)

  But naturally the upper limit can probably be set quite high (eg. 24h)
because not all the entries will take that long to render. Most entries
will probably render in minutes.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

On 9 Feb 2004 05:50:34 -0500, Warp <war### [at] tagpovrayorg> wrote:
>  Well, I think he has to put some upper limit for practical reasons.
> If each entry would take 24 hours to render (at 800x600 with antialiasing),
> rendering all the entries would take as many days as there are entries... :)

Isn't there ren### [at] paulbourke ?

ABX

Post a reply to this message

chr### [at] gmxde news:to2### [at] tritonimagicode

> Please don't be too strict there, my current WIP takes about 5 hours at 
> 320x240, no aa on an Athlon 1GHz.
> 

How about - rendering time shouldn't exceed 3 days on 2GHz in 800x600 +a.03 
+am2 +r2 *but* all contestends must submit .png file(s) if render tooks 
more then 30 minuts (so that author of contest will not have problems 
rendeing all entries)

-- 
#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

> It will evolve as time goes on. If you have any suggestions,
> corrections, complaints (surely not), then feel free to
> email me or post them here for debate.

Complaint: 256 chars is too short. I would like to have the original (?)
500 at my disposal. Please let's turn this into a LONG code contest... ;-)


-- 
merge{#local i=-11;#while(i<11)#local
i=i+.1;sphere{<i*(i*i*(.05-i*i*(4e-7*i*i+3e-4))-3)10*sin(i)30>.5}#end
pigment{rgbt 1}interior{media{emission x}}hollow}//  Mark Weyer

Post a reply to this message

Mark Weyer <wey### [at] informatikuni-freiburgde> wrote:
> Complaint: 256 chars is too short.

  I think it's ok. Requires more ingenuity to get something to look good
with that few characters, which makes it interesting.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Mark Weyer wrote:
> Complaint: 256 chars is too short. I would like to have the original (?)
> 500 at my disposal. Please let's turn this into a LONG code contest... ;-)

Long code contest?  Points going to the most denst, voluminous code,
with commented lines not counting towards the end result, and no fair
setting up five million spheres *behind* the camera?

Post a reply to this message