Configuration and OS

Newly qualified hardware from Lenovo and HP, and new Network Services configuration file for easier service discovery.


Hardware Configuration

Supported Platforms

For macOS and Linux recommended hardware, see the Flame Family system requirements.

Note: Flame Family's graphics API now uses Vulkan(on Linux) and Metal(on macOS) instead of OpenGL. Performance in rendering and playback speed should be at least equal to what was available in previous versions, with many use cases showing marked improvements.

Apple silicon-native

Flame, Flame Assist, and Flare are natively supported on Mac computers equipped with Apple silicon processors, like the M1 and M2.

Supported Operating Systems

Flame Family 2024.2 Update supports the following operating systems:

macOS:

Linux:

Newly Qualified Hardware

Lenovo Workstation

The Lenovo P7 workstation has been qualified with Flame Family 2024.1.2 and 2024.2 Updates.

For more details, see Lenovo website.

HP Workstation

The NVDIA RTX 5000 (Ada Generation) is now qualified on the HP Z8 Fury.

Hardware Deprecation

The HP Z840 will not be supported by the next major Flame Family release.


Application Configuration

Network Services Configuration File

Wiretap relies on self-discovery (multicast) to discover Flame Family-related services running on the local and remote hosts. These services are:

Some network or host configurations can prevent Wiretap from using multicast to discover these services. Flame Family 2024.2 Update introduces a new Network Services configuration file. This file allows system administrators to define network addresses for the various services, which can then be complemented by the various self-discovery technologies like multicast or AWS Transit Gateway, if available. So even without self-discovery, it is now possible to define a Flame Family multi-services workgroup for on-premises and cloud workflows.

The Network Services configuration file is located at /opt/Autodesk/cfg/services.cfg.

A sample file with default parameters is also available at /opt/Autodesk/cfg/services.cfg.sample.

The file is monitored so any modification to the file automatically restarts the various services referencing it.

You can use the new services_snapshot.sh script (in /opt/Autodesk/cfg folder) to update the file with the local Wiretap server information. It requires administrative privileges to run.

ftpuploadlogs

The ftpuploadlogs script moves to /usr/local/bin.

On macOS, the script is located in /opt/Autodesk/Common Utilities.

This change applies to both Flame Family and Project Server installations.

Notes on Rocky Linux 8.7

Flame Family 2024 added support for Rocky Linux 8.7. If you are moving to Rocky Linux from CentOS 7.6 and are using ATTO fiber channel cards, see the following section.

Rocky Linux 8.5 is fully supported by Flame Family 2024. But if you want to upgrade to Rocky Linux 8.7, you can use the Easy Upgrade script included with DKU 18.

Firmware Update for ATTO Cards When Upgrading From CentOS 7.6

If you are using ATTO card FC164E or FC164P, and you plan on upgrading from CentOS 7.6 to Rocky Linux 8.5 or 8.7, you must first update the card's firmware. For details, see this Autodesk support article.

Important: Update the firmware before upgrading to Rocky Linux since the old firmware is not compatible with Rocky Linux and the card will not be visible.

Rocky Linux 8.7 Easy Upgrade Script

Important: Before upgrading, you must install DKU 18.1 since the NVIDIA driver part of previous DKUs is not compatible with Rocky Linux 8.7.

You now have access to a script to upgrade Rocky Linux 8.5 to Rocky Linux 8.7 on a Flame Family workstation or a Burn node. For more details, see Linux Upgrade script.

Note: Do not use this script to upgrade:

Updated GNOME Shortcuts

The following GNOME keyboard shortcuts are changed to avoid key conflicts when a Flame Family product is running:

When you exit the Flame Family application, the original GNOME shortcuts are restored.

Note: If you use a keyboard with a single Windows key, you lose access to the Overview shortcut. You can fix this by following the instructions in Remapping the Overview key Left Meta key.