Warp <war### [at] tagpovrayorg> wrote:
>   You lost me with the "XML" part. I couldn't follow your logic.

Is POV-Ray rendering engine or is it script based rendering software?
Rendering engine should input data from other tools and XML is easy to
parse and generate. There is no use for editor in rendering engine. That
should be different program.

>> POV-Ray's biggest problem is weak animation support. It is useful mainly
>> for still pictures.

>   And POV-Ray supporting a hamster AI helps this how?

If you like to model grass do you set every 100000 blade to scene or do you
make macro for that? If you want to animate hamsters you don't want to tell
every hamster movement on every frame on every scene where you like to use
hamster object now and later.

With collision detection and physics you can also throw hamster with bowling
ball and kill it. Or stupid hamster can walk over table and die if the drop
is enough high.

Of course this kind of stuff is also useful when modelling water particle
behavior and so on.

Matti

Post a reply to this message