 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
From: Warp
Subject: Re: Announcement - POVRay Short Code Contest Open - Round 3
Date: 9 Feb 2004 05:50:34
Message: <402765fa@news.povray.org>
|
|
|
| |
| |
|
|
Christoph Hormann <chr### [at] gmx de> 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
|
|
| |
| |
|
|
From: Warp
Subject: Re: Announcement - POVRay Short Code Contest Open - Round 3
Date: 9 Feb 2004 16:09:04
Message: <4027f6f0@news.povray.org>
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
From: Tim Cook
Subject: Re: Announcement - POVRay Short Code Contest Open - Round 3
Date: 9 Feb 2004 17:18:42
Message: <40280742@news.povray.org>
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > 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 ?
Yes there is and it will be used if necessary.
Anyone who submits something that takes 200+ processors more than a
couple of hours probably hasn't rendered the image themselves.
--
Paul Bourke
pdb_NOSPAMswin.edu.au
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > Please don't be too strict there, my current WIP takes about 5 hours at
> > 320x240, no aa on an Athlon 1GHz.
You guys are scaring me.
> 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... :)
They will be rendered as they are submitted so that might help a bit.
I have also allocated 5 days from the end of contest closure to the
start of the rendering.
I'll think about a limit, one possibility is to say "rendering will
start as soon as the entry is received, it must finish before the
voting starts".
--
Paul Bourke
pdb_NOSPAMswin.edu.au
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 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").
The current (minimal) ini file is
Output_File_Type=C
Width=800
Height=600
Quality=9
Antialias=on
Antialias_Threshold=0.01
If people have special requirements (radiosity, oh no!) then
I will consider them. The jpg is made with "convert" with quality
set to 95%.
--
Paul Bourke
pdb_NOSPAMswin.edu.au
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
