 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello all. I found this great (or so I think) page that explains how to
model all kinds of real world events; string, cloth, gel, spherical
heighfields, fire, water, wu particles, etc. etc. I wanted to translate
the pseudo code to POV, but I found myself unable to do so. I kinda
wanted to surprise everybody with, I dunno, maybe a macro or something
for cloth and string at least. I am submitting the link for all those
advanced enough to actually make something out of this, unlike me.
Enjoy. =)
http://freespace.virgin.net/hugo.elias/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Anthony!
This linke is very useful. I searched for a link like this!
Thanks!
Marc
--
Marc Schimmler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Anthony Bennett schrieb in Nachricht
<36D1DBBE.EE209389@panama.phoenix.net>...
>Hello all. I found this great (or so I think) page that explains how to
>model all kinds of real world events; string, cloth, gel, spherical
>heighfields, fire, water, wu particles, etc. etc.
I've been browsing this. Good tutorials and examples. You can even download
them as zip files. Very good indeed. Translating the pseudo code to POV
script would be a bit harder though. Would better fit in a patch or two
(cloth, gel, etc.).
--
Rudy Velthuis
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> This linke is very useful. I searched for a link like this!
>
> Thanks!
I'm glad I could help, Marc. =)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I've been browsing this. Good tutorials and examples. You can even download
> them as zip files. Very good indeed. Translating the pseudo code to POV
> script would be a bit harder though. Would better fit in a patch or two
> (cloth, gel, etc.).
>
I think that the Inverse Kinematics could be converted into a macro (I have no
idea how, I just guess that it could). A patch with these things would be
extremely cool. The spherical heightfields would be interesting too.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Anthony Bennett wrote:
>
> > I've been browsing this. Good tutorials and examples. You can even download
> > them as zip files. Very good indeed. Translating the pseudo code to POV
> > script would be a bit harder though. Would better fit in a patch or two
> > (cloth, gel, etc.).
> >
>
> I think that the Inverse Kinematics could be converted into a macro (I have no
> idea how, I just guess that it could). A patch with these things would be
> extremely cool. The spherical heightfields would be interesting too.
Putting IK into a macro, and a great many other things, are currently
inefficient in POVRay w/ animations as for each you need to recalculate
everything from the start of the animation. Does anyone know of a patch (or is
someone interested in making one) where you can have global variables, that hold
their value from frame to frame?
--
Sam
mailto:smi### [at] paradise netnz
http://www.geocities.com/SiliconValley/Horizon/4152/
"Someday we'll look back on this moment and plow into a parked car."
-- Evan Davis
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The Crazy Mule <smi### [at] paradisenetnz> writes:
> Anthony Bennett wrote:
>
> Putting IK into a macro, and a great many other things, are currently
> inefficient in POVRay w/ animations as for each you need to recalculate
> everything from the start of the animation. Does anyone know of a patch
> (or is someone interested in making one) where you can have global
> variables, that hold their value from frame to frame?
How about writing them to a file with the new #read and #write directives?
There is also a new clock_delta constant. In my opinion, this should be
all that you need. (No, I don't have the time to try to write such macros.)
Thomas
--
http://www.fmi.uni-konstanz.de/~willhalm
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas Willhalm wrote:
>
>How about writing them to a file with the new #read and #write directives?
>There is also a new clock_delta constant. In my opinion, this should be
>all that you need. (No, I don't have the time to try to write such macros.)
>
This would be plausible, if these directives were a bit more configurable.
Right now #read just reads a number of params from the start, you can't
specify an offset to the read. This severely limits its possibilities.
Believe me, I've tried.
Margus
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The possibilities aren't really that limited. For example, if you want to
read the Nth item in a file, just close it, re-open, and read till you get
there. It may be slow, but it works!
In the early days of computers, almost all data processing was done on
serial access devices. There were all sorts of clever algorithms created to
do this as efficiently as possible. (Merge Sort is one that comes to mind.)
Have a read of the Knuth "Art of Computer Programming" series for example.
I actually really enjoy the challenge of working around the limits of the
language. But maybe I'm a masochist.
Regards
Gordon
<gbe### [at] birdcameroncomau>
Margus Ramst <mar### [at] peakeduee> wrote in article
<36d4436c.0@news.povray.org>...
>
> Thomas Willhalm wrote:
> >
> >How about writing them to a file with the new #read and #write
directives?
> >There is also a new clock_delta constant. In my opinion, this should be
> >all that you need. (No, I don't have the time to try to write such
macros.)
> >
>
>
> This would be plausible, if these directives were a bit more
configurable.
> Right now #read just reads a number of params from the start, you can't
> specify an offset to the read. This severely limits its possibilities.
> Believe me, I've tried.
>
> Margus
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
BC wrote:
>
> I actually really enjoy the challenge of working around the limits of the
> language. But maybe I'm a masochist.
>
To a certain point, it's fun. From then on, it's tedious and just plain
impractical. Some projects I've worked on have required very extensive and
very dynamic data processing, tens of thousands of data lookups and
stores. Thank God (or the POV team) for arrays - but these are useless for
animation.
Mine may be an extreme case, but I'd rather just specify an offset to the
read/write. This shouldn't be too difficult to implement (and is one of
the top items in my wishlist).
Margus
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
