anima® 5.6.1
Release | 30/01/2025
NEW FEATURES:
- Unreal Engine® Plugin: Added support for Unreal Engine 5.5
- Cinema4D® Plugin: Added support for Cinema 4D 2025
BUG FIXING:
- 3ds Max® Plugin: Fixed scene offset in 3ds Max when different scenes had different offsets.
- Unreal Engine® Plugin: Improved stability for Unreal Engine 5.4
- Unreal Engine® Plugin: Improvement of character drop stability in Unreal under certain exceptional circumstances.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- anima® Render Node: Edited actors appear as “Missing Actors” when rendered from Render Node installations.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: A low percentage (>15%) of random startup crashes may still happen when Tyflow is present on the system and the extra CUDA libs package is also included. If the CUDA libs are not present the crashes won’t happen.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
- Unreal Engine® Plugin: The installer may not detect the root path of Unreal Engine 5.2 or newer because Epic has removed the registry entries that pointed to that path. Therefore, the user might need to select the plugin manually on the anima® installer options and specify the root path of the UE installation.
anima® 5.6.0
Release | 01/08/2024
NEW FEATURES:
- anima® Render Node: Render nodes are now FREE and do not require any license!
- anima®: Updated EULA and license terms.
- anima®: Purchasing assets is no longer available in anima® Lite.
- Unreal Engine® Plugin: Support for Unreal Engine 5.4.3 with raytracing.
- Unreal Engine® Plugin: Some minor enhancements for the Unreal Engine plugin.
BUG FIXING:
- 3ds Max® Plugin: Fixed issues with Redshift
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- anima® Render Node: Edited actors appear as “Missing Actors” when rendered from Render Node installations.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has already been reported to Chaos, the other renderers work fine in the same situation.
- 3ds Max® Plugin: A low percentage (>15%) of random startup crashes may still happen when Tyflow is present on the system and the extra CUDA libs package is also included. If the CUDA libs are not present the crashes won’t happen.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by Chaos, it is not caused by anima®.
- Cinema4D® Plugin: Version R26 may freeze when scrubbing the timeline and rendering using the interactive live-view window if the scene includes 4D models. This same situation works fine in C4D 2023, so it is possible that this is caused by a Redshift/C4D bug that has been fixed in the new version.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
- Unreal Engine® Plugin: The installer may not detect the root path of Unreal Engine 5.2 or newer because Epic has removed the registry entries that pointed to that path. Therefore, the user might need to select the plugin manually on the anima® installer options and specify the root path of the UE installation.
- Unreal Engine® Plugin: In version 5.4, the plugin is unstable due to structural problems related to the new Threading system implemented by Epic in this new series (5.4.x), which are causing a lot of crashes the UE plugins that use their rendering API, as anima does. The issues have been reported to Epic and we are waiting for their answer. Until then, our recommendation is to revert to UE 5.3 for production projects using anima®, since, for reasons beyond our control, we cannot ensure plugin stability in version 5.4.
anima® 5.5.0
Release | 26/06/2024
NEW FEATURES:
- anima®: Improved information for 4D characters.
- 3ds Max® Plugin: Support added for 3ds Max 2025.
- 3ds Max® Plugin: Animation can now be offset in time and animated with keyframes.
- 3ds Max® Plugin: Time range can be modified at any point, including the initial time..
- 3ds Max® Plugin: Enhanced texture updating for 4D characters.
- 3ds Max® Plugin: Material rebuild now affects dropped actors.
- Cinema4D® Plugin: Time range can be modified at any point, including the initial time.
- Cinema4D® Plugin: Improved camera synchronization.
- Unreal Engine® Plugin: Support for UE 5.4 (with known issues!).
- Unreal Engine® Plugin: Advanced LOD configuration in project settings.
- Unreal Engine® Plugin: Significant performance improvements.
- Unreal Engine® Plugin: 4D characters’ animation duration can be retrieved from blueprints.
- Unreal Engine® Plugin: Reset animation to any time can be called from blueprints for 4D characters.
- Unreal Engine® Plugin: Changeable time multiplier for 4D characters.
- Unreal Engine® Plugin: Decals are not longer affecting 4D characters.
- Maya® Plugin: Support added for Maya 2025.
- Pixotope® Plugin: Support for version 23.4.
BUG FIXING:
- anima®: Corrected wrong behavior on actors when setting variations.
- anima®: Prevented the use of the same path for the purchases folder and project path.
- anima®: Fixed issues with importing models containing Chinese characters.
- anima® Plugins: Resolved issue of missing actors on duplicated subscription assets.
- anima® Plugins: Fixed issue where duplicated subscription assets did not work if the parent was not used.
- anima® Plugins: Fixed problem when setting a large number of variations.
- anima® Plugins: Anima Drop Library now properly updates when models are downloaded from it.
- 3ds Max® Plugin: Fixed crash when saving a scene after adding and removing a Drop model.
- 3ds Max® Plugin: Resolved animation issue with frozen 4D characters.
- 3ds Max® Plugin: Fixed random startup crash when Tyflow was present on the system.
- Cinema4D® Plugin: Added support for C4D 2024 network render.
- Cinema4D® Plugin: Fixed issue causing missing actors not to render.
- Cinema4D® Plugin: Resolved hang issue when creating and synchronizing a new scene under certain conditions.
- Cinema4D® Plugin: Fixed unresponsive UI after canceling import operations.
- Cinema4D® Plugin: Resolved minor UI issues.
- Unreal Engine® Plugin: Fixed time offset problems.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- anima® Render Node: Edited actors appear as “Missing Actors” when rendered from Render Node installations.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has already been reported to Chaos, the other renderers work fine in the same situation.
- 3ds Max® Plugin: A low percentage (>15%) of random startup crashes may still happen when Tyflow is present on the system and the extra CUDA libs package is also included. If the CUDA libs are not present the crashes won’t happen.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by Chaos, it is not caused by anima®.
- Cinema4D® Plugin: Version R26 may freeze when scrubbing the timeline and rendering using the interactive live-view window if the scene includes 4D models. This same situation works fine in C4D 2023, so it is possible that this is caused by a Redshift/C4D bug that has been fixed in the new version.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
- Unreal Engine® Plugin: The installer may not detect the root path of Unreal Engine 5.2 or newer because Epic has removed the registry entries that pointed to that path. Therefore, the user might need to select the plugin manually on the anima® installer options and specify the root path of the UE installation.
- Unreal Engine® Plugin: In UE versions 5.4.2, 5.4.1, and 5.4.0, the 4D models won’t cast shadows or appear in reflections when Raytracing is enabled. This is caused by a bug in UE that has been acknowledged by Epic and will be fixed in the next update of UE (5.4.3) that is planned to be released soon.
anima® 5.2.0
Release | 16/10/2023
NEW FEATURES:
- Pixotope® Plugin: Added support for the Pixotope virtual production package.
- 3ds Max® Plugin: Significantly enhanced performance during material rebuilding in very large scenes.
- 3ds Max® Plugin: Improved V-Ray and Arnold material handling.
- Unreal Engine® Plugin: Added support for versions UE 5.2 and UE 5.3.
- Cinema4D® Plugin: Added support for C4D 2024.
- Maya® Plugin: Integrated support for 2024 in the command-line deployment tool.
BUG FIXING:
- anima®: Resolved issues within the bone matcher tool.
- anima®: Addressed a crash occurring when using alive™.
- anima®: Mitigated a potential crash during the interface redraw of the root object.
- 3ds Max® Plugin: Resolved an issue preventing users from creating a drop scene more than once within the same project.
- 3ds Max® Plugin: Fixed a crash that occurs when opening a scene via command line.
- 3ds Max® Plugin: Addressed issues experienced when canceling the drop in Max using any button other than the right mouse button.
- 3ds Max® Plugin: Fixed issues occurring when Drop models are downloaded and dropped into Max simultaneously.
- 3ds Max® Plugin: Corrected the application of material conversion to non-loaded drop characters.
- Cinema4D® Plugin: Resolved issues with using dropped characters that share the same model but are in different phases.
- Cinema4D® Plugin: Fixed potential crash when loading a c4d file that contains an aniproj that has been modified externally.
- Unreal Engine® Plugin: Fixed a potential crash that may occur when reimporting the same scene.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- anima® Render Node: Edited actors appear as “Missing Actors” when rendered from Render Node installations.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has already been reported to Chaos, the other renderers work fine in the same situation.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by Chaos, it is not caused by anima®.
- Cinema4D® Plugin: Version R26 may freeze when scrubbing the timeline and rendering using the interactive live-view window if the scene includes 4D models. This same situation works fine in C4D 2023, so it is possible that this is caused by a Redshift/C4D bug that has been fixed in the new version.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
- Unreal Engine® Plugin: The installer may not detect the root path of Unreal Engine 5.2 or newer because Epic has removed the registry entries that pointed to that path. Therefore, the user might need to select the plugin manually on the anima® installer options and specify the root path of the UE installation.
anima® 5.1.1
Release | 15/05/2023
HOTFIX:
- anima® Core: Fixed a rare compatibility bug that caused some of the core DLLs of anima® to crash when executed by a subset of AMD Ryzen™ processors.
anima® 5.1.0
Release | 10/05/2023
- DEPRECATED (has issues with some AMD processors)
NEW FEATURES:
- anima®: It is now possible to duplicate and modify subscription assets however you like! Simply duplicate the asset in your project and start editing it as normal. Keep in mind, however, the original asset must be installed and available to keep using the modified resource. Only the changes you applied are saved to the file stored in your project’s libraries.
- anima®: New animated thumbnails will now be displayed for assets from the online store! Simply hover the mouse over one of them and it should play a short animation if a preview is available. This should allow you to see more easily what kind of animation the product you’re about to download has.
- anima®: You can now select the size of the thumbnails in the actor panel. Simply right-click and select the size you want or you can even use the Control key and the Mouse wheel to adjust it.
- anima®: The search engine from the online store has been integrated into the actor panel! You can now type different terms and get search suggestions to more easily find what you’re looking for. This should be very helpful for anima All users to filter and find the asset they need.
- anima®: It’s now possible to configure the time it takes for actors to be teleported to the start of a path when they reach the end by using the new reset time slider.
- anima®: The sign-in dialog now has a new toggle to show or hide the user’s password to help look for typing errors.
- anima® Plugins: The plugins can now display a special model to indicate an access error has occurred when reading from 4D resources when the source of the project itself is unable to be reached. This should be helpful in determining if rendering errors have occurred due to networking issues.
- anima® Plugins: Project packing performance has been improved by skipping unnecessary duplication of the resource cache when preparing the projects to be sent to render farms.
- anima® Commandline License: Extra information has been added to the device list function.
- 3ds Max® Plugin: Duplicated drop characters can be a copy instead of an instance only and they can be converted to anima® scene.
- 3ds Max® Plugin: Improved compatibility of the 4D models with Chaos Vantage (V-Ray 6.10.06 or newer required).
- 3ds Max® Plugin: Added support for 3dsMax 2024.
- Maya® Plugin: Added support for Maya 2024.
BUG FIXING:
- anima®: The application will now correctly offer again to activate an anima all subscription when signing in again if the message was ignored before.
- anima®: Fixed a small issue where it was not possible to edit sliders with double markers under certain conditions.
- anima®: Fixed various regressions regarding the tall chair functionality compared to the previous version.
- anima®: Fixed an error where the IK would lag behind incorrectly on shorter actors like children when running.
- anima®: Fixed a crash when attempting to change a background’s properties while another scene without a background was open.
- anima®: Fixed a rare crash that could occur when unlocking certain baked scenes under the right conditions.
- anima®: Fixed a rare crash that could occur when playing back and scene and recording a preview until the very end.
- anima®: Fixed an error where rigged actors would have a tendency to look too much at one side while walking.
- anima®: Fixed an error where an anima directory would be created in the documents directory even if the configuration for the default project and purchases path has already been defined.
- anima®: Fixed an error where applying bake to one scene would not correctly update the project tree to match if multiple scenes were open.
- anima®: Fixed a rare crash that could occur when trying to move the timeline of a 4D asset being played back in library mode into the negative range.
- anima®: Fixed a very rare crash that could occur when dropping multiple templates into the viewport due to undefined behavior of the project tree view.
- anima®: Fixed the actor preview looking corrupted in D3D9 when the asset is locked due to an offline subscription.
- anima®: Fixed an issue where the CPU thread counts for the simulator would not default to the correct value on the first configuration, causing reduced performance. Please review your simulator threads configuration to be at the right setting if you have run into a problem.
- anima® Render Node: Fixed an error where the purchases path would not be indexed correctly on render nodes.
- anima® Render Node: Fixed an error when attempting to create the configuration directory on the new AppData path for the render node and render node manager applications.
- anima® Render Node: Fixed an error when creating the configuration directory on the new AppData path where the organization name would be used incorrectly.
- animaDrop®: Fixed a rare crash that could occur when downloading actors purchased from the store directly.
- 3ds Max® Plugin: Better performance when 4D character textures are shown as yellow textures in the viewports (colored texture).
- 3ds Max® Plugin: Fix character drop issues when multiple projects were opened on a single session.
- 3ds Max® Plugin: Fixed support for 3dsmaxbatch.exe.
- Cinema4D® Plugin: Fixed issues when the anima® import object is not the first object on the library tree.
- Cinema4D® Plugin: Fixed rendering issues when 4D character textures are not shown in the viewport.
- Cinema4D® Plugin: Fixed a wrong error message in animaDrop® when no actor is selected.
- Cinema4D® Plugin: Fixed redshift masked materials.
- Cinema4D® Plugin: Fixed a problem with the transforms of the actors when converting Drop models to anima scene.
- Cinema4D® Plugin: Fixed the support of rendering when the main software is in a separate thread and window.
- Cinema4D® Plugin: Fixed a rare case where the 4D texture was not updated properly if the character was shown as an arrow in the viewport.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has been already reported to ChaosGroup, the other renderers work fine in the same situation.
- 3ds Max® Plugin: When using MentalRay or iRay, the walking models appear as walking in place. The support for these renderers was discontinued since version 5, so this won’t be fixed.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Cinema4D® Plugin: Version R26 may freeze when scrubbing the timeline and rendering using the interactive live-view window if the scene includes 4D models. This same situation works fine in C4D 2023, so it is possible that this is caused by a Redshift/C4D bug that has been fixed in the new version.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 5.0.2
Release | 18/01/2023
NEW FEATURES:
- anima®: User configuration has been moved from the “My Documents” directory to “%LOCALAPPDATA%/anima”. This should provide higher compatibility with systems that use this directory with protection or synchronization software that could cause problems during runtime. However, anima will keep suggesting creating the default Projects and Purchases directory under “My Documents” just like always for the users who wish to take advantage of that functionality.
- anima®: The visual scene tree has been revamped completely internally to provide a much faster response time and decrease loading times significantly on projects with large amounts of actors.
- anima® Commandline License: Two new actions are now available for anima all administrators. It’s now possible to retrieve the active list of devices and export it to a JSON or CSV file. You can also delete devices registered to an anima all subscription.
- Unreal Engine® Plugin: Added support for Unreal Engine® 5.1
BUG FIXING:
- anima®: Fixed a crash when using the crowd generator on a table object.
- anima®: Fixed an issue where attempting to switch to shop mode and canceling the operation would make the mode switcher display the active mode incorrectly.
- anima®: Fixed an error where opening a scene with baked actors that had no skeletons associated with them that were saved with older anima versions could cause an infinite loading loop.
- anima®: Fixed an issue where the resource cache would not update correctly when saving the project if automatic updates through anima alive were disabled.
- 3ds Max® Plugin: Fixed a rare crash when opening anima scenes that could occur due to an internal 3DS Max bug that was present in versions 2016 and below.
- Cinema4D® Plugin: Fixed an error when using drop characters in C4D R26/2023
- Cinema4D® Plugin: Fixed an application freeze when using 4D models and Redshift in C4D R26/2023
- Unreal Engine® Plugin: Fixed an error where walking 4D actors would not ignore the global virtual texture project setting as they should, resulting in grey materials.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has already been reported to ChaosGroup, the other renderers work fine in the same situation.
- 3ds Max® Plugin: When using MentalRay or iRay, the walking models appear as walking in place. The support for these renderers was discontinued since version 5, so this won’t be fixed.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Cinema4D® Plugin: Version R26 may freeze when scrubbing the timeline and rendering using the interactive live-view window if the scene includes 4D models. This same situation works fine in C4D 2023, so it is possible that this is caused by a Redshift/C4D bug that has been fixed in the new version.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 5.0.1
Release | 04/11/2022
NEW FEATURES:
- anima®: You can now filter which actors are usable by the 3D scene exporter by typing “Exportable” into the search bar.
- anima®: The “Keep positions and orientations” option inside paths and areas has been reworked into a new “Randomize Actors” button next to the “Generate” button.
- anima® Exporter: The FBX SDK has been updated and you can now choose to use the latest FBX versions for higher compatibility with newer applications.
- animaDrop®: The download progress text that shows the speed and the remaining bytes has been added just like in the main application.
- 3ds Max® Plugin: Removed legacy Mental Ray attributes.
- 3ds Max® Plugin: Added support for native V-Ray and Corona Bitmaps.
- 3ds Max® Plugin: Added support for scaling prior to transforming drop models to regular scenes.
- Cinema4D® Plugin: Added support for scaling prior to transforming drop models to regular scenes.
BUG FIXING:
- anima®: Numerous performance improvements have been made to the crowd generation on paths or areas.
- anima®: Fixed a very rare crash that could happen under certain circumstances when editing some parameters of the UI or switching to Edit Mode.
- anima®: Fixed an error where an actor would choose the incorrect sitting clip if a sitting clip is used in its Idle category and the actor is not currently attached to a chair. This issue also affected a feature where dragging a sitting clip on top of a standing actor would not apply it correctly.
- anima®: Fixed an issue where the project exporter would crash if purchased resources were included in the package.
- anima® Exporter: Fixed an issue with the Blender preset for the FBX exporter not working correctly. A new option has been added to insert a root bone for the skeletons to fix this compatibility issue.
- anima® Plugins: Fixed an issue where a scene would crash if two 4D actors were linked together and the scene was baked.
- Commandline Deploy: Fixed an issue where an older 3DS Max version that is no longer available showed up as an option.
- 3ds Max® Plugin: Fixed an issue where it was not possible to keep the phase of the 4d characters when they are transformed into a regular scene.
- 3ds Max® Plugin: Fixed an issue where the animated subscenes did not update correctly the normals of the child 4D and Rigged actors if they had their rotation animated.
- 3ds Max® Plugin: Fixed an issue where, when multi-scenes have a transform applied, on the first frame of the sequence the Ready Posed and Ambient models keep the previous position of the timeline.
- 3ds Max® Plugin: Phase on 4D characters has been greyed out on Render Node to better display that it cannot be modified.
- 3ds Max® Plugin: Fixed an issue where the scale applied to the actors in anima® Designer was not correctly read and applied during the import process.
- Cinema4D® Plugin: Fixed an error where the plugin for Cinema 4D R19 wouldn’t start correctly.
- Cinema4D® Plugin: Fixed numerous issues caused by the new multi-threaded design present in Cinema 4D R26 and 2023.
- Cinema4D® Plugin: Fixed an issue where the phase of the 4d characters was not kept when they were transformed into a regular scene.
- Cinema4D® Plugin: Fixed an issue where the scale applied to the actors in anima® Designer was not correctly read and applied during the import process.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has already been reported to ChaosGroup, the other renderers work fine in the same situation.
- 3ds Max® Plugin: When using MentalRay or iRay, the walking models appear as walking in place. The support for these renderers was discontinued since version 5, so this won’t be fixed.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Cinema4D® Plugin: Versions 2023 and R26 may freeze when using Redshift with 4D models. We are working to fix this issue on the next release.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 5.0.0
Release | 03/10/2022
NEW FEATURES:
- anima®: Brand new crowd simulation engine powered by a neural network that has been trained with thousands of hours of motion capture data! Actors will now show much more realistic behavior when interacting with each other and when traveling across different types of surfaces. A wide variety of improvements have been made to the simulator across the board.
- anima®: Walking 4D actors are now available! Enjoy the benefits of volumetric captures that can loop seamlessly and walk over any path you wish on your scene. These characters can also avoid each other to prevent collisions. Use these actors to their full potential by bringing them closer to your camera and showcasing their realistic motions and clothing deformations.
- anima®: You can now make any path a closed loop. This will prevent actors from teleporting at the edges of the path, which can be useful depending on the needs of your project.
- anima®: Numerous optimizations have been made across the board to the application, reducing loading times drastically for anima ALL users or just users with lots of purchased models.
- anima®: The dock visibility buttons and the workspace settings have been merged into a single panel next to the account button.
- anima®: The camera list that can be opened inside a scene now supports scrolling if there are a lot of cameras to choose from.
- anima®: A new lightweight IPC service has been introduced to enhance the communication between anima and supported plugins. This also has the benefit of supporting multiple anima instances being connected to different anima plugins at the same time.
- anima®: The resource cache “Read from file” option has been extended with various improvements to allow working with plugins or multiple users in a network without running into file access errors. The resource cache will now write to a temporary file any changes it wishes to save if the file is not available for modification and the changes will be merged the next time the file can be opened for writing. This should allow users to work on the same project that another application is currently rendering from without having to rely on the “Keep in RAM” feature.
- anima®: The background importer has been improved to automatically detect duplicate meshes to reduce the size of the background files significantly if the source geometry does not feature instancing. This should result in a significant optimization for any backgrounds that feature heavily duplicated geometry.
- anima®: You can now edit the visual scale of actors. You can also edit their orientation values directly instead of using the single Y axis rotation that is available on the simple rotation mode. Please note that some file formats or applications might not support non-uniform scaling correctly when modifying this property in rigged characters.
- anima®: The configuration file behavior has been improved and all changes a user makes will be instantly saved whenever an option is changed. The changes will also be visible instantly in other applications that support changing these preferences. This allows multiple anima applications to be used without overwriting each other’s preferences when quitting.
- anima® Plugins: The anima® Drop panel has been upgraded to support a wide array of features in the same way anima does. It is now possible to browse and download new actors directly from the panel without having to go to anima to install them. You can even activate your anima ALL subscription directly from this panel without ever using the application, which makes it very convenient when used with compatible plugins.
- 3ds Max® Plugin and Cinema4D® Plugin: It is now possible to drag and drop ambient and 4D actors directly using the anima® Drop panel. The plugin will now create a hidden scene so it is possible to work with anima® Drop in a similar way to anima. You can convert this hidden scene to a regular anima scene at any point if you wish to do more extensive modifications to it.
- 3ds Max® Plugin and Cinema4D® Plugin: The plugin will now create parent objects for each scene that was imported from an anima Project, as it already happened before in Maya®, allowing for easy movement of the scenes and quick browsing of their elements.
- 3ds Max® Plugin: The plugin now supports dropping and placing actors and updating them automatically once they are installed, just like in anima. A placeholder arrow mesh will be shown while the product is being downloaded.
- Cinema4D® Plugin: Added support for C4D 2023.
BUG FIXING:
- anima®: Fixed an error where anima would unnecessarily load other resources used in the project even if the scenes were not opened when saving a scene for the first time.
- anima®: Fixed an error where locked ready-posed and stream actors would save useless information on the frame blocks when baking the animation.
- anima®: The registry key for the user’s configuration has been changed. The installer will migrate any relevant variables from ‘anima 2’ to just ‘anima’.
- anima®: Improved the behavior of automatic reconnections for anima ALL users after suspending the system while the application was running or disconnections during extensive sessions.
- anima®: Fixed an error where 4D characters would be unable to continue playback if they encountered a file reading error during streaming. The application will now reattempt to open the stream in these cases.
- anima®: Various minor user interface issues to improve the general experience.
- anima®: Fixed an error where actors would slightly reposition themselves after being dragged and dropped inside the viewport.
- anima® Plugins: Fixed an error where Plugins with different versions than anima could be used together, leading to undefined behavior. The plugins will now check properly and show an initialization error if the version of the Plugin and the version of anima have API differences that make them incompatible.
- anima® Plugins: Fixed an error where the Plugin would not attempt to re-authenticate correctly to the anima ALL service if the session was disconnected.
- anima® Plugins: The render farm packing functionality will now prompt for an error if the required resources for rendering are somehow missing from the resource cache, preventing incorrect submissions and render processes from being launched.
- Maya® Plugin: Fixed the texture issues on 4D models when using V-Ray to render animated sequences.
- Unreal Engine® Plugin: The materials created by the importer have been improved and will be less prone to compatibility errors between Unreal Engine versions.
- Unreal Engine® Plugin: Fixed various issues that could appear when re-importing scenes from anima. The naming scheme used by the importer should now be more consistent and less prone to errors.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly at the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has been already reported to ChaosGroup, the other renderers work fine in the same situation.
- 3ds Max® Plugin: When using MentalRay or iRay, the walking models appear as walking in place. The support for these renderers was discontinued since version 5, so this won’t be fixed.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping of the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 4.5.6
Release | 31/05/2022
NEW FEATURES:
- anima®: Various improvements to the account notifications panel.
BUG FIXING:
- anima®: Various fixes and stability improvements.
- Unreal Engine® Plugin: The speed of the import process for scenes with rigged actors has been improved.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: The models from a subscription that are used from the Quick Drop panel are rendered as a degraded mesh in production renders made with V-Ray GPU (V-Ray standard works fine). This issue has been fixed in the V-Ray 5 update 2 (5.20.00).
- 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has been already reported to ChaosGroup, the other renderers work fine in the same situation.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 4.5.5
Release | 12/05/2022
NEW FEATURES:
- 3ds Max® Plugin: Added 3DS Max 2023 support.
- Cinema4D® Plugin: Added Cinema 4D R26 support.
- Unreal Engine® Plugin: Added Unreal Engine 5.0.1 support (Early Access and Preview versions are no longer supported).
BUG FIXING:
- anima® Plugins: Fixed a very rare crash that could happen under certain circumstances when building the internal resource list.
- Unreal Engine® Plugin: Fixed an issue where importing actors with skeleton animations would take a significantly longer time compared to previous Unreal Engine versions.
- Unreal Engine® Plugin: Fixed an issue where textures for anima actors would be imported as virtual textures incorrectly, breaking their material in the process.
- Unreal Engine® Plugin: Packaging projects is now supported on Unreal Engine 5 too.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: The models from a subscription that are used from the Quick Drop panel are rendered as a degraded mesh in production renders made with V-Ray GPU (V-Ray standard works fine). This issue has been fixed in the V-Ray 5 update 2 (5.20.00).
- 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has been already reported to ChaosGroup, the other renderers work fine in the same situation.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 4.5.4
Release | 09/03/2022
NEW FEATURES:
- anima® License Tool: A new command-line interface license tool has been added to the installer. This tool can be used to administer, activate or remove an anima PRO or ALL license from a device without needing to use the application. This tool should prove useful for system administrators or users who wish to activate anima on headless systems like render nodes.
- anima®: Multiple improvements to the filtering functionality and the consistency of the names displayed in the actor and clip libraries. The search filter will no longer include irrelevant information such as asset descriptions.
- anima®: The installer now supports more options when used from a command line.
- anima® Plugin: The velocity channel of the 4D actor will now be filled out correctly so compatible renderers can use that information to create a motion blur effect.
- anima® ALL: A new “render node” mode has been added for anima® ALL. It is now possible to render scenes from any of the pre-authorized devices from a subscription account without taking up a seat as long as the rendering is done on an instance of your 3D app that does not have a UI.
- Unreal Engine® Plugin: Added support for Unreal Engine® 5.0.0 Preview 2.
BUG FIXING:
- anima®: Fixed an error where the application would crash when trying to read corrupted asset files under certain circumstances.
- anima®: Fixed an issue where the application would crash when trying to update a corrupted resource cache in certain conditions.
- anima®: Fixed an error where an incorrect error message would be logged when a resource index didn’t exist.
- anima® Plugins: Fixed an error where a project extracted from a pack of a version previous to 4.5.0 would not open correctly when opening the .anipack file directly.
- anima® Plugins: Fixed an issue where the resource index would not be properly updated when opening a project, so any new assets that were installed while running would not show up correctly.
- 3ds Max® Plugin: Fixed an error where creating escalators could fail under certain circumstances.
- 3ds Max® Plugin: Fixed an error where the error message that appears when attempting to open a scene that doesn’t work correctly would not show up correctly in the message log of a network render.
- 3ds Max® Plugin: Fixed an error where the error message that appears when attempting to open multiple anima projects at the same time would not show up correctly in the message log of a network render.
- Cinema4D® Plugin: Fixed an error where the textures of some models were not properly restored from the anipacks generated using the anima® API script interface.
- Unreal Engine® Plugin: Fixed an error where the application would refuse to import the project if some assets that weren’t critical to the scene couldn’t be found.
- Unreal Engine® Plugin: Fixed an issue where the project would not be closed properly in memory after importing it.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it usually happens when the computer has installed an old version of the GPU driver, it should disappear after a proper update. An alternative workaround is to set the 4D texture decoding from GPU to CPU in the preferences of the anima® standalone app or in the Unreal Engine settings, in the anima® section.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: The models from a subscription that are used from the Quick Drop panel are rendered as a degraded mesh in production renders made with V-Ray GPU (V-Ray standard works fine). This issue has been fixed in the V-Ray 5 update 2 (5.20.00).
- 3ds Max® Plugin: When using Corona in interactive mode and 4D models, having the Maxscript MacroRecorder enabled may cause a crash if the current frame is changed by moving the timeline. This issue only happens with Corona and has been already reported to ChaosGroup, the other renderers work fine in the same situation.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: The support for version 5.0.0 Preview 2 is in the beta stage, keep in mind that it is not production-ready yet. For example, at this moment it is not possible to build packages in UE5 when the anima® plugin is enabled, that is why the plugin is disabled by default in this version. However, if you enable it in the project plugins section of UE, everything except the build package process should work as expected.
- Unreal Engine® Plugin: In version 4.27, the textures of the 4D models might disappear when using the STANDALONE GAME feature. This is a retro-compatibility bug that was introduced by Epic and can be fixed by recompiling and resaving the base material again (“Anima4D_material“, no modifications needed).
anima® 4.5.3
Release | 15/10/2021
NEW FEATURES:
- anima®: It is now possible to configure if an anima® plugin should stream assets directly from the project’s resource cache or if it should preload all their contents in memory using the new Keep in Ram option in the Project Preferences panel. With the latest resource cache update, it was not possible to keep working on a project and update its contents if an anima® Plugin or another system in the network was rendering it. By using this option, you can allow one or more applications to open the same project simultaneously, at the cost of extra memory usage in the systems that wish to render some of its scenes.
- anima® Plugins: The submission to render farm process has been improved and only the required resources for the scenes that are being rendered will be uploaded, resulting in an overall size reduction of the anima® project pack.
- Cinema4D® Plugin: Added support for Cinema 4D R25.
- Unreal Engine® Plugin: Added support for Unreal Engine® 4.27 and beta support for Unreal Engine® 5.0.0 Early Access 2.
BUG FIXING:
- anima®: Fixed an issue where a specific situation dealing with resource cache corruption would not be properly detected, leading to being unable to remove or update the corrupted assets.
- anima®: Improved the behavior of saving project files to avoid file corruption due to external reasons while writing to storage.
- anima®: Fixed an issue where the FPS option in the scene settings was configurable when it was unable to do any actual modifications to the framerate due to an active anima® alive connection.
- anima®: Improved speed on certain NAS configurations when opening old projects by creating an empty resource cache file first.
- anima®: Fixed an issue where the account or subscription information would be wiped from the registry when failing to connect and closing the application.
- anima®: Fixed an issue where the animation from the Ambient models would not be randomized correctly.
- anima®: Fixed an issue where the clip editor did not respond correctly to changes in the loop threshold or the category editor.
- anima® Plugins: The name of the quick drop feature has been made more consistent across all the Plugins.
- 3ds Max® Plugin: Corrected some issues and improved performance when detecting complex geometry in the quick drop mode.
- 3ds Max® Plugin: Fixed an issue where models downloaded from an anima® ALL would not show up correctly in Redshift and V-Ray GPU.
- Cinema4D® Plugin: Improved compatibility with OctaneRender Studio.
- Maya® Plugin: The plugin will now detect and warn you correctly when scenes with different modification dates are detected when compared to the version that was used to generate the Maya scene.
- Unreal Engine® Plugin: Fixed an issue where 4D assets would fail to extract properly if they were not installed in the system. The plugin will now request for the assets to be installed before proceeding.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: The models from a subscription that are used from the Quick Drop panel are rendered as a degraded mesh in production renders made with V-Ray GPU (V-Ray standard works fine). This issue has been fixed in the V-Ray 5 update 2 (5.20.00).
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
- Unreal Engine® Plugin: The support for version 5.0.0 Early Access 2 is in the beta stage, keep in mind that it is not production-ready yet. For example, at this moment it is not possible to build packages in UE5 when the anima® plugin is enabled, that is why the plugin is disabled by default in this version. However, if you enable it in the project plugins section of UE, everything except the build package process should work as expected.
anima® 4.5.2
Release | 7/07/2021
NEW FEATURES:
- 3ds Max® Plugin: Multiple improvements have been made to the Quick Drop panel to provide a better and more stable experience when using it.
- Cinema4D® Plugin: A new option for displaying all actors as full meshes instead of arrows is now available.
BUG FIXING:
- anima®: IMPORTANT Fixed an error where exporting a project with a resource cache bigger than 4 GB would cause the resulting .anipack file to be corrupted. This is a critical fix that should be applied as soon as possible if you wish to submit your projects to a render farm.
- anima®: Fixed an issue where updating a scene using anima alive without automatic updates could cause the application to get stuck on a waiting cycle.
- anima®: Fixed an error where locking and unlocking a scene repeatedly while connected with alive could cause the resulting frames to be erased, display visual glitches, or even freeze the anima plugin being used.
- anima®: Fixed an error where the application was unable to recreate the resource cache if it was corrupted for some reason. A prompt will now appear to confirm this operation if it’s required to save the project.
- anima®: Fixed an error where switching to the library editing mode could cause a freeze if a scene with a big amount of baked frames was loaded.
- anima®: Fixed an error where attempting to bake a scene with no actors would result in a freeze.
- anima® Plugins: Fixed an issue where the last modified time of a scene would not be updated correctly when using anima alive, leading to an incorrect warning on the plugins.
- 3ds Max® Plugin: Fixed an issue where the models from the subscription were not visible in production renders when using Redshift.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - 3ds Max® Plugin: The models from a subscription that are used from the Quick Drop panel are rendered as a degraded mesh in production renders made with Redshift and V-Ray GPU (V-Ray standard works fine). This issue will be fixed in the next anima® update.
- Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled. This is an error caused by V-Ray ignoring the MotionBlur tags in the actors and must be fixed by ChaosGroup, it is not caused by anima®.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
anima® 4.5.1
Release | 10/06/2021
NEW FEATURES:
- anima® Plugins: The texture quality setting for rendering can now be selected when creating a new project, either from anima or when using the Quick Drop feature.
- 3ds Max® and Cinema4D® Plugins: A warning will now appear when changes have been detected on an anima scene from the last time it was imported.
- 3ds Max® Plugin: Meshes that were dropped when using the anima All service will now be clearly indicated with a different wireframe color.
BUG FIXING:
- anima®: Fixed an error where the baked contents of a scene would be ignored and deleted when opening it from anima or one of the plugins.
- anima®: Fixed an error where it was no longer possible to download a product owned by an account if that same product had been downloaded previously using the anima All service after logging out.
- anima®: Fixed an error where the scene exporter would crash if any assets had been dropped with the new Quick Drop behavior in the project before.
- anima®: Fixed an issue where the application would crash when attempting to alter the height of an actor that had no skeleton.
- anima®: Fixed a visual error where the bounding box for actors would not update properly when their simulation results were baked.
- anima®: Fixed a visual error where the billboards for nodes inside the viewport would not appear in the correct position when using their on and off toggle.
- anima®: Fixed an issue where actors that are no longer available after logging out from the anima All service would be referenced by the crowd generator and use generic actors instead.
- anima®: Fixed an issue where generating actors with an empty model list would not default correctly to only using the free library, leading to situations where only the installed actors would be picked instead.
- Cinema4D® Plugin: Fixed an error when attempting to create a new project or open an existing one on an untitled document.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.
anima® 4.5.0
Release | 31/05/2021
NEW FEATURES:
- anima®: The new anima® ALL subscription is now available. By using this service, you can now choose from all the available Metropoly® assets and download them directly into anima®. When logging in, an activation license tied to your system will also be automatically acquired. You can find out more information about this new service on the AXYZ design web.
- anima®: A new resource cache system has been integrated for all anima® projects. When saving your project, anima® will automatically detect which assets are currently being used and store all the necessary information required for rendering on a new resource cache directory. Any anima® Plugin can open the project and render it, with no need to acquire the purchased products by other means. This means you’ll no longer need to share your purchases directory across your dedicated render nodes: simply transfer the project once it’s been saved from anima and it’ll be free to be opened by any compatible Plugin. Keep in mind this resource cache is only used by the anima® Plugins: you’ll still need to have the purchased asset if you wish to work on a project with anima. It’s worth noting that the size of projects will likely increase as a result of this new system, but it’s important to keep in mind this is a much more portable solution. We’ve detected many common problems that could happen from incorrect configuration when sharing projects across render systems and this solution solves most of them efficiently.
- anima®: Downloading actors is now easier than ever: simply drag and drop an online asset from the actor library into the scene and it’ll automatically start downloading the required resource files. Once it’s done, the product will be installed and displayed inside the scene. A progress bar will also appear above the actors currently being downloaded along with a matching thumbnail. This feature also works when opening projects from other users. If you open a scene that contains actors you don’t currently have installed but have access to (either from being purchased or from the anima® ALL service), then any missing actors are downloaded and displayed once the process is finished.
- anima®: Various performance improvements thanks to a new filesystem implementation that cuts down on memory usage and unnecessary memory decompression among many other things. Loading times have been reduced across most components of the application.
- anima®: The texture quality of the assets used in the anima® Plugins is now controllable from the new “Project Settings” panel above the scene tree. This setting has been removed from the scene browser when opening it from a Plugin.
- anima®: Many improvements have been made to the searching functionality in the actor library. It is now possible to search for terms with spaces on them by surrounding them with double quotes (e.g. “Delivery Man“).
- anima®: You can now select whether to flip the green channel of the normal maps of an asset when using the actor importer.
- anima®: The application will now detect when multiple users are working with a project on the same location and show an appropriate warning that their changes may be lost due to possible editing conflicts.
- 3DS Max® Plugin: The name given to actors in the project tree is now displayed inside the node tree of 3DS Max®. This opens the possibilities of developing custom scripts that affect certain actors by using a naming scheme from within anima®.
- 3DS Max® Plugin: Improved actor Quick Drop placement tool. The contents of the Quick Drop panel will now be updated automatically when installing new products in anima®.
- 3DS Max® Plugin: Improved Arnold and V-Ray materials.
- 3DS Max® & Cinema4D® Plugin: Drag and drop behavior from the Quick Drop panel has been improved, making it possible to select different color variations directly from the node properties. Any dropped actors will now be part of the existing anima® project, providing a quick starting point for adding static content to your scene and allowing you to expand your work with animated characters at a later point.
- Cinema4D® Plugin: Support for Cinema 4D® S24 has been added.
BUG FIXING:
- anima®: Fixed an issue where performing multiple selections on the actor library while a search filter is active would incorrectly select items that weren’t visible.
- anima®: Fixed an issue where a simulation would have significant visual differences from what was previewed in anima® and an anima® Plugin while alive™ was active due to a subtle operational error. While this had no effect on the final result of a render, it could lead to confusion when comparing frames directly between both applications.
- anima®: Fixed an issue where the search bar on the actor library would hide even if its focus was active.
- anima®: Fixed an issue where the visibility of protected materials would not be updated correctly when editing variations in library mode.
- anima®: Fixed an error where ready-posed characters would be identified incorrectly as ambient actors when being saved again even if they weren’t animated.
- anima®: Fixed an error where the offset of a ready-posed character would be reset after capturing a new thumbnail in library mode.
- anima®: Fixed an error where a warning would be displayed if a scene was baked and one of the used assets was missing from the installation. Instead, the asset will be installed automatically if possible or instead, the bake result will not be useful.
- anima®: Fixed an error where the application would not respond correctly when opening a project with a corrupted or missing background.
- anima®: Fixed an error where the license panel would accept purchase codes for a different license version of anima® and result in an error during activation.
- anima®Plugins: Fixed an issue where relevant dialogue prompts would not appear in the correct screen that the host application is currently using.
- anima®Plugins: Fixed an error where any anima® Plugin would be able to update the resource index on its own and cause conflicts when installing new resources while anima® is open.
- 3DS Max® Plugin: Fixed an error where the scene’s framerate would not be synchronized correctly with anima® in some cases.
- 3DS Max® Plugin: Fixed a performance drop with Arnold renderer and the material editor when 4D characters were added to the scene.
- 3DS Max® Plugin: Fixed the geometry normals that could break under some special circumstances.
- 3DS Max® Plugin: Fixed an issue where the animation of the actors would not be updated if the animaScene001 object was not visible in the viewport.
- Unreal Engine® Plugin: Fixed an error where reimporting a scene with escalators could cause a crash if the number of steps had changed.
KNOWN ISSUES:
- anima® and Unreal Engine® Plugins: If you see black textures on the 4D models, it means that you are using an old version of your GPU driver. The issue will disappear after you update your driver.
- 3ds Max® Plugin: The 4D models might be shown with heavy deformation artifacts only in the 3D 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 in the 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.
In Redshift, after an interactive render is made the mesh on the 4D models becomes unstable, but it can be fixed again by rendering a production render. This happens because Redshift does not notify correctly the end of the interactive render, so we have already reported this issue to the Redshift developers. - Cinema4D® Plugin: The 4D models cannot be used with Motion Blur on Cinema4D® due to an incompatibility with the architecture of this application. When 4D models are rendered with MB enabled, they appear to lose the mapping on the textures on some frames. The problem is caused by a missing feature in the Cinema 4D SDK that is present in all the other platforms we support. We have reported this issue to Maxon and asked them to add this feature in order to enable Motion Blur compatibility.
- Cinema4D® Plugin: V-Ray 5 may render some frames as corrupted meshes on the 4D models when the Motion Blur is enabled.
- Maya® Plugin: The renderers supported on Maya® are Arnold, Redshift, and V-ray.
- Maya® Plugin: The texture of the 4D models is not correctly updated when rendering sequences with V-Ray. We are in contact with ChaosGroup to find a clean solution for this but, meanwhile, we have a workaround available that can solve this problem too. Please contact our Support Team to get it.
- Maya® Plugin: V-ray renderer does not support motion blur on 4D models.
- Maya® Plugin: The viewport must be set in DG Evaluation mode to correctly display the animation of the models. Serial and Parallel modes can cause mesh corruption on 4D models and break the animation on the Rigged models.