There seems to be an issue with the propagation of deleting presets. It seems like synchronization of deletes is weird somehow. Imagine two computers, A and B , and a preset 'TEST'.
When you create 'TEST' on A it seems to sync to the cloud and on restarting BambuStudio on computer B, it appears. Now, if I delete 'TEST' on B, it remains on A and does NOT get deleted (which it should be).
When you delete a preset from one computer, it remains on the second.. and then, even if you go back and update 'TEST' on A (say, change the temperature and save), it will STILL not show up in the cloud/get sync'd.
So the bug here is that user profile deletes arn't getting propagated I think, which causes a lot of confusion when you're trying to figure out what's going on. As soon as those profiles are 'orphaned' in the cloud (deleted) the OTHER bambustudio instances should be cleaning them up at next launch, but are not. This leads to a messy situation where you can have two profiles with the same name on different computers but one is cloud based, and the other is local only.
The proper fix here would be to propagate deletes / fully synchronize the user profiles with the cloud properly, as common services like OneDrive, etc. do. If users don't want this behavior, they can un-link synchronization in the preferences.
Note: I originally misattributed this issue to a different problem (have changed this issue to reflect updated discoveries, and forked a different issue to https://github.com/bambulab/BambuStudio/issues/625 , which I conflated originally).
There seems to be an issue with the propagation of deleting presets. It seems like synchronization of deletes is weird somehow. Imagine two computers, A and B , and a preset 'TEST'.
When you create 'TEST' on A it seems to sync to the cloud and on restarting BambuStudio on computer B, it appears. Now, if I delete 'TEST' on B, it remains on A and does NOT get deleted (which it should be).
When you delete a preset from one computer, it remains on the second.. and then, even if you go back and update 'TEST' on A (say, change the temperature and save), it will STILL not show up in the cloud/get sync'd.
So the bug here is that user profile deletes arn't getting propagated I think, which causes a lot of confusion when you're trying to figure out what's going on. As soon as those profiles are 'orphaned' in the cloud (deleted) the OTHER bambustudio instances should be cleaning them up at next launch, but are not. This leads to a messy situation where you can have two profiles with the same name on different computers but one is cloud based, and the other is local only.
The proper fix here would be to propagate deletes / fully synchronize the user profiles with the cloud properly, as common services like OneDrive, etc. do. If users don't want this behavior, they can un-link synchronization in the preferences.
Note: I originally misattributed this issue to a different problem (have changed this issue to reflect updated discoveries, and forked a different issue to https://github.com/bambulab/BambuStudio/issues/625 , which I conflated originally).