We are looking at 2025 now so I will keep an eye out for this happening.
Seems a few odd things have been cropping up in 2025
we are on 2025.2.x without any version specific complaints. Tons of good stuff always being adding, in addition to lots of bug fixes. Upgrade without hesitation.
1 Like
I’m finding lots of little weird things. Today, every time I set an input transform, it is inverted. Yesterday it wasn’t.
EDIT: I just did a restart and this problem disappeared.
This I agree with.
Matchboxes behaving strangly
OpenClips pulling in the wrong shot/version
Background Render (Mac) stopping working
…
1 Like
No matchbox issues yet. Lost some python hooks. Your other issues are NA for me.
Saw this today—backgroundreactor.
Finally got an eyes-on view of funkiness. I touched a node dead center and another node that I hadn’t touched in many clicks connected it’s matte channel to the one I touched. The exact same connection had been made twice before during today’s session and the first time I thought it was cockpit error. The second I wasn’t so sure, but the third, I was eye witness. There’s some buggy shit going on with 2025.2.1
1 Like
Must be a new Batch AI feature that’s hallucinating 
we had quiet a lot of hard crashes with 2025.2.1
took me like 6 restarts of flame to import a bunch of normal XMLs it would just hard crash, no logs, no nothing, not even the autodesk “we have crashed” thing
also had the flame UI burn itself into a action output on a mac
1 Like