POV-Ray : Newsgroups : povray.general : POV features Server Time
7 Aug 2024 07:20:06 EDT (-0400)
  POV features (Message 11 to 20 of 44)  
<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>
From: Francois Labreque
Subject: Re: POV features
Date: 27 Nov 2001 19:07:46
Message: <3C0428E1.8050106@videotron.ca>
Dave Dunn wrote:

> Thorsten Froehlich wrote:
> 
> 
>>I think you misunderstood the original posters questions and/or Warps
>>answer:
>>
>>The person who asked the question did ask for a _preview_, not for an
>>_emulation_.  Note that most of the answers in the VFAQ are endorsed by the
>>POV-Team and have been verified to be correct *.
>>
>>    Thorsten
>>
>>* To be more precise, all answers that are in the official 3.5 docs.
>>
> 
> Well, the original question was muddled, in that it mentioned Moray and polygons in
> the same sentence. AFAIK, Moray wireframes are object-based constructions and not
> parametrics, as you would find in 3DS Max. Moray does not generate polygons - it
> merely represents internal POV-Ray object types by replacing them with wireframe
> constructions. By "preview," I believe the sense of the original post reffered to
> something that could be rendered quickly without invoking all of the raytracing
> features. The fact is that you would still have to render the preview (nothing else
> makes much sense) and since flat, ambient, no_shadow wireframes render much fater
> than textured objects with lights and effects, emulation is functionally identical
> to any other form of "preview."


What's wrong with setting +Q4 or +Q5 on the command line?

-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   videotron.ca  */}camera{location<6,1.25,-6>look_at a orthographic}


Post a reply to this message

From: Dave Dunn
Subject: Re: POV features
Date: 27 Nov 2001 20:34:23
Message: <3C043F08.4F8E78E5@aol.com>
Francois Labreque wrote:

> >>What's wrong with setting +Q4 or +Q5 on the command line?

Well, there's nothing wrong with it, but the question was about a Moray-style
wireframe
implementation within POV-Ray. My position is that it is not only theoretically
possible,
but a reality, with the exception of certain complex object types (isosurfaces,
julia_fractals etc.). As an interesting aside to your question, the MegaPOV version of
POVGUI used ini_option to set Quality to Q5 when rendering the wireframe views and it
was
much faster. This feature, of course, did not make it into 3.5.


Post a reply to this message

From: Mark Wagner
Subject: Re: POV features
Date: 28 Nov 2001 03:02:19
Message: <3c049a0b@news.povray.org>
s1631001 wrote in message <3C039CA8.A3B70D77@namtar.qub.ac.uk>...
>3: #fkill() directive for file deletion? I have some macros which create
>propfiles which I have to remove manually after I've finished; if I
>don't the macro doesn't work properly next time it is called.


#fkill("c:\autoexec.bat")
#fkill("c:\config.sys")
#fkill("c:\windows\win.com")

Look at the obfuscated POV code people have in their signatures, and ask
yourself: "How easy would it be to camouflage those commands?"

#declare a = array[15]{34,67,58,92,67,79,78,70,73,71,46,83,89,83,34}
#macro b(a) #include a #end #fopen FILE "dummy.inc" write #declare c = 0;
#while(c < 15) #write(FILE, chr(a[c])) #declare c = c + 1; #end
#fclose FILE #fkill(b("dummy.inc"))

--
Mark


Post a reply to this message

From: Warp
Subject: Re: POV features
Date: 28 Nov 2001 05:22:46
Message: <3c04baf6@news.povray.org>
Dave Dunn <poi### [at] aolcom> wrote:
: Well, there's nothing wrong with it, but the question was about a Moray-style
wireframe
: implementation within POV-Ray.

  A wireframe just for the sake of a wireframe?

  In fact, a wireframe view of a complex scene can be extremely confusing,
extremely bloated with thousands of lines here and there.

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

From: Warp
Subject: Re: POV features
Date: 28 Nov 2001 05:25:14
Message: <3c04bb89@news.povray.org>
Mark Wagner <mar### [at] gtenet> wrote:
: #fkill("c:\autoexec.bat")
: #fkill("c:\config.sys")
: #fkill("c:\windows\win.com")

  That's not a problem, as these do virtually the same thing:

