 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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...
--
From the Grey Knight
//@---signature---
// Grey Knight's site of the week:
url{ "http://mathworld.wolfram.com" }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oh yes,
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.
4: Support for matrix operations would be nice, although I'm writing a
series of macros to handle matrices at the min. Ho hum.
s1631001 wrote:
>
> 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...
>
> --
> From the Grey Knight
> //@---signature---
> // Grey Knight's site of the week:
> url{ "http://mathworld.wolfram.com" }
--
From the Grey Knight
//@---signature---
// Grey Knight's site of the week:
url{ "http://mathworld.wolfram.com" }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
s1631001 wrote: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.
In the meantime, you might want to search back in povray.binaries.utilities
for a copy of POVGUI 1.5, which is a set of includes and macros that emulate
Moray-style modeling with a set of wireframe objects and gridded views(
front, side, top, perspective as well as render). Plane, sphere, cylinder,
cone, box, text (sort of), lathe, prism, height_field (both types) and
super-q are supported. Some of these ideas could probably make their way
into a patch of some sort.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 27 Nov 2001 14:01:12 +0000, s1631001 <s16### [at] namtar qubacuk> wrote:
> 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?
Do you know #include and #declare directive ?
You can build own script (include- file) with favourite constants and use it
with POV 3.1.
> 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.
Typical answer is "POVRay is raytracer not modeler" however there are some
useful macro to work with wireframes. With POV's Scene Description Language you
can even write own. Available in POV 3.1.
> 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.
Is it very important ? If "yes" are names of this files regular ? Perhaps you
can delet it with Post_Scene_Command ? It is ini-setting available in POV 3.1
> 4: Support for matrix operations would be nice, although I'm writing a
> series of macros to handle matrices at the min. Ho hum.
Are you thinking about matrices with transformations ? You can store them as
transform{} and always get its elements with macro described lately in advenced
group on this news server. Works with POV 3.1.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
s1631001 <s16### [at] namtarqubacuk> wrote:
: 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.
Not possible.
http://www.students.tut.fi/~warp/povVFAQ/languageVFAQ.html#wireframes
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> s1631001 <s16### [at] namtarqubacuk> wrote:
> : 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.
>
> Not possible.
I'll go along with the polygons part, Warp, but since POVGUI works, and pretty
darn well, I'd have to say that wireframes inside POV-Ray, per say, are not
impossible. The difference, of course, is that the wireframes are constructed
by parameters fed into macros out of other object types. I have always said it
is wireframe emulation, but the results you see on the screen are the same.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C03CC1F.6CD7F23F@aol.com> , Dave Dunn <poi### [at] aolcom>
wrote:
> I'll go along with the polygons part, Warp, but since POVGUI works, and pretty
> darn well, I'd have to say that wireframes inside POV-Ray, per say, are not
> impossible. The difference, of course, is that the wireframes are constructed
> by parameters fed into macros out of other object types. I have always said it
> is wireframe emulation, but the results you see on the screen are the same.
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.
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> : A Moray-style preview...
> Not possible.
If a moray-style preview is not possible, then how does moray do it?
;)
--
Tim Cook
http://empyrean.scifi-fantasy.com
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Timothy R. Cook <tim### [at] scifi-fantasycom> wrote:
: If a moray-style preview is not possible, then how does moray do it?
: ;)
Moray does not read a pov-file. Moray supports a rather limited set of
primitives.
In theory you could generate a wireframe with a given resolution from many
povray primitives, and even when in CSG (I think there are algorithms for
calculating the CSG of triangle meshes). However, this becomes difficult to
do with certain objects. For example tesselating a 4D-Julia, a poly or an
isosurface is not that simple (specially the poly object can be difficult as
it can be an infinite surface, which is impossible to tesselate completely).
If you start tesselating those things, the tesselation takes time (it can
take even a surprisingly long time depending on the wanted accuracy). This
starts to raise the question of whether it's worth the efforts, as a +Q0
raytrace might not take longer than that.
Moray doesn't have to worry about those because it doesn't support them.
If it supported them, I suppose that it would just show them as boxes.
--
#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
|
|
| |
| |
|
|
|
|
| |
|
|
