[JDHill]

Maxwell for Rhino
Version 2.6.0 Release Notes

This is a minor compatibility update for Maxwell Render 2.6.

Changes:

• Compiled for Maxwell Render 2.6.0.
• Added Physical Sky Intensity parameter.
• Added Image Based Lighting Intensity parameter.
• Added pretesselated and vector displacement parameters.
• Save Fire Image dialog now remembers its previous extension.
• MXM Gallery downloads now support MXED's Alternative folder.
• Scene Manager Presets are now shared across sessions.

Fixes:

• Save Fire Image function saved wrong format internally.

[calciati]

Hi JD thanks for the update.

Any news on this bug? LINK
Maybe getting rid of the calendar could remove the problem?

Also as asked here, since there is no UI for changing output format of other channels, could you please make that the same settings used in general output are taken for other channels as well?
I mean if i choose jpeg 8bpp in the main output field all channels will be saved in this way. Does this make sense?

Thanks

[JDHill]

On the first, unfortunately, I have still not been able to reproduce this here, but I will try to theorize some more on what could be causing it. On the second, yes, I will do this, but there was not time for it before the release.

[Polyxo]

Hi Jeremy,
it is obvious that the Rhino-Plugin has no official Hair Support and I can live well with that.
That said - might there be chances to hook up at least partial solutions by supporting Curves
generated by Hand or by Script or Grasshopper? Were you willing to look into this?
Also the FurGen-Plugin by Damien Alomar which was available for some time and runs in V5
has an option to output as curves (instead of meshes as by Default).

Holger

[polynurb]

simple curve support would be great.
it would open up all the possibilities with grasshopper.

maybe export point(could) as particles too

[JDHill]

Thanks for the ideas guys, I have been thinking of ways we might be able to use some of these new features in this plugin. Before hair/particles though, I will probably focus on figuring a way to take advantage of mxs references, and rewriting the motion blur system to take advantage of the new vector-based multi-substep motion blur in Maxwell 2.6.

[polynurb]

sounds good!

i haven't had time to install 2.6 yet .. and only now realized what "referenced" mxs means... how cool that this feature was implemented , so i also think this feature has high priority.

> and i can also see what impact it has.. for a full mxs support, the rhino plugin would need to import&display hair/particles coming from an mxs exporter like maya/max.

[JDHill]

No, it wouldn't need to do that; it might be implemented more as: a block instance (so that we have a transform) of a block definition that contains a point cloud whose points were generated by reading N% of the verts contained in the MXS file. That is analogous to how I am doing it in Cinema -- just drawing a list of points, in order to keep things running smoothly as possible.

[polynurb]

i see, just to understand how the new geometry types are handled inside the mxs:

for example, imported hair would also be displayed as point data? or would it be possible to show n% hair as regenerated curves?

[JDHill]

Possible is not a word I would choose to use at this point; much code needs to be written before I can tell you what can be made to work well. Hair in an mxs is just a huge array of vectors.

[polynurb]

hi JD,


pleas don't feel pushed; as i don't know the code side of things, my question may have sounded a bit crude to you.
Still i understand the situation around hair much better now.

thanks,
daniel

[JDHill]

No worries, sir, any input is good.

[kami]

Hi JD
Thanks for the update. Can't wait to try the new maxwell+plugin when I find the time. And looking forward to having a hair solution at some time in the future.
One question though: What is this referenced mxs integration? What would be the use of it if you are working without studio? I mean it has always been possible to integrate referenced rhino files into my document? What's the difference/adventage?
Cheers,
Christoph

[JDHill]

The point of MXS References (not yet implemented in Rhino) is mainly to reference an MXS without loading it into the memory space of the plugin. So, you could place a couple million trees or similar, and they would only actually get loaded at render time.