[rusteberg]

Thanks Nicole for the explanation.
Will I be able to continue working on Rhino on my workstation while my render box churns out SLs ?
Otherwise said : does the plug-in count as an instance of Maxwell when it is loaded in memory ?

your boxx rep wouldn't happen to be Chuck? If this is your first Boxx product, then i guarantee you'll be happy! Their customer service reigns SUPREME! I had a stick of RAM go bad on my workstation not long ago and they had a new one to me the next day. Only problem with the renderboxx is flaky maxwell networking..... you might find yourself buying a kvm switch soon.... EN-JOY!

[JDHill]

Hey Olivier - since the plugin has no actual rendering functionality inside of it, it is not restricted by the license (in fact, it doesn't bother with any license at all). It does have to start Maxwell as an external process to render material previews, so that might be a consideration.

[nicole]

Yes, if you are running a plug-in, that is considered another instance of Maxwell. So if you are working with Maxwell (or using a plug-in) on one machine and are rendering in Maxwell on another, that would require two licenses. Of course, if you are just working in Rhino without touching Maxwell or the plug-in, that doesn't require a Maxwell license!

Cheers,

Nicole

[brodie_geers]

I think strictly speaking it will let you have multiple instances of Maxwell open, however you can only have one render going at a time. Correct me if I'm wrong.

-Brodie

[nicole]

Hi again, sorry for my confusing answers before. Jeremy is right in what he says in his previous post!
In general, if someone is using Maxwell Render on multiple concurrent machines, he/ she should have multiple Maxwell licenses.

Cheers!

Nicole