Yes, that is correct. Also, it may be noteworthy that there is a temp color scheme in the slicer and one would be forgiven for having not noticed it because you have to drop the menu down and scroll to the bottom. However, I’ve only seen that evident in the temp tower but it is a useful holdover from the Cura code which Bambu Studio and Orca are forked from.
A similar tool in the same drop down is available for speed and flow rate.
In all candor, I am not sure how useful these are, aside from providing a good visual confirmation that the correct Gcode is loaded. A great example is generating a test pattern, or as I’ve seen countless times on this forum, loading a test model from the Internet. The model is useless unless the appropriate Gcode for speed, volume, etc., is modified. However, this is not mentioned on the websites that host these models because it’s assumed the person is already familiar with the process. This is where Orca stands out—it handles the Gcode manipulation.
Here’s an example: If I set up a Max Flowrate model and mistakenly believe that all my settings, including the Gcode, are saved, here’s what happens upon reload—the Gcode modifications are eliminated.
_________________________________________________________
Caution: Important tip. Do not make the mistake I made for far too long
I want to share a hard-learned lesson with the community: I mistakenly thought I was saving my calibrations, but in reality, I was corrupting my profiles by saving
the ‘Test Profile’ modifications over the profile I wanted to modify. It was bewildering why I seemed to be getting random results.
Here’s a tip I learned from Len Drizzles’ Filament Friday channel on YouTube that solved that mystery. When running calibrations, always start a new project before saving values. Enter the modifications from your calibration in a freshly loaded session, then and only them you can save your filament profile. Then repeat the load of a new project again and verify that your filament settings stuck. Use CTRL-N hotkey to quickly start a new project—no need to save when the slicer asks.
This is important because Orca drastically changes settings during calibration to test extremes in the Gcode. If you haven’t noticed, here’s what to watch for.
The asterisk (*) and orange-highlighted areas indicate unsaved changes. To view these changes, click on them. After running a calibration, don’t save the test profile. Use CTRL-N to reload the default profile. From there, you can safely make changes and save your adjustments.
For example, below are some of the changes from a pressure advance test that you don’t want to permanently save in your profiles(noted in orange). Although those modification made by Orca were needed for the calibration, you definitely don’t want them saved in your profile especially since the only modification for this test is Pressure Advance.
