Hmmm, I'm not sure if this is the right way to go.
Have you checked why the select_preset_by_name function failed?

Hmmm, I'm not sure if this is the right way to go. Have you checked why the select_preset_by_name function failed?

As far as I can tell, select_preset_by_name is used to sets the "active" or "currently selected" reset, so when the currently selected preset is already the preset that select_preset_by_name is trying to set active, it just returns false and skip the preset selection this->select_preset(idx); . I do not think this method should be used in the case of exporting presets.

I just found out bambu studio "fixed" it by changing (preset_bundle.printers.select_preset_by_name(preset_name, false)) to (preset_bundle.printers.select_preset_by_name(preset_name, true)) which just force it to trigger preset selection and relavant UI rendering then returns true. It also works, but I think it is unnecessary. Both options fixes the export not showing up bug. @SoftFever How would you like this to be implemented?

I just found out bambu studio "fixed" it by changing (preset_bundle.printers.select_preset_by_name(preset_name, false)) to (preset_bundle.printers.select_preset_by_name(preset_name, true)) which just force it to trigger preset selection and relavant UI rendering then returns true. It also works, but I think it is unnecessary. Both options fixes the export not showing up bug. @SoftFever How would you like this to be implemented?

@Azio-Pantheon
Thank you for digging into the issue.
I've reviewed this issue too. We shouldn't remove this if check because doing so would cause problems when selecting a non-current printer. The update compatibility won't work properly if we don't select the printer first.
Setting the "force" parameter to true is the correct way to resolve this issue.