Maxwell Render | Official public forum

Maxwell for Rhino
Version 2.5.1 Release Notes

Version 2.5.1 of the Maxwell for Rhino plugin is mainly a bug-fix update.

Changes

• Added ability to save Maxwell Fire image
• Extrusions are now supported in Rhino V5

Fixes

• Mesh transfer was slow in some cases
• IBL Intensity now updates Maxwell Fire
• Maxwell Fire could hang in some cases
• Maxwell Fire could refresh unnecessarily

Notes

• This version of the plugin implements a new user-preferences system. If you are using a customized plugin color scheme, it is therefore advised that you save your current color scheme to a file (Scene Manager > Options toolbar > Save UI Colors File) before installing this update so that you can re-import it afterward. This plugin also uses new default color schemes, on a per-Rhino version basis; if you prefer the old default color scheme (i.e. dark, Maxwell-style), it is available in the file classic.xml, which you will find if you click Scene Manager > Options toolbar > Load UI Colors File.

Downloads:

• (version superseded)

Please try this build and let me know if it takes care of the mesh-export speed issues which were introduced in the initial Maxwell Fire-enabled plugin, version 2.5.0. Please post any issues you find with this build in this thread.

Cheers,

JD

Hi JD,
all looks very good to me - don't see problems so far!
Is there a chance that you find the time to hook up

Rhino-Edge-Softening
Rhino-Curve-Pipingcur
and
SSS-Presets?

for the final release?

cheers, Holger

Those RDK-related things should currently work in Rhino 4 and Rhino 5 x86, but not Rhino 5 x64, and they won't work in x64 until I start doing V5-specific builds. On SSS presets, I'll check it out.

JDHill wrote:Those RDK-related things should currently work in Rhino 4 and Rhino 5 x86, but not Rhino 5 x64, and they won't work in x64 until I start doing V5-specific builds. On SSS presets, I'll check it out.

Thanks - I thought as you hooked up Extrusions as V5 exclusive stuff it was already the right time to ask

No, I was able to get Extrusions working because in the end, Rhino identifies object types by a named integer -- so, although the plugin can't know their name, it can know their number, and therefore, that it should not ignore them like it must do for many other uninteresting object types.

Just to note a couple of issues which have been found and will be fixed before an official 2.5.1x release:

1. Objects with no texture coords do not appear in the render. Workaround: add texture coords (i.e. add surface/cubic/etc. mapping).
2. Changes made to textures only apply to Fire when the texture in question is current. Workaround: make a texture current before working on it.
3. Textures are never disabled in Fire, once they have been enabled. Workaround: use the Refresh button in the Fire window after a texture has been enabled or disabled.

thank you very much, I use it on large model now!

Hi JD
I got the impression, that realscale is not working anymore with the latest plugins?
screenshot: http://www.deiters.ch/maxwell/realscale.jpg
file: http://www.deiters.ch/maxwell/realscale.zip

The cubes are 1m, 2m and 5m and the texture is always tiled once.
Is this a bug or did I make a mistake?
Thanks for confirming.
Cheers, Kami

Either using the Refresh Viewport Materials command, or changing the texture tiling re-enforces real scale correctly in the viewport, correct? The only change you should notice in this area would be that you may need to use Refresh Viewport Materials more often than you previously did, since Rhino 5 has not liked me asking it to do that when opening files.

You are right, the refresh does work.
ok, I tried a bit around with it, the results are:

If you apply a real scale material to an object or layer, it does not work. If you change the tiling it affects the wrongly applied texture but does not bring real scale.
Once you hit Maxwell_RestoreViewport, everything is looking good, also if you change the tiling afterwards.

Do you have the same behavior?

Yes, I see something like that here -- it might take some time to chase it down.

Sorry, but just to clarify - does Rhino soft edgening work with Maxwell? And if so, does it work with Fire?

It is supported when running in Rhino 4 and Rhino 5 x86. By default it is disabled; the setting which enables/disables it is Options > Behavior > Ignore RDK.

Ah, there it is. Thanks! Have to try that out.

Are there any drawbacks of not ignoring RDK?