When trying to put a mesh2 into a mesh_camera instead of a regular mesh, POVray
aborts on the line containing vertex_vectors with "Parse Error: No triangles in
triangle mesh."

Putting a triangle into mesh2 seems to work.
Writing mesh42 instead of mesh2 causes a parsing error at this point already.

Using mesh2 objects for regular objects works fine, though.

Please tell me if you need additional information.

Post a reply to this message

> When trying to put a mesh2 into a mesh_camera instead of a regular
> mesh, POVray aborts on the line containing vertex_vectors with "Parse
> Error: No triangles in triangle mesh."

   Hmmm... I'm using it with mesh2 without any problems here. For
example, my latest AO baking demo uses a mesh2 converted by Poseray:

http://www.ignorancia.org/en/index.php?page=ao-baking

   Admittedly, I only tried with mesh2 objects converted by Poseray, but
with a lot of them, from very different origins. Your mesh2 is the
output of a conversion software, or custom made?

--
Jaime

Post a reply to this message

"lytenyn" <nomail@nomail> wrote:
> When trying to put a mesh2 into a mesh_camera instead of a regular mesh, POVray
> aborts on the line containing vertex_vectors with "Parse Error: No triangles in
> triangle mesh."

This kind of code causes the error:

camera {
    mesh_camera {
        1 3
        mesh2 {
        ...
        }
    }
}


This should work:

#declare cam_mesh = mesh2 {
....
}
camera {
    mesh_camera {
        1 3
        mesh {
            cam_mesh
        }
    }
}

Post a reply to this message

You are right, wrapping the mesh2 into a #declare does indeed solve the problem.

Thank you very much!

This should either be documented somewhere or fixed, I assume..

Post a reply to this message

> You are right, wrapping the mesh2 into a #declare does indeed solve the problem.
>
> Thank you very much!
>
> This should either be documented somewhere or fixed, I assume..
>

   Well, the syntax on the docs already suggests it has to be declared 
before, as it requires a MESH_OBJECT_IDENTIFIER:


camera {
   mesh_camera {
     rays per pixel
     distribution type
     [max distance]
     mesh {
       MESH_OBJECT_IDENTIFIER
       [TRANSFORMATIONS]
     }
     [mesh ...]
   }
   [location]
   [direction]
   [smooth]
   }

   But yes, it could be said explicitly somewhere on that section...

--
Jaime

Post a reply to this message

On 11/22/2012 03:27 AM, lytenyn wrote:
> You are right, wrapping the mesh2 into a #declare does indeed solve the problem.
>
> Thank you very much!
>
> This should either be documented somewhere or fixed, I assume..
>
>

Added a clarification to the 1st paragraph:
http://wiki.povray.org/content/Reference:Camera#Mesh_projection

Post a reply to this message

> Added a clarification to the 1st paragraph:
> http://wiki.povray.org/content/Reference:Camera#Mesh_projection

Thank you!

Post a reply to this message