Models saved in v22.2 backwards compatible?
Certain models saved in v22.2.0 can\’t be opened by users still using v22.1.2. Is there a setting to change or filtering that needs to be removed to be compatible?
Hello all, just wanted to give you the “official” word that the file format has changed with Modeller 22.2 and if you save a file from the new version, it will not open in the previous versions, including previous versions of your Quantrix Qloud if you use Qloud.
This sort of file format change is rare for us, but occasionally we must do it to support new features properly. For the future, there is a new feature in 22.2 and forward, wherein Modeler gets its update signal from it’s dedicated Qloud (if you have one) which, for future file format changes, should significantly reduce this likelihood of experiencing this incompatibility specifically with Qloud because you will not be prompted to update before your Qloud has been updated, which will more likely keep versions in sync.
Meantime, this file format change was in the release notes, however it was a bit buried – we will make sure to make this type of change more visible in the future at the top of the Release Notes. (search for “Important Note” if you’d like to read that information).
We hope this change has not caused too much inconvenience, and will make such changes more clear going forward.
Interesting. Provided that the QM22.1.2 license is valid, what prevents users from upgrading to QM22.2.0? In any case, users have the option to install QM22.2.0 to a new folder.
It’s a work in progress to get users updated and we’re looking for a workaround in the interim. thanks!
Are you working on Windows? And sometimes you say you can open an V22.2 saved model on a V22.1.2 version?
I’m working on Mac (M1-version), and model saved in V22.2 can NEVER be opened in V22.1.2 again, even if there was NO modification in the file other than opening and saving in V22.2.
I understand that there must be file format changes sometimes. But if there is a backward incompability, it would be good practice to alert users before they destroy backward compability!
Yes, working in windows. We didn’t run into compatibility issues when upgrading to 22.1.2 and I couldn’t find any mention in the Release notes explicitly stating 22.2 isn’t backwards compatible.
It’s a work in progress to get all users updated but we need a solution in the interim.