Exporter for Rhinoceros

[patro]

Luxrender recognize the nurbs geometry.... what Luxrender finally display in the window is it a rendered nurbs or a mesh?

Currently it triangulates the nurbs using a fixed number of "steps" in both directions (30, if I read the code right). Considering the complexity of directly rendering a nurbs surface triangulation is probably the best way to go, however a fixed triangulation resolution is non-optimal. It shouldn't be too hard to triangulate based on curvature (and optionally resulting size of the triangles), feel free to add a feature request once the exporter's up and running, so we have something to test with .

thank you Lord,
have I to understand that Luxrender mesh it self the nurbs data! I'm right?

[Lord Crc]

It converts the nurbs into a triangle mesh before rendering, yes.

[patro]

It converts the nurbs into a triangle mesh before rendering, yes.

0k thank you again!
one last question:
which is the convenience of Luxrender to read nurbs data?
for example rhinoceros have a tool to convert nurbs in to mesh... and you can also chose the tessellation grade!
thank you again
patro

[tomb]

It converts the nurbs into a triangle mesh before rendering, yes.

0k thank you again!
one last question:
which is the convenience of Luxrender to read nurbs data?
for example rhinoceros have a tool to convert nurbs in to mesh... and you can also chose the tessellation grade!
thank you again
patro

Well, one good point to have NURBS internally instead of via a pre-tessellated mesh is, as LordCrc mentioned above, the possibility to tessellate the NURBS "on-demand"; i.e. do it dynamically based on point-of-view, film resolution etc. Another advantage is smaller geometry files (and thus less export/import time)

[patro]

It converts the nurbs into a triangle mesh before rendering, yes.

0k thank you again!
one last question:
which is the convenience of Luxrender to read nurbs data?
for example rhinoceros have a tool to convert nurbs in to mesh... and you can also chose the tessellation grade!
thank you again
patro

Well, one good point to have NURBS internally instead of via a pre-tessellated mesh is, as LordCrc mentioned above, the possibility to tessellate the NURBS "on-demand"; i.e. do it dynamically based on point-of-view, film resolution etc. Another advantage is smaller geometry files (and thus less export/import time)

that's great!..
and thank you Tomb!

[flatland]

hi! is this project dead?

[patro]

hi! is this project dead?

as I know Exvion is still working on it and also on other exporters.
but it would be nice to have some news about.

[flatland]

ok thanks! i'll wait

[flatland]

any news?

[nickeh]

How is it going with this?

Is there any source code available if some one else would like to give it a try?
Would be great to have a good free renderer for Rhino.