I am new to Bambu Labs, and am currently learning this system.
It appears there is a design problem with the way ‘profiles’ are managed.
In the documentation there are three types/categories of profile information.
- Printer - for physical printer configuration
- Filament - for individual filaments
- Process - details related to the printing mechanics of a specific object.
In the documentation there are three ways to ‘save’ profile information.
- System presets - not changeable (but update able with updates by Bambu)
- User presets - these presets are stored locally on the users PC and contain user customization to system presets.
- Project presets - these presets are stored inside 3MF files (as an in-bedded profile object) and are distributed with the file as it is shared about the community.
NOTE: There is one other location profile settings are stored and this location is basically not mentioned. I think this detail should be mentioned as it is a key concept to understand the way ‘profile’ information is moved about through the community.
- Model presets - these presets are stored inside the 3MF file, but unlike the “project presets”, which are stored as a profile object within the 3MF, the “model presets” are stored with the ‘model itself’ and are applied automatically when the file is opened by the user.
This 4th item is not mentioned and as such is causing confusion. Here is an example of the confusion it is creating.
a. User selects a model from the online collection and ‘opens’ the 3mf file in studio. “NO CHANGES MADE” - Just open the file.
b. The user ‘closes’ the file. (again, no changes made & then studio prompts the user to ‘save’)
Problem: When a user opens a file, and changes nothing, the system should not ask for a ‘save changes’, as there are no changes. This should never happen, I think that is an fair statement.
Reason this Happens:
Bambu studio, when opening a 3MF file, will apply settings saved in the 3MF file (the model presets) to the settings in bambu studio reflecting the choices the model designer chose when they designed the object.
Bambu Studio will register these settings from the 3MF file as changes, and show these changes with via change indicators such as color and reset buttons designed into the user interface. (Fantastic, this is a great feature and works nicely)
Bambu Studio, when closing the ‘unmodified’ file, fails to understand these model presets are already saved and current in the 3MF file the user opened.
Bambu studio instead prompts the user to ‘save’ these ‘model presets’ as either a
- ‘user preset - saved to config file on disk’,
OR - 'project preset - saved inside the 3MF as a profile object.
Summary.
I think that because we have ‘presets’ that belong to the ‘model itself’ and are stored in the 3MF file, and since this is not actively communicated/described in the documentation, it creates good amount of confusion, ESPECIALLY when a user opens a file, changes nothing, and then goes to close the file and is prompted to ‘save’ the settings.
- Update the documentation to include a 4th category detailing where parameters are stored.
- Do not prompt the user to ‘save’ the model presets that originate from within the 3MF file. If they have not changed, there is no need to save them.
I hope this is making sense, and I hope this is helpful minimizing profile confusion in this product.