LuxRender, a new open-source unbiased renderer

[Labello]

i also tested luxrenderer and i loved it. but i will stick to indigo! for the moment. but i also will keep an eye on luxrenderer

[psor]

I can say for myself that I take it pretty easy. I use the tool that fits best for
the work I've to do. So no sticking here or there, I just stick everywhere.






take care
psor

[dougal2]

Luxrender may get a new Maya exporter soon

Conversely, MtI might also see some improvements

[psor]

Good to know, thanx Doug! ;o))



take care
psor

[Wedge]

As far as I know the exporter for Blender/Lux was based on the Blender/Indigo exporter. And since the Blender/Indigo exporter is GPL then it can be (would be easy to port my latest work that exports mesh as OBJ, any other render software that supports OBJ could use this code with almost no modifications done to it) ported to another renderer. No ripping off of anything as long as the GPL license is followed.

Edit: I should add that I export Mesh data AS IS, I do not try to fix mesh errors or modify mesh data other than shrinking it. (shrinking the mesh for the skin feature) It is my opinion that your mesh data should be correctly designed from within your 3d program and not the exporters job to fix it. The exporter should only have to translate the data, in my opinion. There are exceptions for certain things like that skin feature. Where it would be annoying to try to shrink a mesh by hand. But even this feature should be a separate script and not part of a exporter.

And it looks like Zuegs is working on the Blender/Lux exporter and he was also the one that used to work on the Blender/Indigo exporter and was the one who implemented the material editor. (again, as far as I know)

Some of you may wonder what I will do. I can assure you I will not be developing any other exporters for any other render software. I have had enough fun in that department. The work I have done is under a GPL and can be used further as the GPL permits so that was my contribution.