Chaos
Back to Chaos website Try Buy
Important Notice: Due to a high volume of inquiries, our response times may be delayed. We apologize for this, and appreciate your patience as our team works diligently to address your concerns. Thank you for your understanding! If you are experiencing licensing issues related to the Enscape 4.1 release, please visit our detailed FAQ document here
  1. Chaos Help Center
  2. FAQ
  3. Product Articles
  4. Corona
  5. Corona - General
  6. Corona Render Engine

Known bugs and limitations

Updated

This article lists bugs and limitations in Corona which we are aware of, and which we are planning to fix in the future. If you have encountered any of the issues listed below, there is no need to report it to us.

 

For bugs and limitations related to volumetric FX (Phoenix FD, FumeFX, CoronaVolumeGrid, CoronaVolumeMtl), see this separate article.

 

 

Known Bugs / Problems

Light transport issues
These issues are some of the most commonly encountered by the users, yet they are extremely hard to fix for our development team. Corona is intended for realistic, physically-based rendering, and the following issues usually appear if non-physical ("fake") properties are used for objects and materials. Such properties include, but are not limited to:

    • Refractive materials with disabled caustics
    • Objects which do not cast shadows
    • Lights with the "emit light" option disabled

Sometimes "black highlights" or other artifacts may appear on objects with reflection glossiness level lower than 1. Example cases:

"Black highlights"
Black reflection of sunlight may be visible on materials with glossiness lower than 1, if sunlight is passing through a Corona Light material with the "emit light" option disabled:

Correct result - the plane uses a Corona Light material with the "emit light" option enabled:
lightmtl-correct.jpg

emit-light.png


Incorrect result - the plane uses a Corona Light material with the "emit light" option disabled:
lightmtl-wrong.jpg

emit-light-off.png

 

Issue example in a scene - the black highlight appears on the flower pot. This is caused by sunlight passing through a "background plate" object using a Corona Light Material with "emit light" option disabled: 

SH_Zendesk.jpg

 

The workaround, which in some cases may help get rid of this issue, is using two different versions of a Corona Light Material with a Rayswitch Material: https://forum.corona-renderer.com/index.php?topic=32357.msg181607#msg181607 

 

 

Other issues

  • Transparent materials seen through global volume material (volumetric fog) may look incorrect.
    Solution: increase the Enviro distance value in Development/Experimental Stuff rollout (3ds Max | C4D).

    fog-op.jpg
 
  • Volumetric effects are only taken into account with the Base Material of Corona Layered Material
    When using the Corona Layered Material, subsurface Scattering/volumetric scattering effects are only taken into account when used in the base layer. Otherwise, the effects are ignored.
  • Material Library 
    Undo history (moving, scaling, rotating, changing properties, etc) is cleared after dragging and dropping a material from the library onto any scene object in the viewport. Using the undo icon or pressing Ctrl+Z will only undo the most recent action, which is assigning the material to the object.
    This is a 3ds Max issue, and it appears in the native material editor as well. An example report about it from 2008 can be found on the Autodesk forums. 

 

Interactive Rendering Limitations

  • Resetting the scene or closing 3ds Max during rendering (regular or interactive) may sometimes cause a crash. This is a 3ds Max limitation, and we do our best to prevent it, however, we cannot guarantee 100% stability.

  • Multitexture in BerconTile mode is not supported.
  • 3ds Max atmospheric effects - using them while IR is running may lead to instability (lags, freezing, incorrect output).
  • The velocity render element cannot be previewed in the interactive rendering VFB.

 

 

Known Limitations and Unfinished Features

  • Starting with Corona 12, when using 3ds Max batch rendering:
    • Canceling the rendering using the 3ds Max "Batch Render in Progress" window leads to saving of the main output file and all render elements. In case of saving to CXR format, each render element is a copy of the main output file with all additional information included. This can lead to consuming large amounts of disk space.
    • Canceling the rendering from the Corona VFB works as expected - no data will be saved. 
    • Stopping the rendering from the Corona VFB works as expected - it will stop rendering and save the current progress (main output and render elements). 
  • [3ds Max] Falloff map in Shadow/Light mode is not supported:

    sh-li2.jpg
  • [3ds Max] "Lock sampling pattern" option does not work when using Corona's distributed rendering.

  • [3ds Max] Multi/Sub-Object material is currently not supported when nested inside Blend, Double-sided, and Top/Bottom materials

  • [3ds Max] Particle Motion Blur Map (Particle MBlur) is not supported. It may render incorrectly or cause crashes.
    Solution: use Corona's native motion blur with particles - it should not introduce a significant speed penalty.

  • Geometry Motion Blur does not work for geometry with changing topology (changing number of faces, vertices, or normals).

  • Motion Blur does not work on objects scattered with Chaos Scatter.

  • Corona AO (Ambient Occlusion) map cannot be used in Chaos Scatter (for example as a distribution mask). This is because Corona AO can only work during the rendering, and using it as a mask for Chaos Scatter would require it to work before the rendering is started.


  • There are differences between how geometry is created with different 3ds Max versions. Currently, we are aware of Teapot and Circle objects (differences between 3ds Max 2019 and 2020) and Sphere object (differences between 3ds Max 2016 and 2017). This may result in Chaos Scatter rendering differently in different versions of 3ds Max if instances are scattered on those offending objects (and possibly some other object types which we have not identified yet).

    Some cases where this can happen include:
    • Opening a scene created with an older version of 3ds Max in a newer version of 3ds Max and re-rendering (the scattering may be different, for example, the instances may be aligned in a different pattern).
    • Rendering a scene using distributed / network rendering where some render nodes are running an older version of 3ds Max and some nodes are running a newer version of 3ds Max (in this case different computers may render different scattering, which can result in scattered objects appearing and disappearing in animations or showing half-transparent). 
      Note: it is generally not recommended to mix different versions of 3ds Max when using distributed / network rendering!


Possible workaround: open your scene in the version of 3ds Max it was originally created in, convert the offending objects to editable poly, save your scene, and only then re-render it with the newer version of 3ds Max.
Note: unfortunately this is a 3ds Max-related issue, so we might never be able to guarantee identical rendering between different versions of 3ds Max.

Chaos Scatter Issues

For a list of Scatter issues and performance troubleshooting, see:

 

  • Corona MultiMap cannot be used with the 3ds Max native BlendedBoxMap (only one map will be projected onto all axes).
    Solution: use the Corona TriplanarMap instead of the 3ds Max BlendedBoxMap.

  • Corona EXR (.CXR) is not supported by some 3rd party software and service providers. It may not work properly with region/tile/strip rendering.

  • 3ds Max native photometric lights do not scale well with multi-processor systems and therefore may introduce a significant performance drop.
    Solution: remove the photometric lights, or replace them with Corona lights.

  • It is not recommended to use objects, modifiers, or materials that are native to other renderers than Corona, unless they are officially listed as compatible - this can lead to hard-to-diagnose problems, even if initially everything appears to work correctly.

  • Itoo ColorEdge is no longer supported by developers and frequently causes 3ds Max crashes.

  • The message “Error Creating File Output”: caused by 3ds Max bug that adds non-existing paths to render elements.
    Solution: go through your render elements and delete all non-existing output paths, or fix render element paths in the asset tracker (Shift+T).

    render_elements_bug.png

Was this article helpful?
2 out of 3 found this helpful

Articles in this section

See more