[JDHill]

Maxwell for Rhino
Version 2.5.12 Release Notes

This version of the plugin brings Maxwell Fire to the plugin's material editor.

Changes

• Compiled for compatibility with Maxwell Render 2.5.1.
• Added new Fire-based material preview rendering.
• Wizards now offer to overwrite the current material.
• Added new Maxwell 2.5-style SSS Preset wizards.
• Added ability to save Maxwell Fire image.
• Extrusions are now supported in Rhino V5.
• New user preference system implemented.

Fixes

• Database manager visible state was not remembered.
• It was not possible to set a Sun Power value lower than 1.0.
• Plugin initialization could fail if AppData directory redirected.
• Weight value in BSDF UI could become disabled forever.
• During export, Rhino textures were not compared correctly.
• Anisotropy & Angle labels were reversed in the BSDF UI.
• Scene Manager tab text was too light with some themes.
• Changes to displacement were not triggering a Fire refresh.
• Rhino 'Assign material' button was not working properly.
• The plugin now attempts to alter block definitions for Real Scale.
• Removing or disabling displacement resulted in a crash.
• Removed some spurious calls to refresh Fire.
• MXI/IES emitters were enabled even with bad paths.
• Material assignment on nested blocks was broken.
• Material assignment to curves was not persisted.
• Meshes could be written with not enough projectors.
• Bit depths other than 8bpp caused problems in Fire.
• Z-clip values were not being validated.
• Maxwell_ExtractMaterials was partially broken.
• 'blocks' node was created, even with no blocks.
• Bad IES paths were not being fixed sometimes.
• Invalid path report was ignoring IES files.
• Pack and Go could fail to copy IES files.
• Textures could not be disabled in Fire.
• Fire was not updated for some texture changes.
• Objects with no tex coords were not being fixed.
• 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

• Due to the new preferences system, if you are using a customized plugin color scheme, it is advised that you save it to a file (see the toolbar in plugin options) so that you can re-import it after installing the update (only applies if you are upgrading from a plugin older than 2.5.1).

[bjorn.syse]

Hi!

Just a note, I'm still experiencing the problems that Polynurb also reported with the material preview jumping and skipping between SL 1 and the final image.

Regards,

- Björn

[kami]

Thx for the update. I got a question concerning the Installation Engine. (x64 version)
It always wants to install the plugin to "C:\Program Files (x86)\" as default. Can't it detect the position of the last plugin installation or just of my rhino5 folder (C:\Program Files\Rhinoceros 5.0 WIP (64-bit)\Plug-ins\)?

[JDHill]

Thanks Björn, I'll keep looking into it. I had found one thing which I though might affect it, but apparently it did not.

Kami, it chooses that folder, so that you don't end up having two copies of the same plugin on your machine when you install both the x86 and x64 plugins. Of course, that's optional, since you can choose any folder you wish during the installation.

[kami]

ok. didn't know that. I always thought the two plugins don't share any components.

[kami]

the plugin does not work with 2.5 maxwell, right?
weird that fire does work

[JDHill]

Yes on the first thing, since 2.5.0 can't read a 2.5.1 MXS file, but on the second, no it's not weird -- plugins contain Fire directly.

[kami]

Hi JD
I found a bug: The override material does only work if you got Fire running as well. If Fire is closed, the command is ignored.
cheers, kami

[JDHill]

Thanks, I see it too.

[kami]

the next one, if I'm not mistaken:
If you cancel the export (ctrl+alt+shift) it does start mxcl and render a part of the exported objects.

[JDHill]

Thanks, I see it here too.