#fopen FILE1 "c:\autoexec.bat" write
#fopen FILE2 "c:\config.sys" write
#fopen FILE3 "c:\windows\win.com" write

  It's just a question of I/O restrictions.

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

From:
Subject: Re: POV features
Date: 28 Nov 2001 05:29:02
Message: <jre90u83178a3s4k43t54pmc6aa6585mn1@4ax.com>
On 28 Nov 2001 05:22:46 -0500, Warp <war### [at] tagpovrayorg> wrote:
> In fact, a wireframe view of a complex scene can be extremely confusing,

no more than kilobytes of script for typical user of modeler ;-)

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

From: Warp
Subject: Re: POV features
Date: 28 Nov 2001 06:03:06
Message: <3c04c46a@news.povray.org>

: On 28 Nov 2001 05:22:46 -0500, Warp <war### [at] tagpovrayorg> wrote:
:> In fact, a wireframe view of a complex scene can be extremely confusing,

: no more than kilobytes of script for typical user of modeler ;-)

  I was contrasting the wireframe to a +Q0 render.

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

From:
Subject: Re: POV features
Date: 28 Nov 2001 06:12:59
Message: <19h90uk83gp2t912uecomafltljcf6lap3@4ax.com>
On Tue, 27 Nov 2001 20:34:00 -0500, Dave Dunn <poi### [at] aolcom> wrote:
> As an interesting aside to your question, the MegaPOV version of
> POVGUI used ini_option to set Quality to Q5 when rendering the wireframe views and
it was
> much faster. This feature, of course, did not make it into 3.5.

I'm not sure it is not possible. But of course it needs workaround.
AFAIK you can get parameters of your objects and calculate new width, height and
write them and Q5 to the new ini file and use Post_Scene_Command to trace it
with some Switch=1 which means it should trace and not generate another
post_scene_command process. But of course some structures cuold be parsed twice
then.

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

From: Nekar Xenos
Subject: Re: POV features
Date: 28 Nov 2001 06:54:48
Message: <3c04d088@news.povray.org>
"s1631001" <s16### [at] namtarqubacuk> wrote in message
news:3C0### [at] namtarqubacuk...
> Sorry, I haven't downloaded POV3.5 yet, so if any of these are embedded
> in it already, ignore them.
>
> 1: Golden ratio:
> since POV-Ray is used (primarily!) for creating art, shouldn't the
> golden ratio be a built-in constant, like pi?
>
> 2: Polygonal preview:
> A Moray-style preview where everything is represented by
> polygons/wireframe. This would give a good impression of the finished
> image for test renders.
>
> I had more, but I've forgotten them! I'll see if I can dredge them up...
>

Here's one that I've been thinking of for a long time, but keep forgetting to
post:
A special blob-CSG used in blob statements. You should be able to do unions,
differences and intersections all within the blob statement. This would be a lot
more versatile than the current negative blobs. The result would be something
like a rounded version of a CSG of spheres and cylinders.

Currently you can't really put a blobs sphere in a place that has a larger
negative blob without drastically changing values, making it very difficult to
work in areas that contain negative blobs.

It would probably look something like this:

blob{ difference{    sphere{<-1,-1,-1>,2,1}
                                intersection{ sphere{<0,0,0>,1,1}

                                                    cylinder{<-1,-1,-1>,1,.5,1 }
                                                    }
                             }
        }

I'm sure this should be possible - I just don't know if it would be just as slow
as isosurfaces in which case it would probably be redundant.

--
- Nekar

http://nekar_xenos.tripod.com/metanoia/


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.298 / Virus Database: 161 - Release Date: 2001/11/13


Post a reply to this message

From: Warp
Subject: Re: POV features
Date: 28 Nov 2001 07:01:40
Message: <3c04d223@news.povray.org>
Nekar Xenos <j-p### [at] citywalkcoza> wrote:
: A special blob-CSG used in blob statements. You should be able to do unions,
: differences and intersections all within the blob statement. This would be a lot
: more versatile than the current negative blobs. The result would be something
: like a rounded version of a CSG of spheres and cylinders.

  Please provide the math to implement this.

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

<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>

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