POV-Ray : Newsgroups : povray.general : Shortest Code Contest Server Time
15 Oct 2026 07:02:12 EDT (-0400)
  Shortest Code Contest (Message 1 to 33 of 33)  
From: Greg M  Johnson
Subject: Shortest Code Contest
Date: 18 Jan 2002 09:46:25
Message: <3c483541$1@news.povray.org>
Let's put this creative effort used on sigs to use!

SHORTEST CODE CONTEST

Povray has many strengths.  On one hand it can compete with some of the best
professional packages in the production of photorealistic images with
radiosity from the DXF output of a modelling program. On the other hand, it
IS amazing what the thoughtful amateur can do with just a few lines of ASCII
text. IMHO, this second quality of povray is a better "poster boy" for the
program and much more *fun*.

Many pov'vers like to celebrate this second quality of povray with
innovative signature files: making something really interesting with just a
few bytes of text.

Let's have a contest.

HOW TO ENTER:
Send an email to Greg M. Johnson at gre### [at] aolcom with two attachments:

1) your submission in the form of a XYZ.pov file.

    a) Please don't have any personal info in the image as the contest will
be judged blind. For example, if you currently have text that says, "BILLY
POVUSER", change it to "POV 3.5" or "POVVERS RULE" or something else.

    b) Make it compatible with povray 3.5.

    c) no #includes or #reads or #writes or #fopens are permitted.

    d) MAX size: 500 bytes (arbitrarily chosen as twice the size of one very
competent sig file posted to p.g.)

    e) have it end with //XYZ, where XYZ is a (hopefully) unique 3-digit
combination of your initials and/or numbers

2) an XYZ.txt file with

     a)	your name,
     b)	email adresss,
     c)	web page,
     d) and any other comments you want to make about the image.

3) Please make the title of your email distinct from typical junk mail,
something like, "[Shortest Code Contest]"

HOW IT WILL RUN:

1) An 800 x 600 jpg of your pov file will be prepared.

2) A web page will be prepared where all of the image are visible, BUT NO
personal or author information NOR any data about the scene file

3) Participants will vote on their favorite five images (or some other
criteria).  No one will know how many bytes are in the pov file during the
judging!

4) Prizes (in the form of praise) will be given to:
   a) highest score
   b) lowest bytes to still get rated as someone's favorite 5.
   c) GRAND PRIZE: most efficient (some sort of formula of score / bytes of
text).

5) Contest submission deadline:
February 28th, or the first instance that we have ten entries AFTER this
date!


Post a reply to this message

From:
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 09:55:18
Message: <mgdg4u44sesc8r1ek6bt5hv2d675o4iqlp@4ax.com>
On Fri, 18 Jan 2002 09:44:34 -0500, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:

Your idea sounds interesting, but ...

>    b) Make it compatible with povray 3.5.

with specification or reality ?
I mean scenes compatible with documentation but not working becouse of bugs or
changes ? For example I can prepare suprehipertransscene but beta from February
could destroy it somehow ...

>    c) no #includes or #reads or #writes or #fopens are permitted.

sure.

>    d) MAX size: 500 bytes (arbitrarily chosen as twice the size of one very
>competent sig file posted to p.g.)
>    e) have it end with //XYZ, where XYZ is a (hopefully) unique 3-digit
> combination of your initials and/or numbers

is //XYZ inside or outside 500 bytes ?

ABX


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 09:57:27
Message: <3c4837d7@news.povray.org>
"W³odzimierz ABX Skiba" <abx### [at] babilonorg> wrote in message
news:mgdg4u44sesc8r1ek6bt5hv2d675o4iqlp@4ax.com...
> On Fri, 18 Jan 2002 09:44:34 -0500, "Greg M. Johnson"
<gregj:-)565### [at] aolcom>
> wrote:
>
> Your idea sounds interesting, but ...
>
> >    b) Make it compatible with povray 3.5.
>
> with specification or reality ?

Comments anyone?

> >    e) have it end with //XYZ, where XYZ is a (hopefully) unique 3-digit
> > combination of your initials and/or numbers
>
> is //XYZ inside or outside 500 bytes ?

//xyz is part of the 500 bytes.


Post a reply to this message

From:
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:15:53
Message: <b3eg4u0dkeatvgk5p28e8qquf4rfim241m@4ax.com>
On Fri, 18 Jan 2002 09:55:40 -0500, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:
> > >    b) Make it compatible with povray 3.5.
> >
> > with specification or reality ?
>
> Comments anyone?

