You will be in for a world of hurt.
In fact, we have decided all future projects will be done back in 2025.x. We’ve had 3 special QFEs to try and fix 2026, to no benefit. It is flawed and broken. You’ve been warned.
1 Like
@ALan - I love you brother, but I absolutely disagree.
YMMV
It’s not surprising that a big release with lots of fundamental change runs into a corner somehwere.
However, it would be helpful to get more detail rather than a blanket warning, so we can understand a bit more what the flaws are. That way folks can decide better if they’ll face similar issues or not.
7 Likes
Rule of thumb. Always wait till .1.x gets released.
1 Like
@tombox - which although prudent in outlook, will not win either Le Mans 24H or Nurburgring 24H.
Be prepared and WIN
1 Like
Only problem: if 100% of us wait until .1, then .1 is the new .0.
Someone has to fall on the sword to find all these issues, right?
Better to have a community that can do this together and has good relations to the dev team, than everyone doomsday prepping in the cave.
5 Likes
I’ve fallen on the sword so frequently in the last 30 years that death by a thousand cuts is just Tuesday…
5 Likes
That’s sort of self-defeating, as others have pointed out. I was really chuffed to upgrade during the .0 version this year. I can’t upgrade until I have no major projects in production, and my engineer is available. Last year I didn’t upgrade until October-ish. If those 2 phases coincided with the day of release, I’d be all over it. Discreet is really good with feedback if you connect with the right people, and those who provide it are often the impetus for the .1.x release. The OP specifically comes to mind. Waiting for the .1.x release may be a necessity for a few, but it should be less of a rule and more of a guideline.
2 Likes
The companies that used to hang on to legacy flame versions, for whatever reason, no longer exist.
Few companies maintain legacy hardware or software.
Fewer companies maintain legacy workflows.
Transitions are painful.
Instinctual are more fortunate than most in that Alan can 100% responsibly facilitate a 100% successful workflow on legacy flame software.
Unlike 99.99% of our community, he knows what that takes and can shoulder the responsibility.
I still 100% disagree.
Oh I disagree with that statement Phil!
1 Like
Define legacy versions, how far back?
@paul_round - legacy=anything that’s not now.
@ALan - said 2025.something in his second post…
Bit harsh calling 2025 legacy
1 Like
And here I am going thru the motions of installing the project server on a new system for Flame 2026… Question, will 2025 work on Rocky 9.5? (since i already formated a few systems…(
I can’t remember 2025 not working on Rocky 9.5, despite the documentation reporting 9.3.
What does your engineering IT team tell you?
2025.2.3 and up will work on 9.5 (I am told.)
1 Like
When in doubt, the system requirements are the first place I check.
Rocky Linux 9.5 is supported on Flame 2025.2.3 and above. 9.3 for the rest of 2025.
2 Likes
Always wait for the extension release. You will get all major bug fixes and A couple of cool toys to play with.
You play with fire If you use the first major version for production.
1 Like
garlic, holy water and silver bullets are also notoriously successful at avoiding complications that arise from encounters with vampires.
1 Like