[yanada]

Would it be possible to write an MXS exporter for Moi, with material/camera work being done in MXST.

Imaging the possibilities, Moi could take full advantage of studio, it could be an amazing combo espatially for product photography.

Sorry JD I know you have only two hand.

[JDHill]

Hi yanada,

I corresponded with Mr. Gibson about this some months ago, and we came to the conclusion that until Moi has a material system and plugin capability, it makes little sense to invest the effort to write a dedicated MXS exporter, seeing that MXST already reads OBJ. When Moi can host a plugin UI, then there will be something real to be gained.

Cheers,

JD

[yanada]

Thank you for your promt answer

It makes me really happy that you have a eye on moi and your and Micheal Gibson's knowledge could only result to great things.

as far as I can see the only think for me is to hibernate... until that happens

and yes OBJ does the job for now.

[yanada]

Sorry to bother you but would it be possible For mxst to support native 3dm and IGES files, something like bunkspeed?

[JDHill]

I highly doubt it, as the renderer is based completely on triangle-meshes. Wherever you have NURBS, SubDs, or any other thing - you always also have meshes - so it wouldn't make alot of sense for Maxwell to try to tie itself to any of the proprietary non-mesh formats. Well, that's my speculation, anyway - meshes are just too interoperable to move away from them any time soon. If it were possible for any of those other formats to be completely self-describing, as is the case with simple triangles (i.e. you need absolutely no interpreter to understand the meaning of the data), then it would be a good way to go.