Maxwell Render | Official public forum

Hi,

The ways I'm aware of to assign materials are these three:

1. Drag and drop.
2. Select objects, then right material and choose "Assign to selected"
3. Select a material, right click it and choose "Select and Assign"

I find myself using number 2 all the time, but it's quite a maneuver for something one does so often. Right clicking and finding something in the middle of the context menu.

It would be great if there was a simpler way, something like:

1. I select the objects I want to assign
2. I double click (presumably with a modifier key such as CTRL or similar) on the material, and it's assigned.

What do you think?

Best

- Björn

How about this:

• 1. select the objects you want to assign.
  2. drag/drop the desired material onto the viewport.

It will work that way if you set Options > Behavior > De-select All On Drag to No.

Hi Björn,
I believe Doubleclick on the Shaderball already taken in all contexts, so this definedly had to happen with an additional Modiier Key.
What I would not like about the Mapping you propose is that Doubleclick is typically not associated with altering other objects properties.
It typically means editing the item itself, opening up its sub-compontents and hierarchies or starting processes.

I would already be perfectly happy when Maxwell for Rhino at some point got the nice Drag and Drop Assignment the McNeel-supported
Renderers have. Here one even gets an intuitive PreSelection Highlighting if I recall correctly. Having to have items already selected
for drag and drop and not getting visual feedback after dropping a .mxm (apart from the Commandline Printout) works less good.

Holger

Hi,

JD: I wasn't aware of that, thanks, I'll give it a shot. It sounds simple enough actually!

Polyxo: I see what you mean, it might confuse.

Regards

- Björn

Polyxo wrote: I would already be perfectly happy when Maxwell for Rhino at some point got the nice Drag and Drop Assignment the McNeel-supported Renderers have. Here one even gets an intuitive PreSelection Highlighting if I recall correctly. Having to have items already selected for drag and drop and not getting visual feedback after dropping a .mxm (apart from the Commandline Printout) works less good.

I am confused, Holger, because the plugin has worked exactly as you describe here for several years now.

JDHill wrote:

Polyxo wrote: I would already be perfectly happy when Maxwell for Rhino at some point got the nice Drag and Drop Assignment the McNeel-supported Renderers have. Here one even gets an intuitive PreSelection Highlighting if I recall correctly. Having to have items already selected for drag and drop and not getting visual feedback after dropping a .mxm (apart from the Commandline Printout) works less good.

I am confused, Holger, because the plugin has worked exactly as you describe here for several years now.

Sorry JD,
I forgot to add "with Hud showing" which I have always on when using Maxwell.
I need less the Hud itself but the Overlay.

Yes, but factoring for that bug, you should see no difference between the drag/drop behavior of this plugin and that of other renderers (i.e." the nice Drag and Drop Assignment the McNeel-supported Renderers have"), correct? Here, the overlay breaks Rhino Render drag/drop just the same as it does for Maxwell.

JDHill wrote:Yes, but factoring for that bug, you should see no difference between the drag/drop behavior of this plugin and that of other renderers (i.e." the nice Drag and Drop Assignment the McNeel-supported Renderers have"), correct? Here, the overlay breaks Rhino Render drag/drop just the same as it does for Maxwell.

Yes, when the Hud is off off it looks the same. Sorry - I did not try this for long.

Thanks for confirming, I just wanted to be sure there wasn't some other unknown issue. I reported this issue long ago, and I've now just reported it again.

Thanks Jeremy!

Hi again, Holger -- Jeff says he has fixed this for the next V5 WIP build. V4 fix will depend on whether there's another SR or not.

JDHill wrote:Hi again, Holger -- Jeff says he has fixed this for the next V5 WIP build. V4 fix will depend on whether there's another SR or not.

Cool!
V4 isnt critical for me - I only still use it on rare occasions (not for rendering).

Thanks, Holger