On Thu, 31 Jan 2002 08:54:20 +0100, Apache wrote:
> Well, what about obfuscated (rendered unreadable) povscripting?

What do you call the stuff we've all been putting in our .signatures?

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

I don't see any fun at all in the concept, unless I misunderstand the
concept.

"Apache" <apa### [at] yahoocom> wrote in message
news:3c58f4ad@news.povray.org...
> Well, what about obfuscated (rendered unreadable) povscripting?
>
>

Post a reply to this message

Greg M. Johnson <gregj:-)565### [at] aolcom> wrote:
: I don't see any fun at all in the concept, unless I misunderstand the
: concept.

  Well, it's a field of competition which many people find funny. The
Obfuscated C Code Contest and the Obfuscated Perl Code Contest are classics.

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

How much time will be allowed for the rendering computer to complete
entries?

I have a friend who started one on his overclocked Athlon 1900+ running at
2.6Ghz and it only got 27% done in 24hrs.

N Shomber

Post a reply to this message

Well, that is a potential problem.
If you have something like that, make it clear in the email submission and
we can see if we can find someone with the resources to render it...

"N Shomber" <nsh### [at] hotmailcom> wrote in message
news:3c5f29e5@news.povray.org...
> How much time will be allowed for the rendering computer to complete
> entries?
>
> I have a friend who started one on his overclocked Athlon 1900+ running at
> 2.6Ghz and it only got 27% done in 24hrs.
>
> N Shomber
>
>

Post a reply to this message

By the way, what rendering settings will you be using? You have said just
the resolution but not, for example, the antialiasing settings.

  IMHO best antialiasing speed/quality tradeoff is got with "+a +am2" (for
even more quality use "+a0.1 +am2").
  Yes, it makes the rendering slower than with a plain "+a", but I think that
the resulting quality is worth it (in many images you can't see but really
subtle differences, but in some images it really makes a big difference!).

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

By the way, I really hope that you are *not* rendering my entries
with assumed_gamma 1 (as someone suggested) because they look just
plain *horrible* with that setting.

-- 
#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 17 Feb 2002 11:50:35 -0500, Warp <war### [at] tagpovrayorg> wrote:
>  By the way, I really hope that you are *not* rendering my entries
> with assumed_gamma 1 (as someone suggested) because they look just
> plain *horrible* with that setting.

The way how I support my entries is that I post two text files as rules
describes and gives url inside description file with rendered image of my
entries to verify appearance of it. Some render times are long so preview
allows to avoid mistakes at begining.

ABX

Post a reply to this message

Well,
i)    My philosophy is to go with the default settings on the program, as to
impress folks with the granduer possible with--cough-- 500 bytes...  If you
urgently need another gamma, shouldn't that be part of your code?  Your last
statement involved a bunch of +switches which are completely greek to me.
If a dull 3-year windows user cannot do it, a sharp windows newbie user--the
target audience to impress here-- might find it equally intimidating.
ii)   I never promised different tweakings for every different entry when
that discussion came up--- iirc I stated I was leaning against it.
iii)  Yours don't look that terrible.
iv)  I'll promise a week or two of extra recoding time for anyone seriously
injured by this.
v)   We can still talk about this....

Post a reply to this message

Greg M. Johnson <gregj:-)565### [at] aolcom> wrote:
: i)    My philosophy is to go with the default settings on the program, as to
: impress folks with the granduer possible with--cough-- 500 bytes...  If you
: urgently need another gamma, shouldn't that be part of your code?  Your last
: statement involved a bunch of +switches which are completely greek to me.

  No. What I meant is that my entries look best with POV-Ray's default
settings. However, someone suggested that you would use assumed_gamma 1 when
rendering the entries. I tried it with mine and they looked horrible.
  It's just that I don't remember you writing clearly "no, I will *not* use
anything else than the default settings when rendering the entries" and so
I wasn't sure if you would do that or not.

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