[bjorn.syse]

Hi, please see the following post...

http://www.maxwellrender.com/forum/view ... 656#271656

... and please let me know if anyone of you have tips for paths that work when rendering with OSX but using MXS-files from Windows.

Best regards,

- Björn

[bjorn.syse]

Hi Again, if anyone has a working workflow similar to this one, please raise a hand:

1. Preparing an MXS on Windows (perhaps through parallells desktop)
2. Rendering that same MXS with Maxwell in OS X

I can not get this to work for practical reasons when using textures in materials, since these don't get shipped inside the .MXS. There has GOT to be a way!

- Björn

[jvanmetre]

bjorn.syse

I have the same or similar workflow.

I create in Rhino, then "export to mxst", do some tweaking in Studio (still on XP) then use the Pack&Go, writing to a shared folder on the XP machine.

From my MAC I access the shared folder on the XP machine (sometimes I will just go to mxcl and render, many times I will open Studio on the MAC and do additional tweaking and then render on the MAC.

It has worked very well for me although lately (with 1.7) I've been having some export issues with Pack&Go.

jvm

[bjorn.syse]

Interesting, I have never used the "Pack and Go" feature, but I aswell use Rhino on Windows. What does the "Pack and Go" feature do?

[jvanmetre]

Pack&Go collects the scene and materials and drops them where you say. Oh...give it a try, it's pretty straightforward.

jvm

[bjorn.syse]

jvm, Sounds good. That includes all textures and stuff aswell I presume?

The way I've tried doing it for now, is using Rhino within Parallels desktop on the mac. I assign the material in Rhino, using them as they reside on my Mac HD, though accessed via the Parallells desktop network path (something like //.PSF/.home/path/on/mac).

This does not seem to work. I tried using the -bitmaps with mxcl flag on rendertime to manually override the path for all the bitmaps, which would have worked in theory if it wasn't for that it ignore my custom texture mappings setup in Rhino.

I'll try using a shared network disk, but since this is all just one computer running two operating systems (one virtualized) I'm not sure how I would do that. One option is using a third network disk exlusively for storing the scenes and materials...

Is there a reason that you use Studio aswell for tweaking? Can pack and go be used directly from the Rhino plugin?

thanks for your comments jvm, I appreciate it.

[jvanmetre]

I'm not sure my method is the best workflow!

You could try using a 3rd disk. I've got my XP machine networked using a router and OSX connected to the router with an ethernet cable. OSX has no trouble reading the shared folder and getting the file.

I typically don't use Rhino to write just the mxs -- and that's mostly because withj earlier MW iterations there seemed to be more features with Studio with regard to working with materials (being able to select polys and apply materials, as well as, camera options). This has changed though with JD's plugin improvements.

Sometimes, I will quickly render on my XP machine from Studio, check to see if it's okay, and then will write the Pack&Go file and render directly from mxcl on my MAC -- bypassing Studio on the MAC.

I'm not sure if just writing an mxs from Rhino these days will take all the materials and textures along -- it's possible. Like most people -- if it works, I tend not to change until something better comes along.

The good thing with Pack&GO is that it takes everything and puts it into one folder and either OSX or XP machine can use it.

jvm

[bjorn.syse]

Thanks, I will try to get something to work using your suggestions. Thanks again,