[Jalixko]

Hi all!
I´ve got several bugs to check and more improvements for next versions both plugin and Maxwell render.

Bugs:

-For any reasons Maxwell Lights are not exported as passes in an unic OpenXR file.
-Two emitters HDRI and standard lighting together in a scene are not working properly. in ML+Color
-Maxwell parameters from the shape nodes do not affect the shadow chanels in render, to avoid this is necesary to set the Nd,K to 1, making the objects transparent. It will be appreciate adding a hide shadows to maxwell parameters.
-Rendered images from batch render differs from rendered within maya in some cases where a character set up is involved. Seems to be some nodes (expressions or node utilities ) are not beeing evaluated.
-Image Type flag -of not supported or not working
-If a channel from IBL has a file(hdri) loaded but this deactivated Maxwell ask for it anyway and does not render the image.
-Sun Temperature seems to give wrong results as the manual says depending on the settings in skydome colors. (there is a workarround, may be a litle dirty)

Improvements:

-Some parameters to manage mememory when rendering will be apreciated.
-In Sky Dome, as the sun and enviroment have independent intensity values, I would like to have the values as independent channels in the multilight panel.
-I would like to have another parameter for SkyDome to avoid the simetry in the sky. Mapping the virtual skysphere, with a ramp will give more flexibility.
-"Geometry that is not going to change could be exported just once, instead on a per .mxs export. A workflow similar to what can be done with RenderMan using Delayed Rib Archives would be great IMHO."

[Mihnea Balta]

-Two emitters HDRI and standard lighting together in a scene are not working properly. in ML+Color
-Maxwell parameters from the shape nodes do not affect the shadow chanels in render, to avoid this is necesary to set the Nd,K to 1, making the objects transparent. It will be appreciate adding a hide shadows to maxwell parameters.
-If a channel from IBL has a file(hdri) loaded but this deactivated Maxwell ask for it anyway and does not render the image.
-Sun Temperature seems to give wrong results as the manual says depending on the settings in skydome colors. (there is a workarround, may be a litle dirty)
-Some parameters to manage mememory when rendering will be apreciated.
-In Sky Dome, as the sun and enviroment have independent intensity values, I would like to have the values as independent channels in the multilight panel.
-I would like to have another parameter for SkyDome to avoid the simetry in the sky. Mapping the virtual skysphere, with a ramp will give more flexibility.
-For any reasons Maxwell Lights are not exported as passes in an unic OpenXR file.

These are all engine issues, please report them in the main forum. The people who can implement them probably don't read this forum.

-Rendered images from batch render differs from rendered within maya in some cases where a character set up is involved. Seems to be some nodes (expressions or node utilities ) are not beeing evaluated.

We've seen this issue once or twice, but it's impossible to debug without a scene which triggers it (and even then it's pretty hard). Can you isolate the problem to a relatively simple scene and send it to me?

-Image Type flag -of not supported or not working

I'll look into this.

-"Geometry that is not going to change could be exported just once, instead on a per .mxs export. A workflow similar to what can be done with RenderMan using Delayed Rib Archives would be great IMHO."

We've discussed supporting referenced MXS files, so you can export static geometry only once and reference it in other MXS files. It will probably happen at some point, but it requires a bit of work in both the plug-ins and the Maxwell core, and I don't know when it will be scheduled.

[Jalixko]

Jalixko wrote:
-Rendered images from batch render differs from rendered within maya in some cases where a character set up is involved. Seems to be some nodes (expressions or node utilities ) are not beeing evaluated.


We've seen this issue once or twice, but it's impossible to debug without a scene which triggers it (and even then it's pretty hard). Can you isolate the problem to a relatively simple scene and send it to me?

Ok, if I have enough time to digging in to this I´ll prepare a scene reproducing the error.