Everything related to the integration for Rhinoceros.
One thing that could make the absence of a stable plugin less painful is to (at least ) make the mxs exported from rhino usable in the studio: currently the objects are not organized by layer and therefore it is not possible to make an easy mapping in maxwell studio...
By Marton Day8
Hello Nicola,
OK, I will add the layer group export

Hello Jasper,
I have added these for the next build, but in your current version it is still not there.

By Felipe Millan
Is just me or the new Mawell version is really complicated to use, I feel is missing multiple functions or are hidden in places that I can't find, the emitters that used to work on the previous version don't make any change to the scene now, I don't know if I'm doing something wrong but all mi scenes look flat, like the materials don't have character is almost as if I get better results from the rendered window on rhino, also tends to freez my PC when I try adding hdrs as environment. Where can I find a guide of the work flow for this version, is getting really frustrating, also I have to stop my render and change the sampling in the render window, because it does not take the sampling level from rhino, it always defaults to 7, and the camera function to focus to selected objects that was so easy to do on the previous version is gone, or I'm unable to find it, there is one but as soon as I select an object the camera menu disappears, really frustrating.
User avatar
By Forum Moderator
Hello Felipe,

Here is a quick transition guide: https://docs.google.com/document/d/11SS ... 61s7ly07fu

I'm currently testing a version with several improvements regarding Rhino lights translation and many other things but found some problems that wanted to get fixed before releasing it.

Forum Moderator wrote:
Wed Jul 24, 2019 4:08 pm
PA3K wrote:Hi Fernando,

I noticed few things in new released plugin.
1. Changing Engine in Fire Settings to GPU and then trying to changing perspective window to Maxwell Fire crashes Rhinoceros 6 (laptop GPU NVIDIA GeForce GTX 880M Kepler)
2. Different default render settings in compare with MWR3 in Rhinoceros 4 and different look of rendered image even with the same settings.
Hello Patrik,

Regarding #1, it's true I see some instability when changing to to GPU; your Kepler card is not supported, but it shouldn't crash in that case.

Regarding #2, that's something we have observed and found the reason. It looks like when you bring a file made in Rhino 5 into Rhino 6, this sets the gamma to 1 instead of 2.2, which is the default option in new scenes. That value affects several things, not only Fire, but Rendered view or material preview. You can change it in Rendering tab when it is set to Rhino Render and then go down till you find Dithering and Color Adjustment section; you will find Gamma parameter there. Just set it to 2.2 and everything will start to look normal.

Hi Fernando, my Kepler card https://www.notebookcheck.net/NVIDIA-Ge ... 622.0.html should be supported, as I was runing V4 render on it in Rhinoceros 5 demo back in 2016 viewtopic.php?f=140&t=44529&p=392593#p392593 .
User avatar
By greengreen
I just installed the new maxwell_rhino_v4.2.6.3_WIN
I'm running maxwell
Rhino is Version 6 SR17

So everything looks up to date, but Fire keeps crashing Rhino, and when I click the render button, nothing happens, it does not export a .mxs :?: :?:

Also, two "Maxwell for Rhino" options show up in the "Current Renderer" drop down menu :?:
  • 1
  • 6
  • 7
  • 8
  • 9
  • 10

Long time not-anymore user here. Wasn't multiGPU […]

Rhinoceros 6 support

I just installed the new maxwell_rhino_v4.2.6.3_WI[…]

Good day! We have just released a new version of […]

Hi there, after a texture tag has been assigned to[…]