Some examples:
- camera behaviour was changed but documentation not updated yet.
- something with isosurfaces'll change afaik
  (I don't know how changes influence appearance).
- sphere sweeps differ from behaviour described in documentation.
- radiosity has bugs
- splines has bugs
- there are a few of blob bugs
- and many others from Known Bugs lists

There is a chance someone can discover nice 500 bytes long scene unfortunatelly
based on bug (without his knowledge), send it , and next beta can destroy his
effort.

ABX


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:20:29
Message: <slrna4gf9v.6ds.ron.parker@fwi.com>
On Fri, 18 Jan 2002 09:44:34 -0500, Greg M. Johnson wrote:
>     d) MAX size: 500 bytes (arbitrarily chosen as twice the size of one very
> competent sig file posted to p.g.)

sig files already have a max size: 320 bytes.  Any longer and they're not
sig files.  So if you limited participants to, say, 300 bytes (to make up for
word wrap issues) then they'd be making sig files.

Wow!  500 bytes.  Whatever will I do with all that space?

Seriously, though, no theme or anything?  It's easy to come up with an 
attractive-looking pseudo-abstract image in a small number of bytes.  An
image that actually has a point - like "neon" or "uses bicubic patches to
draw letters" or the below-included "spectrum" - is a lot more difficult. 

--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}


Post a reply to this message

From: Jan Walzer
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 10:59:36
Message: <3c484668@news.povray.org>
I think the sourcecodes should also be shown to the pics, to enable the
voters
to judge by "quality" ...


BTW: How 'bout Mutiple Entries per person?


--
[Talking about cardriving]
"People are opstacles?
Oh...I always treat them as bonus points..." [Ian Burgmyer in p.o-t]
// Jan Walzer <jan### [at] lzernet>


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:14:35
Message: <3c4849eb$1@news.povray.org>
"Jan Walzer" <jan### [at] lzernet> wrote in message
news:3c484668@news.povray.org...
> I think the sourcecodes should also be shown to the pics, to enable the
> voters to judge by "quality" ...

Well, that's what makes it all the more interesting.  It's a raw judge of
"quality" without knowing how small.  If some bloke decides to do a fractal,
well maybe that's cool to some, and crap to others.


> BTW: How 'bout Mutiple Entries per person?

2 raised to the power of a relatively small integer.


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:15:43
Message: <3c484a2f$1@news.povray.org>
"W³odzimierz ABX Skiba" <abx### [at] babilonorg> wrote in message
news:b3eg4u0dkeatvgk5p28e8qquf4rfim241m@4ax.com...
> There is a chance someone can discover nice 500 bytes long scene
unfortunatelly
> based on bug (without his knowledge), send it , and next beta can destroy
his
> effort.

Fair enough.  COmments?
Should some just have to face the consequences if they take this risk?


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 11:30:05
Message: <slrna4gjcg.6eq.ron.parker@fwi.com>
On Fri, 18 Jan 2002 09:44:34 -0500, Greg M. Johnson wrote:
>     b) Make it compatible with povray 3.5.

rons_really_cool_signature_file //RLP

Works with the next beta of version 3.5.  Outputs the Mona Lisa.  What do I
win? :)

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 14:18:01
Message: <3c4874e9$1@news.povray.org>
"Ron Parker" <ron### [at] povrayorg> wrote in message
news:slr### [at] fwicom...
> rons_really_cool_signature_file //RLP
>

Judges reserve right to reject entries using features never mentioned in the
docs.


Post a reply to this message

From: Anders K 
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 15:36:17
Message: <3c488741$1@news.povray.org>
> sig files already have a max size: 320 bytes.  Any longer and they're not
> sig files.

According to who? Mine is just over 400 bytes.

Anders

--
light_source{6#local D#macro B(E)#macro A(D)#declare#declare C=mod(E
D);E=(E-C)/D;C#end#while(E)#if(A(8)=7)#declare D=D+2.8;#else#if(C<3)
}cylinder{0(C=<1 2>).2translate<D+C*A(2)A(4)#else}intersection{torus
{1 .2}box{-2y}rotate<1 0C>*90translate<D+1A(2)*2+1#end-2 13>pigment{
rgb x}finish{specular 1}#end#end#end=-8;1B(445000298)B(519053970)B(
483402386)B(1445571258)B(77778740)B(541684549)B(42677491)B(70)}


