[polynurb]

ideally we could use .mxs to go both ways... not knowing if it can be done easily.. i imagine a great benefit for maxwell if users of totally different platforms cold exchange render ready scene data between their packages.. what a great improvement to heterogenous working environments that would be!

also there seem to be more and more maxwell ready models out there.. but they are usually provided in .mxs for use in studio (eg. dosch) .. so not easy to get into rhino without having to reassign/reimport maxwell mats manually, after going the obj. way...

daniel

[JDHill]

There have been questions about this, or things similar to it, in the past. In the SketchUp forum, I'm being asked to provide a proxy object which references an MXS file, since SketchUp is 32-bit -- the MXS would be merged into the scene as it was being exported from the plugin. That would be tricky for various reasons, but I think it would be superior to importing the whole MXS into the host app.

Both would be possible -- let me know what you think about it.

[polynurb]

thanks for your fast reply!

sorry i don't quite get the difference between the proxy object and importing into the host app.

wouldn't the result be the same?

i was also thinking that it would strengthen the position of the .mxs format if it could be used to exchange data between programs and use it as a solid and reliable exchange format.. all of a sudden you could exchange data types between eg. Rhino and Maya at a complexity hardly possible before.

[kami]

I think the easiest way would be to import it into the scene.
then you could change the materials, or even the geometry if needed.

[numerobis]

both options would be very helpful!!!
proxy exchange on the fly for sketchup export and mxs import for all major 3d apps would be great!!!