Creator update cleared all saved profiles
Answered
Profiles that had been created and saved with the previous version of the Creator app have been completely zeroed out except for the file/profile name when they are opened with the current version of the app.
If I happened to have modified and re-saved a profile with the new update, then the file opens and works as usual.
I assume this is a bug in the new update. I don't want spend hours rebuilding my profiles. I'm hoping all the save data is still there and is just unreadable by current app.
Any suggestions for how to get my profiles back?
-
Hi Sally, thanks for raising this. I'd like to help find out what went wrong. Rest assured that opening these profiles does not overwrite the saved data... as long as there were originally valid profiles that were saved, we can restore them.
Mind sending an email (support@monogramcc.com) with all your saved profiles attached in a .zip?
Once we've received the profiles and found the bug, I'll work with our software team so they can address it, and will also post a workaround for anyone else potentially affected here.
-
An update for anyone else who may have been affected: I think we've found the root cause of this.
Basically what we believe happened is that the profiles failed to load into Creator when opened from Finder/File Explorer, but the saved files themselves were not affected or blanked.
This can be worked around by opening the profiles from inside Monogram Creator (see short-term fix below).
Comments from our software tester:Opening profiles from explorer (ie double-click on the profile in finder/file explorer) while the creator app is closed opens the profile as blank, but opening the profile while the creator app is open still functions correctly.
Short-term fix:
Please make sure to load any profiles in the following manner: Open Creator and load the profiles in one-by-one using Ctrl/Cmd+O or File > Load Profile
If a profile loads as blank, please close it and re-load using the above steps.
Long-term fix:
This bug is now being addressed by our software team and will be fixed in an upcoming Creator update.
Please sign in to leave a comment.
Comments
2 comments