|
 |
Ken <tyl### [at] pacbell net> wrote in message
news:399C51B5.506F6DF9@pacbell.net...
>> What that error message usually means is that your mesh object(s)
contained
> nothing but degenerate triangles which POV-Ray will not accept. I have
> seen this in the past when using 3DWin to convert between various formats
> but only rarely.
The main clue for me is that the same object rendered with no errors when it
was exported in a smaller group of objects. A much smaller file size.
Although I kind of wonder if my system didn't make some errors while
handling the really large export of the entire model. It was swapping out
to disk a lot during the udo translation operation in Rhino.
-Steve
>
> Steve Clarke wrote:
> >
> > List,
> >
> > I'm modeling a highly detailed F1 race car in Rhino 1.1 and exporting as
a
> > Moray udo object. I think I have encountered some limits in file size
> > because of the following:
> > If I export the entire model as a udo and attempt to render in Moray
> > 3.2/Povray 3.1, I will get an error like this:
> >
> > error: no triangles in triangle mesh
> > rear_susp_object62
> >
> > I was able to locate 'object62. Knowing what the object is I went back
into
> > Rhino and exported a smaller portion of the model which included
'object62.
> > This time I was able to get a render with Moray/Povray. This leads me
to
> > believe that I may have run into some kind of limitation for the size of
the
> > file. Would this be the case? Workarounds?
>
>
> --
> Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
> http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
