Great write-up on Bambu Studio & OrcaSlicer. Just a quick example of potential impacts that can happen when Orca & Bambu Studio get out of sync between their release trees.
One glitch I found was caused by using the brand new Bambu Filament PETG-CF in my AMS. Bambu Studio 1.5.x added support for the new filament, but Orca Slicer (v1.4.5) doesn’t have support for it.
When I opened my model in Orca and resynced my AMS filament, it threw a warning about an unknown filament. I believe it set the profile to ABS, but I manually changed it to PETG.
However, since the filament is auto-set by the AMS, BUT Orca doesn’t know how to deal with it, it won’t let you submit the sliced file to the printer (if you are using the AMS).
I didn’t manually load the filament (non-AMS), but I assume that should work since it wouldn’t be reading the RFID chip in the filament spool in that case.
I am sure that once SoftFever rebases his Orca version to the new Bambu Studio 1.5.x tree (or adds the appropriate filament profiles for the new types like PETG-CF) it will become a non-issue.