This forum will be used to announce new features and release
Hello dear customers,

A new big version of Maxwell is out! Maxwell 5.1. If you already own Maxwell 5 you can download it for free from the portal and if not, you can download it from the web and try it out for some days.

It includes tons of improvements in the GPU engine. You will notice the transparent materials now match the CPU result much better and we added support for coatings too. There are also many, many fixes here are there in the GPU engine behavior trying to make it more solid and predictable. In general you will find it more reliable.

We also added a new Substance Painter assistant in the material editor to easily convert the job done in Substance into a Maxwell material. Check it out here: ... assistance

Also, in this version, an old friend has come back: the Benchwell is now live and available for both CPU and GPU. You will find a new section on the website dedicated to it ( and you can run your Benchwell test from Maxwell Render > Tools menu.

Additionally, if you are a Studio user, don't miss the new search options in the object, camera and material lists to easily find your items. Tip: you can also restrict the selection in the viewport to the objects that match the search by using the new button next to the search box.

It has been released along with all the plugins (except for the plugin for 3ds Max that will come in a few days with support for 3ds Max 2021).

Here are the release notes (you can also check them in the documentation page: ... ease+Notes)

Publish date: Wed, 14 May 2020


  • New Benchwell tools for CPU and GPU benchmarking with online live charts. You can access them from the Tools menu from Maxwell Render.
  • Asset Reference extension object: assimp library upgraded to 5.0.0 so it gives better support for all the file formats.
  • Upgraded Xrite SDK to 1.7.1 so it gives better support for the latest materials.
  • The bump map and the normal map were being affected by geometry’s transformations in some situations.
  • Crash computing denoised image in intermediate steps during render.
  • Launching a render with CPU, stopping, changing to GPU and restarting produced an error when starting the voxelization.
  • The RLM could not be installed on MacOS Catalina.
  • The Random Color procedural texture always returned the same color if the object ID color saturation was 255.
  • The command line parameter -mintime was not only setting a minimum time between each time Maxwell saved output images to disk but was forcing a maximum time too.
  • Maxwell CPU failed to render correctly texture channels higher than 0 if channel 0 was not used.
  • Wrong data issues with TIFF images and LZW compression in Linux platforms (including Maxwell Cloud nodes).
  • MaxwellScatter extension removes MaxwellScatter extension from the scattered objects (if they have).
  • On Mac, Xrite AxF materials make Maxwell close if they are used in the scene.


  • Benchwell tool.
  • Coatings are now supported in the GPU engine.
  • The maximum number of ray bounces is now set to the same as the CPU production value.
  • Much better support for transparent materials:
    • The attenuation color and behavior now matches the CPU engine result.
    • The transparent materials now produce caustics.
    • The transparent materials now do not produce incorrect white fireflies.
  • Improvements in memory management.
  • Wrong textures could be accessed on materials in different circumstances.
  • Several fixes in dielectric (transparent) materials.
  • Bad interactions between emitters and clipmaps who could make light rays turn black (with all emitters) or generate extremely intense fireflies (IES).
  • The bump map and the normal map were being affected by geometry’s transformations in some situations.
  • Some scenes with hidden emitters rendered to black in FIRE GPU and could eventually crash. In general, this affected the scenes with hidden objects.
  • The GPU engine rendered black if no channels were selected (including the Render channel). This has been forced to behave as in the CPU engine and render the Render channel anyway.
  • The MXI file was saved twice after the render ended.
  • The time between SL updates eventually became extremely short.
  • The scenes with procedural geometry (grass, sea, etc.) did not render, even if they were hidden.
  • The command line option “-removegpus” didn’t work as intended.
  • No tiling texture option still produced tiling in the negative direction of the UV axis.
  • Non-coherent shading on 2 BSDFs on the same additive layer.
  • Maxwell crashed if Fire GPU was active when we apply a material with a coating.
  • A spotlight rendered with GPU could show a black hexagon in the light direction.
  • Dielectrics materials don’t behave as intended in some scenes.


  • New search boxes to filter the content of the object, camera and material lists. This helps to find particular items by name in these potentially long lists.
  • New button next to the object search box to restrict the viewport selection only to the items that match the search. The rest of the objects won’t be selectable until the search is cleared or the button un-pressed.
  • New Substance Painter assistant; now you can easily create a Maxwell material from the textures generated by Substance Painter.
  • Now, when pressing the Maxwell Cloud button, Studio checks which is the active camera so that’s the one rendered.
  • The CPU priority was not loaded properly from the MXS file.
  • Cloned objects that had blocked emitters broke the blocked emitters' behavior (the emitters could not be unblocked).
  • Adding or removing blocked emitters to an object was not refreshing FIRE.
  • Random crash starting Maxwell Studio.
  • When you created a new MaxwellGrass modifier, the existing ones were reset to default values.
  • The Studio animation tool should add padding to the output files too (image name and MXI name).
  • Studio move/rotate/scale gizmos didn’t highlight the active axis on mouse hover.
  • The hidden camera and locked camera icons were wrong.
  • Projection properties in the texture picker were not showing in the preview anymore.
  • In some cases, it was not possible to change the Field Type of the MaxwellVolumetric.
  • Studio could crash opening a scene when the current scene has a camera selected.
  • Wrong FIRE update when moving the UV set.
  • The Resources Browser can potentially make Studio crash on widget resize.
  • Studio won’t work on a remote desktop (Linux host).


  • New Substance Painter assistant; now you can easily create a Maxwell material from the textures generated by Substance Painter.


  • Now the users can override Extra-sampling and Denoiser parameters before sending a job to Maxwell Cloud.
  • The login dialogue had a dark background that made it hard to locate the different fields; now it is improved.
  • Now the users can set Maxwell Cloud to save outputs only at the end, saving render time.
  • Some warning messages changed in MacOS for clarity’s sake.
  • Getting dependencies of a MXM reference failed if the MXM was not found.
  • The “request preview” button in mxnetwork local mode didn’t work.
  • When sending a job from a Mac to a PC the job showed on the node as received but nothing else happened.
  • Maxwell Cloud spent too much time saving intermediate results in some heavy renders.


  • The following C++ SDK methods clamp input RGB values to a valid range:
    • Cmaxwell::Cmaterial::setColorID
    • Cmaxwell::CmaterialEmitter::setPair
    • Cmaxwell::Creflectance::setAttribute
    • Cmaxwell::Cobject::setColorID
    • Cmaxwell::Cenvironment::setSunProperties
    • Cmaxwell::Cenvironment::setSkyConstant
  • Python module pymaxwell5 returns MXparamListRef instead of MXparamList objects in the following methods:
    • CmaxwellCamera.getCameraLensExtensionParams
    • CmaxwellMaterial.getMaterialModifierExtensionParams
    • CmaxwellObject.getGeometryLoaderExtensionParams
    • CmaxwellObject.getGeometryProceduralExtensionParams
    • CmaxwellObject.getGeometryModifierExtensionParamsAtIndex
    • CmaxwellObject.getCustomDataChunkByName
    • CmaxwellObject.getCustomDataChunkAtIndex
  • New MXparamListRef class has the same functionality as MXparamList, plus getCopy(), which returns a MXparamList copy of the MXparamListRef object.
  • MXparamlist create/set methods’ input parameters updated to const.
  • Python module pymaxwell5 callback mwcallback now is mwcallback_cb.
hardware question :)

I can easily create an usable render in 15/20 mi[…]

Maxwell for Rhino on Max missing Toolbar

Hello, For some reason, the Mac version of Rhino[…]

Let's talk about Maxwell 5.2

Price for sure matter a loot. Speed is the core i[…]

Materials translucent with V5.1

Well, the problems can be in the chair, the monito[…]