 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gleb <gk1### [at] soton acuk> wrote in message news:3c83c338@news.povray.org...
> Have you used splines(and if so, what kind) for it?
I used the natural spline in the #declare spline function to trace to top
and bottom curves. The piece has to fit perfectly with several other pieces,
so this allows a perfect fit through the control points.
-Shay
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I attached a piece of wire frame to show what I'm talking about.
This really shows what you've done.. great work.. :o)
> I wrote a macro that takes an n-by-n array (mesh_array[columns][rows]) and
> writes out a #mesh2 macro with normals. If this would help with your
> heightfield work, I would be glad to clean it up and send it to you
tonight.
> Let me know.
I too have attached a picture that hopefully demonstrates what I'm doing..
It's a heightfield (a bit boring one) traced within POV.. The idea is that
people can use my macros as modelling tools.. People may use well-known and
easy primitives to make a shape.. My macro will then transform it to a
heightfield, and another macro will smooth out the vertices (remove hard
edges that primitives usually have) and a third macro sweeps the grid around
a lathe, spline, etc.. It will be easy to put in a forth or fifth macro,
with other deformation features.
Each square in the grid consist of 2 triangles. As shown with yellow and
blue lines, these "qaud faces" (double faces) are connected in either one
way - the way that suits the curvature best.. Ordinary HF's don't seem to
have this feature, but it improves the shape when there's not a lot of
triangles.
My problem is to average the normals in this "matrix".. Each vertex is
surrounded by 4 squares, and each square consist of 2 triangles, but
sometimes only 1 of them should be averaged because only 1 of them are
directly connected to the vertex.. It's no problem to store this pattern in
an array with either 0 or 1.. But I battle to get this averaging to work
correctly.. Buggy code and it may sound rediculous.. But I'd like to get it
working.
Your code does not take this swapping of quad-faces into consideration, so
it won't solve my problem. :o) But thanks for your offer, anyway! I don't
know if you could use my long explanation to anything, I tried to be
concise, and anyone is welcome to take a look at my code, of course.
Regards,
Hugo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I too have attached a picture
Forgot the picture.
Post a reply to this message
Attachments:
Download 'Hf_example.JPG' (19 KB)
Preview of image 'Hf_example.JPG'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I see now what you are doing. This will be very useful for animation where
the goal is to use as few triangles as possible.
I have an idea for how to adapt my macro for what you are doing. I think
that the best way to do this would be to store the normals in a
3-dimentional array (Normal_Array[Columns][Rows][8]). Then, write two
macros, one for each case of division. Each of the two macros will figure
the normal of each triangle as it is made and then file that normal with
each of the vertices of the triangle.
The normal of each vertex could then later be found with something like
this:
#declare Triangle_Normal_Sum = 0;
#declare Counter = 0;
#while (Counter < 8)
#ifdef ( Normal_Array[Column][Row][Counter] )
#declare Triangle_Normal_Sum = Triangle_Normal_Sum +
Normal_Array[Column][Row][Counter];
#end // #ifdef ( Normal_Array[Column][Row][Counter] )
#declare Counter = Counter + 1;
#end // #while (Counter < 8)
#declare Vertex_Normal = vnormalize {Triangle_Normal_Sum}
I think I will try to test this tonight. Let me know if I understood
corectly what you are trying to do.
-Shay
Hugo <hua### [at] post3teledk> wrote in message news:3c83ef1f@news.povray.org...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Better idea. Just make an array (Normal_Array[Columns][Rows][1]) and set
every value to <0,0,0>. Then, keep adding normals to the <0,0,0> when
appropriate. This will make the macro adaptable to more meshes.
-Shay
Shay <sah### [at] simcopartscom> wrote in message
news:3c83f484$1@news.povray.org...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The modelling is great, if you understand modelling as
creating any object. For me modelling is also creating
a model of something. Hence the question what it is,
just to know what to compare it with. So my verdict:
technical achievement: 9.5
artistic merit: 7
conformity to real object: NA
conversation piece: 8.5
Is that what you wanted to hear? More serious: for some
obscure reason I am interested in working with patches,
their scaling properties, connecting different patches
together, etc. An object like this could be an interesting
object to test what to achieve with patches for me, except
that I do not have a reference, other than your image :)
Andrel
Shay wrote:
>
> Clever ideas, guys, but what did you think of the modeling?
>
> Rick [Kitty5] <ric### [at] kitty5com> wrote in message
> news:3c834ea9$1@news.povray.org...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Let me know if I understood
> corectly what you are trying to do.
Yes you have. :o)
> Better idea. Just make an array (Normal_Array[Columns][Rows][1]) and set
> every value to <0,0,0>. Then, keep adding normals to the <0,0,0> when
> appropriate. This will make the macro adaptable to more meshes.
Yes, true.. I will clean up my code cause I keep getting confused, but it
should be possible that it just calls your macro once for each grid - then
ends with the final normals to each vertex.
I'll be back tomorrow.
:o)
Hugo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rick and oliWood posted this, but I guess I need to confirm it. This is the
bottom of a Dalek.
Really it isn't even that because I am redesigning the Dalek to my own
tastes. The dimentions are identical, however.
I have attached a picture of a Dalek for any who are unfamiliar with it and
a second picture of my model which shows how snugly the spheres (Not sure
what to do with those yet) will fit into my model. This is partly a product
of my imagination, but it is still very precise.
-Shay
Post a reply to this message
Attachments:
Download 'dalek-1j.jpg' (19 KB)
Download 'Dal_Bodyj.jpg' (27 KB)
Preview of image 'dalek-1j.jpg'
Preview of image 'Dal_Bodyj.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Is a darlek a female dalek? I guess that's why it's full of holes...
proper interfacing.
Cheers!
Chip Shults
My robotics, space and CGI web page - http://home.cfl.rr.com/aichip
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Rick and oliWood posted this, but I guess I need to confirm it. This is
the
> bottom of a Dalek.
:)
--
Rick
Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