Post a reply to this message

From: Bill DeWitt
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 15:37:59
Message: <3c4887a7$1@news.povray.org>
"Anders K." <and### [at] prostard2gcom> wrote in message
news:3c488741$1@news.povray.org...
> > sig files already have a max size: 320 bytes.  Any longer and they're
not
> > sig files.
>
> According to who?

    According to the convention of four lines of eighty characters.


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 16:39:18
Message: <3c489606@news.povray.org>
Bill DeWitt <bde### [at] cflrrcom> wrote:
:     According to the convention of four lines of eighty characters.

  In fact, it's better to use well less than 80 characters in order to avoid
line wrapping in quotes (I think that the recommendation is something like
72 characters in a line).

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 16:40:29
Message: <3c48964d@news.povray.org>
Greg M. Johnson <gregj:-)565### [at] aolcom> wrote:
: Judges reserve right to reject entries using features never mentioned in the
: docs.

  I think that technically he has the right to add whatever he likes to
the docs... ;)

-- 
#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: Ron Parker
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 16:54:12
Message: <slrna4h6c7.6q9.ron.parker@fwi.com>
On 18 Jan 2002 16:39:18 -0500, Warp wrote:
> Bill DeWitt <bde### [at] cflrrcom> wrote:
>:     According to the convention of four lines of eighty characters.
> 
>   In fact, it's better to use well less than 80 characters in order to avoid
> line wrapping in quotes (I think that the recommendation is something like
> 72 characters in a line).

Signatures are exempt from that rule, because only lusers quote signatures. :)
Google on McQuary Limit, or see 
http://www.tuxedo.org/~esr/jargon/html/entry/McQuary-limit.html

-- 
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker


Post a reply to this message

From: Bill DeWitt
Subject: Re: Shortest Code Contest
Date: 18 Jan 2002 19:21:58
Message: <3c48bc26@news.povray.org>
"Ron Parker" <ron### [at] povrayorg> wrote :
>
> Signatures are exempt from that rule, because only lusers quote
signatures. :)
>
> plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip
x}rotate
> z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red
1rotate 60
> *z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb
z}text{ttf"arial.ttf"
> "RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron
Parker

    I wonder why that is....


Post a reply to this message

From: Mark James Lewin
Subject: Re: Shortest Code Contest
Date: 20 Jan 2002 20:19:27
Message: <3C4B6839.6BEFE6E7@yahoo.com.au>
Nice idea. 500 bytes is heaps to play with.

"Greg M. Johnson" wrote:

>     c) no #includes or #reads or #writes or #fopens are permitted.

What about using fonts? Should this be limited to those that come with POV?

> 1) An 800 x 600 jpg of your pov file will be prepared.

I assume you will be adding global_settings{assumed_gamma 1} to all the entrants?

MJL

--
text{ttf"timrom.ttf"concat(#local O=1;#while(O<7)chr(val(substr(concat(#local Q=
1;#while(Q<7)str(asc(substr("???<?>",Q,1))-56,0,0),#local Q=Q+1;#end""),O,2))),#
local O=O+2;#end"").1,0pigment{rgb 9}translate-<1,.3,-2>} // MJL


Post a reply to this message

From: Tom Melly
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 09:36:40
Message: <3c4c2778$1@news.povray.org>
"Greg M. Johnson" <gregj:-)565### [at] aolcom> wrote in message
news:3c483541$1@news.povray.org...

<snip>

A couple of ideas coming out of the things others have pointed out...

1. Wait until 3.5 is officially released
2. The file should illustrate a phrase - e.g. "POV 3.5"
3. No fonts or external files of any kind....


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 11:48:32
Message: <3c4c4660$1@news.povray.org>
"Mark James Lewin" <m_j### [at] yahoocomau> wrote in message
news:3C4B6839.6BEFE6E7@yahoo.com.au...
> Nice idea. 500 bytes is heaps to play with.
> "Greg M. Johnson" wrote:
> >     c) no #includes or #reads or #writes or #fopens are permitted.
> What about using fonts? Should this be limited to those that come with
POV?
>

Surely.


> > 1) An 800 x 600 jpg of your pov file will be prepared.
> I assume you will be adding global_settings{assumed_gamma 1} to all the
entrants?
>

