Ken wrote:
> Each of the above examples are perfectly valid and illustrate the
> various types of POV-Ray scene file coding in practice today. A
> pov2xxx conversion program would have to be able to recognize
> each of those varations and decide what to do with them. That is
> just the beginning. Then, since POV-Ray objects are mathematical
> representations, they would have to be tesselated into a triangle
> based or similar system, that most other 3D file formats use. Do
> you start to see some of the practical problems involved ?

Hmm.  Yeah, that is a challenging thing.  But...pov can parse
each of the things, and there are already-existing tesselations
for spheres-to-triangles (it's what those other, wimpier 3d
modellers like 3d studio use).  So it's not impossible, nor
terribly unfeasable...pov IS open source, ain't it?  So the
parsing code is already available.

...but then, you're not allowed to use pieces of POV in
other software.  Ok, so much for that idea.

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