Blog

ANIMA 4.0.3 UPDATE | 30/06/2020

• DOWNLOAD Installer (630 Mb)
   

NEW FEATURES:

• anima®: Improved the compatibility of the application in an environment that uses very long file paths (+256 chars).

• anima® plugins: Improved the load scene times on 3ds Max® and Cinema 4D®.
   

BUG FIXING:

• anima®: Fixed an issue where the assets displayed as a bounding box in anima® were incorrectly exported in T-pose to FBX, VrScene, or Collada.

• 3ds Max®: Fixed an issue where the normals of the meshes could be wrong when rendering animations using render nodes.

• 3ds Max®: Fixed an issue where the normals of the 4D models could be displayed incorrectly in the UV seams when using V-ray.

• 3ds Max®: Fixed a stability issue with Octane and 4D characters.

• Cinema4D® Plugin: Fixed an issue where the alive™ connection would lock any animated cameras present in the Cinema4D scene.

• Cinema4D® Plugin: Fixed material conflicts when multiple shaders were applied to the same mesh selection tags on custom actors.

• UE4® Plugin: Fixed an issue where you could get UE4 to crash when importing an asset that was already present in the scene.

• UE4® Plugin: Fixed an issue with packages including 4D models made on UE 4.25.

• Maya® Plugin: Fixed incorrect texture and normal updates in 4D actors.
   

KNOWN ISSUES:

• anima®: The VrScenes exported from anima® have an issue with their textures in the latest V-ray versions. ChaosGroup® has confirmed to us that they have already made a bugfix for this problem and it will be included in their next releases of both V-ray Next® and V-ray 5®.

• 3ds Max®: The 4D models explode in the viewport when using the IPR (interactive render) on multiple renderers, but this is only a cosmetic problem as it does not affect the final render and is automatically corrected when the IPR stops. In Corona, this problem is also visible int he interactive render, but this has been confirmed by the Corona developers to be caused by a bug on their side that they plan to fix in a future version.

• 3ds Max®: Displaying the 4D models as arrows may lead to instabilities on some render engines.

• Cinema4D® Plugin: The 4D models don't have Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. We have reported the problem to Maxon but there are no plans to solve this yet.

• Cinema4D® Plugin: The IPR mode from V-Ray does not show textures on the models. We are talking with ChaosGroup to find a solution to this problem.

• Maya® Plugin: The renderers supported by now on Maya® are Arnold, Redshift, and V-ray. Octane renderer will be added soon.

• Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-ray.