I'm really ignorant on this one:  why is it important?


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 11:53:14
Message: <3c4c477a@news.povray.org>
"Tom Melly" <tom### [at] tomandlucouk> wrote in message
news:3c4c2778$1@news.povray.org...
> 1. Wait until 3.5 is officially released
>

Well, is that  a half dozen weeks or a half dozen months??


> 2. The file should illustrate a phrase - e.g. "POV 3.5"

Well, on one hand, the idea is to impress a newbie, (okay, me!).  I think
having it open allows a wide variety of coolness: fractals, landscapes,
etc..  So I'd vote to keep it wide open.


> 3. No fonts or external files of any kind....
>

Okay, is this covered by the requirement of "no includes"?


Post a reply to this message

From: Tom Melly
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 12:22:38
Message: <3c4c4e5e@news.povray.org>
"Greg M. Johnson" <gregj:-)565### [at] aolcom> wrote in message
news:3c4c477a@news.povray.org...
> > 2. The file should illustrate a phrase - e.g. "POV 3.5"
>
> Well, on one hand, the idea is to impress a newbie, (okay, me!).  I think
> having it open allows a wide variety of coolness: fractals, landscapes,
> etc..  So I'd vote to keep it wide open.
>

Yes, but as RP pointed out, it can be too easy to produce a nice, unstructured
abstract with just a few lines of code. Of course, they still have the option of
a nice fractal landscape that somehow spells out "POV 3.5".....


Post a reply to this message

From:
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 12:27:04
Message: <iljo4u0e61u0jdbhb12cr5mrm644l81m0v@4ax.com>
On Mon, 21 Jan 2002 17:22:36 -0000, "Tom Melly" <tom### [at] tomandlucouk> wrote:
> Yes, but as RP pointed out, it can be too easy to produce a nice, unstructured
> abstract with just a few lines of code.

I agree with others - subject most wanted.

> Of course, they still have the option of
> a nice fractal landscape that somehow spells out "POV 3.5".....

Looks possible with modified Warp's sig :-)

ABX


Post a reply to this message

From:
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 12:29:52
Message: <tqjo4uoed3a2pq1dtta9alttu7rt2196qq@4ax.com>
On Mon, 21 Jan 2002 11:52:06 -0500, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:
> Okay, is this covered by the requirement of "no includes"?

"No external/additional files required to render except renderer" ?

ABX


Post a reply to this message

From: Greg M  Johnson
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 13:12:18
Message: <3c4c5a02$1@news.povray.org>
"Tom Melly" <tom### [at] tomandlucouk> wrote in message
news:3c4c4e5e@news.povray.org...
> Yes, but as RP pointed out, it can be too easy to produce a nice,
unstructured
> abstract with just a few lines of code. Of course, they still have the
option of
> a nice fractal landscape that somehow spells out "POV 3.5".....
>

Hence, have judging so that people will pick out the coolest/best/ most
innovative.
Yet, wide open, so that people can see all the wild things that ARE
possible.  If it's limited to text, really why bother at all?

(IMHO, yes povray's strengths do include the ability to make photorealistic
renders from Poser, and super-advanced DXF modellers. BUT if I were to see a
box of povray in the store, and what I saw was exacting detail of the Taj
Mahal and a note that said that image required 100Mb of meshes, I'd be
ho-hum, next freeware please.   Seeing the VARIETY of what a genius can do
with a few lines is better, IMHO).


BTW:  I'm just one opinionated dork.  If someone more popular wants to
officially host it, by all means...


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 15:59:59
Message: <3c4c814e@news.povray.org>
W³odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
:> Of course, they still have the option of
:> a nice fractal landscape that somehow spells out "POV 3.5".....

: Looks possible with modified Warp's sig :-)

  Have you rendered fractals3.pov in scenes\textures\patterns? It's half of
that.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 16:01:11
Message: <3c4c8197@news.povray.org>
Tom Melly <tom### [at] tomandlucouk> wrote:
: 1. Wait until 3.5 is officially released

  As he said: Do we have to wait a half year for this comp? *yawn*

: 2. The file should illustrate a phrase - e.g. "POV 3.5"

  IMO this limits creativity just too much.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 17:06:50
