Flame 2025 is here! 🚀

[robert.doche]

The wonderful @Jeff recorded Flame 2025 videos for the Flame Learning Channel. 1st video of the series is up now. More to follow over the next couple of days: https://youtu.be/tzGBP47QcLo?feature=shared

[allklier]

@robert.doche That is great to hear. @Jeff’s last series for 2024 was very good.

That said, the Learning Channel didn’t just cover new features, but also general how-to content, which now is not being refreshed. We have to rely on Logik and Logik Pro at our own cost. That is a definite hole ADSK has left behind.

[randy]

@GPM

ADSK has cut so many resources, including Grant Kay, so there is no one left to make the great videos we used to get with releases. Due to this we also have scant interactions with them on the forum, etc.

[ytf]

Is the license workflow any better? I’m not impressed with the current scenario.

[ALan]

Just you wait. It is actually much worse in 2025. You have to login to ADSK licensing via a web browser. Then the browser opens a pop-up where you need to click a button to launch flame.

[allklier]

That’s been for many of like that for quite a while…

[fredwarren]

@paul_round

• You no longer need to create a Flame user profile.
  Can you expand on this point.
  What about the user bin in batch?

The user settings are no longer saved to a dedicated hierarchy (/opt/Autodesk/user) but rather to your OS login files, like most applications. That includes preferences, keyboard shortcuts, and presets.

For example, the nodes you put in your User node bin will be saved in a place that can be accessed from any machine on a network if your user login credentials are centralised and, starting with the 2025 and on, will be availlable in every new release without the need to copy them or re-create them.

You can add to that the possibility to save User-based settings in more places than ever and the possibility to export and import your user-based preferences, shortcuts, and presets.

[allklier]

I just installed the 2025 release version on my Mac. It did not automatically enable Full Disk Access.

So after you install it, run the Service Monitor, do the Full Disk Access scan and fix it.

[fredwarren]

It will never will until Apple let us do it.

[allklier]

Could the installer remind you then to do it?

[fredwarren]

Flame 2025 now tells you so when you first launch it.

[allklier]

Ah, I guess I was too proactive, since I checked right after install, but before launch.

[ytf]

@fredwarren

…at can be accessed from any machine on a network if your user login credentials are centralised and, starting with the 2025 and on, will be availlable in every new release without the need to copy them or re-create them.You can add to that the possibility to save User-based settings in more places than ever and the possibility to export and import your user-based preferences, shortcuts, and presets.

Does this mean that my login name and my flame user name need to be the same?

[BHarris]

@allklier

’s last series for 2024 was very good.

That said, the Learning Channel didn’t just cover new features, but also general how-to content, which now is not being refreshed. We have to rely on Logik and Logik Pro at our own cost. That is a definite hole ADSK has left behind.

Fully agree. As a longtime Nuke compositor getting into Flame, the Learning Channel has not been particularly helpful. When I want a quick overview of how a tool or process works, the learning channel videos are often just cover which controls have been “aptly renamed” to something else or re-organized under a different submenu. I see the value for Flame veterans who want a quick change recap, but it won’t help grow the user base.

[BHarris]

@cristhiancordoba

I remember when I was exicted waiting each new flame realease at night…when we had new features… unfortunately that time has gone. Honestly, was expecting some copycat for flame or AI relevant feature.

Yeah was hoping there might be some ML tools in the release. Excited about the Grain Match.

[ytf]

@ALan

Just you wait. It is actually much worse in 2025. You have to login to ADSK licensing via a web browser. Then the browser opens a pop-up where you need to click a button to launch flame.

Perfect . . . one more thing to go wrong.

[paul_round]

I can’t say I’ve ever had an issue with the whole user thing, more important things to sort IMO.

[PhilippeJ]

@ytf

Does this mean that my login name and my flame user name need to be the same?

Name and Nickname used for the name fields with tokens can still be set from the application in Preferences > User > User Tokens or from the User tab in the Flame Setup application.

On first use, the “Name” will be initialized with the os user name.

[TimC]

ALL THE…
…SMALL THINGS

NA-NA NA-NA NA-NA NA-NA…

The order of the Sequence tabs is in sync with the Media Panel.

[kily]

@allklier

There are still user settings, it’s just how they’re managed has changed. They’re no longer version specific which is a nice upgrade.

Sure. Many people may have become accustomed to working only on their flame and not sharing with anyone else, but what about flames shared by several people? Changing the OS user can be critical. There are countless things customized with the OS user, including IT in-house stuff. Login with different users doesn’t seem practical to me.

Honestly, I didn’t see anything wrong with the flame user. Maybe it’s tedious to create a user with each version, but with the “copy user option” it is no problem. It was a good thing.