In article <3c0cf1f2.12037077@news.povray.org> , ken### [at] uniplanit (Angelo 
'kENpEX' Pesce) wrote:

> I'm not suggesting to stop that at all... Just if U have a system
> without dynamic plugin support you'll have to recompile povray with
> every plugin you need and then you can render every scene you want.
> This is what povray *ACTUALLY* does, so using plugins will only
> improve povray usability for some plattforms, but not penalize the
> others, as for the others the system will remain the same (of course
> there should be a way to compile a "plugin" as a plugin or not without
> modifing its source...)

I am not aware of any POV-Ray "plug-ins" at all, be they dynamically or
statically linked.  Maybe one of us is on the wrong planet.  I am sure it
isn't me, so it must be you.

Anyway, looking back at my first reply, "Looks like you have a few
misconceptions about POV-Ray (or are looking for a flame war).", I have to
correct myself.  I should have asked "Why are you looking for a flame war?"!

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Tue, 04 Dec 2001 17:29:45 +0100, Christoph Hormann
<chr### [at] gmxde> wrote:

>
>
>Angelo 'kENpEX' Pesce wrote:
>> 
>> mhm mabye I can't remember well because I've read maaaaany msgs in
>> those days (I'm a newbie of this ng and this is clear as many ppl
>> think that i'm just another lamer, it seems).
>
>Although i think nearly everyone who answered your postings was quite
>friendly
I think so too

> it would probably be a good idea to read some of the previous
>discussions on these subjects, a lot of the things you mentioned are also
>covered somehow in Warp's VFAQ:
>http://www.students.tut.fi/~warp/povVFAQ/
mhm... I've read that

>And i think it would be good to simply accept the fact that there won't be
>new features introduced that only work on a few platforms, no matter if
>these cover 90% of the users or not.  Same probably applies for algorithms
>that require tesselation of objects.
well if that's the point, I accept it. I accept every decision of
povray team, mabye I don't agree, but as I'm not a povray developer, I
can only accept it... I'm just telling what I think, it many other ppl
think that I'm right, mabye the povteam will change its mind... That's
what a ng is for I think

Post a reply to this message

On 4 Dec 2001 10:50:59 -0500, Warp <war### [at] tagpovrayorg> wrote:

>Angelo 'kENpEX' Pesce <ken### [at] uniplanit> wrote:
>: Most of povray images
>: (see IRTC etc...) have a bad aliasing (imho) because of povray is
>: still slow (if compared to stuff like lightflow or mentalray or other
>: renderers)...
>
>  I don't understand how speed affects antialiasing quality. You speak like
>a faster program would make a better antialiasing.
>  Of course a smaller antialiasing threshold takes longer to render, but the
>result will be identical independently of how fast the program or the
>computer is.
>  If you had said "a faster program allows you to use a higher quality
>antialiasing in the same render time", that would have been more accurate.
>  And besides, I don't remember seeing many images with crappy antialiasing
>in the IRTC.
If your time limit is +inf, then speed is not equal to quality. Other
wise it is. But usually when I talk I'm thinking of real world, not of
every other thing.

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

Post a reply to this message

On Tue, 04 Dec 2001 17:21:55 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <3c0cc693.932849@news.povray.org> , ken### [at] uniplanit (Angelo 
>'kENpEX' Pesce) wrote:
>
>> if compared to stuff like lightflow or mentalray or other renderers
>
>Remind me, what did Softimage with Mental Ray cost again?  About as much as
>a mid-sized car?  Or was is a Mercedes?
Lightflow is free for non commercial use and imho it's better than
mentalray or lightwave 6 renderer. Someone thing that free stuff
should be worse than commercial stuff, some others not... Btw
softimage costs about as much a mid-sized car, or a small mercedes :P

Post a reply to this message

On Tue, 04 Dec 2001 17:39:54 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <3c0cf075.11656238@news.povray.org> , ken### [at] uniplanit (Angelo 
>'kENpEX' Pesce) wrote:
>
>> Like java class files do? IEE754 format? Using 128bit fixedpoint math?
>
>And then just do a fread?  Try it, and you will be very surprised.  Or look
>into the JVM source code and see how easy it is...
Of course not...

Post a reply to this message

On Tue, 04 Dec 2001 17:44:52 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <3c0cf1f2.12037077@news.povray.org> , ken### [at] uniplanit (Angelo 
>'kENpEX' Pesce) wrote:
>
>> I'm not suggesting to stop that at all... Just if U have a system
>> without dynamic plugin support you'll have to recompile povray with
>> every plugin you need and then you can render every scene you want.
>> This is what povray *ACTUALLY* does, so using plugins will only
>> improve povray usability for some plattforms, but not penalize the
>> others, as for the others the system will remain the same (of course
>> there should be a way to compile a "plugin" as a plugin or not without
>> modifing its source...)
>
>I am not aware of any POV-Ray "plug-ins" at all, be they dynamically or
>statically linked.  Maybe one of us is on the wrong planet.  I am sure it
>isn't me, so it must be you.
Of course you are not aware of them... This is only because it was a
feature proposal... As U can see the topic of my original post was
"Povray 4? wish list" and in the message that U've quoted I was
answering a question about them

Post a reply to this message

<SNIP>

> Nope. What I was trying to say is that it's wiser to concentrate into
> optimizing a renderer than into adding more complex features. For
> example, radiosity,caustics,diffraction,etc etc... are complex topics
> that require hard work, but they are not really useful as they
> influence just a small number of images. Photorealistic renderman is
> not a raytracer, it doesn't have correct reflections as it uses

<SNIP>

No, more features please!!!!!! the render time is something that will be solved
automatically be new computers, it is easier and cheaper to buy a new machine every
so often then it is to change the source code each time. although network support
would be nice ofcourse :)


Thomas

ps. And remember even assembler might perform VERY bad on different processors of
the same family. Just look at RC5 on RS-64III

Post a reply to this message

> Lightflow is free for non commercial use and imho it's better than
> mentalray or lightwave 6 renderer. Someone thing that free stuff
> should be worse than commercial stuff, some others not... Btw
> softimage costs about as much a mid-sized car, or a small mercedes :P

And have you ever tried the python interface to Lightflow? it is a bit crappy
compared to POV's. Yes you can do some stuff pov can't, but some stuff is very
complicated in it.

Thomas

Post a reply to this message

>  Or look into the JVM source code and see how easy it is...

hmmmmm I might take you on to that, the guys are sitting right upstairs here ;)



Thomas

Post a reply to this message

On Tue, 04 Dec 2001 17:11:21 +0000, Thomas <tho### [at] gmxnet> wrote:
> And have you ever tried the python interface to Lightflow? it is a bit crappy
> compared to POV's. Yes you can do some stuff pov can't

IIRC Warp waits for chellenge :-)

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message