Message: <slrna4p47s.fcq.ron.parker@fwi.com>
On Mon, 21 Jan 2002 11:52:06 -0500, Greg M. Johnson wrote:
> "Tom Melly" <tom### [at] tomandlucouk> wrote in message
> news:3c4c2778$1@news.povray.org...
>> 1. Wait until 3.5 is officially released
>>
> 
> Well, is that  a half dozen weeks or a half dozen months??

"yes"

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}


Post a reply to this message

From: Ron Parker
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 17:08:10
Message: <slrna4p4ae.fcq.ron.parker@fwi.com>
On Mon, 21 Jan 2002 13:11:10 -0500, Greg M. Johnson wrote:
> Yet, wide open, so that people can see all the wild things that ARE
> possible.  If it's limited to text, really why bother at all?

I wouldn't say text is really a limitation.  Look at the various ways I've
found to express a couple characters.  Look at Warp's sig.

-- 
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker


Post a reply to this message

From: Mark James Lewin
Subject: Re: Shortest Code Contest
Date: 21 Jan 2002 17:59:56
Message: <3C4C990F.1B6426E1@yahoo.com.au>
With regard to fonts, etc., perhaps you should repost some rules to clarify this
issue. Ditto for subject matter (if this is to be set).

>
>
> > > 1) An 800 x 600 jpg of your pov file will be prepared.
> > I assume you will be adding global_settings{assumed_gamma 1} to all the
> entrants?
> >
>
> I'm really ignorant on this one:  why is it important?

To ensure all entrants are rendered with the gamma intended by the entrant.

MJL

--
prism{0,.1,30#local I=1;#while(I<30)#local B=asc(substr(// Mark James Lewin
"#K?U_u`V[RG>3<9DGPL.0EObkcPF'",I,1))-33;<div(B,10)-4mod(B,10)+5*div(I,21)-
6>#local I=I+1;#end,-4pigment{rgb 9}rotate-x*90translate 15*z}//POV-Ray 3.5


Post a reply to this message

From:
Subject: Re: Shortest Code Contest
Date: 22 Jan 2002 03:08:15
Message: <d77q4us5if7igodfvgkpu60iafrjskjhbg@4ax.com>
On 21 Jan 2002 16:01:11 -0500, Warp <war### [at] tagpovrayorg> wrote:
> > 2. The file should illustrate a phrase - e.g. "POV 3.5"
>  IMO this limits creativity just too much.

What about 'jungle', 'kitchen', 'sea' or 'worlds within worlds' topics ? :-)

ABX


Post a reply to this message

From: Warp
Subject: Re: Shortest Code Contest
Date: 22 Jan 2002 06:09:42
Message: <3c4d4876@news.povray.org>
W³odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
: What about 'jungle', 'kitchen', 'sea' or 'worlds within worlds' topics ? :-)

  Only if it becomes a regular competition.
  IMO the first one should be free, to see what people can do.

-- 
#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: Tom Melly
Subject: Re: Shortest Code Contest
Date: 22 Jan 2002 06:47:25
Message: <3c4d514d$1@news.povray.org>
"Warp" <war### [at] tagpovrayorg> wrote in message news:3c4d4876@news.povray.org...
>   Only if it becomes a regular competition.
>   IMO the first one should be free, to see what people can do.
>

I think that they meant that having a topic wasn't necesserily a limitation....


Post a reply to this message

From: Peter J  Holzer
Subject: Re: Shortest Code Contest
Date: 22 Jan 2002 16:01:57
Message: <slrna4rhp0.lvg.hjp-usenet@teal.h.hjp.at>
On 2002-01-21 22:06, Ron Parker <ron### [at] povrayorg> wrote:
> On Mon, 21 Jan 2002 11:52:06 -0500, Greg M. Johnson wrote:
>> "Tom Melly" <tom### [at] tomandlucouk> wrote in message
>> news:3c4c2778$1@news.povray.org...
>>> 1. Wait until 3.5 is officially released
>>>
>> 
>> Well, is that  a half dozen weeks or a half dozen months??
> 
> "yes"

I bet against it :-)

	hp

-- 
   _  | Peter J. Holzer    | Hört doch dieses törichtes Volk ohne
|_|_) | Sysadmin WSR       | Verstand, die Augen haben und nicht sehen,
| |   | hjp### [at] hjpat         | die Ohren haben und nicht hören!
__/   | http://www.hjp.at/ |    -- Jeremia 5:21


Post a reply to this message

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