I like your thoughts and I hope you will share them with the MegaPOV team.
They might not read this post.

As you, I prefer a direct connection between modellers and POV-Ray. Any
stand-alone program that acts as converter, isn't the best solution.
Currently mesh2 files are out of reach for a macro that tries to work on the
data. The core of this problem is the mesh2 format; not the #read directive.
But instead of adding a mesh3 format, I think POV-Ray could benefit in
general from better reading capabilities.

Other programs usually have a long list of supported formats, to export and
import. Why not POV-Ray? Yes, it's a different approch to 3D and more math
minded. But why stand in the corner, when combining talents from other
software, would help POV-Ray to rock even more. There is a risk that people
would begin to use POV merely as a raytracer; thereby it would loose some of
it's uniqueness. But still...!

Regards,
Hugo

Post a reply to this message