Hello everyone,
I'm a graduate student working on RF simulation, and over the past year I've been slowly building a small open-source tool that drives HFSS end-to-end. Compared with most people on this forum I'm still very much a newcomer to the Ansys ecosystem, and I've run into a version-compatibility question that I couldn't resolve on my own — I suspect the answer may be simpler than I think, but I'd rather ask than keep guessing.
The situation. Our collaborators' projects span several releases; some go back to the 2021 release, while the machines we use for unattended runs only have 2025 R1 installed. When we open a 2021-release .aedt project on 2025 R1, Electronics Desktop declines to open it and asks us to first convert the project with an earlier release. In practice this has meant installing an intermediate "bridge" release (2024, in our case) just to open and re-save those older projects before they can be used on 2025 R1.
What I checked before bothering the forum (probably far from exhaustive):
- The Opening Legacy Projects page — it covers the very old pre-
.aedt HFSS files, which was helpful but not quite our case;
- The command-line reference — I found
-BatchSave ("saves a named project or folder containing one or more project files or folders to the current version") and the older -BatchConvert form, which sounded like exactly the right tool; I just couldn't tell from the documentation whether it converts a 2021-release project directly to 2025 R1, or whether it would hit the same cutoff and simply produce a clearer error;
- A few community threads — I found the same cutoff error reported before ("Legacy project files can no longer be opened in this version… Please use release X or earlier to convert"), and the standard advice does seem to be installing that earlier release as a bridge. I did not find a documented no-bridge path, but again, my search may well have been incomplete.
If I may, I'd like to ask:
- Is there a supported way to open or convert a 2021-release project directly on 2025 R1, without installing the intermediate release? For example, does
-BatchSave / -BatchConvert cross the cutoff, or is there a standalone conversion utility I've overlooked?
- If stepwise conversion is genuinely required, is the compatibility matrix documented anywhere (i.e., which release converts which project era)? Knowing the exact cutoffs would let us plan installs properly instead of discovering them by trial and error.
- And for unattended setups — pooled machines and CI runners that intentionally keep only the latest release — the per-machine bridge install is a heavy burden for us. If stepwise conversion is here to stay, we'll happily live with it; but if a standalone converter or a friendlier path is ever considered, it would mean a lot to small automation setups like ours.
Thank you very much for reading — and thank you for this community's enthusiastic and timely guidance; as a newcomer I've learned a great deal from the threads here, and I'm grateful for any pointers you can offer.
One last note: English isn't my first language, and I asked an AI assistant to help polish this post — my apologies in advance if anything reads a little oddly.