Workflow question -- Rhino to MW on OSX

Workflow question -- Rhino to MW on OSX#312092

By jvanmetre - Fri Oct 16, 2009 4:24 pm

- Fri Oct 16, 2009 4:24 pm #312092

I think there are few people with a workflow from Rhino to MW on OSX...haven't purchased the upgrade yet...are you able to export using pack and go from the Rhino/MW plugin and open in Studio and render on your OSX machine?

Thanks,

JVM

Re: Workflow question -- Rhino to MW on OSX#312096

By kami - Fri Oct 16, 2009 4:56 pm

- Fri Oct 16, 2009 4:56 pm #312096

this works fine if you don't use any complicated sybols in your filenames like öäüèéà ...
but why switch to os x if you could render directly on windows?

nightnurse images, Zürich
http://www.nightnurse.ch

Re: Workflow question -- Rhino to MW on OSX#312099

By jvanmetre - Fri Oct 16, 2009 5:07 pm

- Fri Oct 16, 2009 5:07 pm #312099

Work in Rhino on "older" machine for modeling purposes and export to much faster Macpro. It's kinda like separation of church and state.

jvm

Re: Workflow question -- Rhino to MW on OSX#312102

By kami - Fri Oct 16, 2009 5:25 pm

- Fri Oct 16, 2009 5:25 pm #312102

hehe. not a bad concept

the pack and go thing worked fine for me (with 1.7) with the named restrictions.

nightnurse images, Zürich
http://www.nightnurse.ch

Re: Workflow question -- Rhino to MW on OSX#312107

By JDHill - Fri Oct 16, 2009 5:55 pm

- Fri Oct 16, 2009 5:55 pm #312107

Hi Jim - the 2.x plugin has a new pack and go function that works more simply than older plugins. What it does is:

- copies all referenced files into a /textures folder next to the target mxs
- alters all paths in the mxs to point to the newly-copied textures, using relative paths

So, the mxs has no relationship to the machine on which it was generated; when you render this mxs in maxwell, it should find all the files automatically no matter what machine the file has been moved to.

Next Limit Team