I now get this message in bambu studio, i’m not sure what to make of it, i did not set any custom dynamic flow value, why does this show up? (btw i’m using HF nozzle on the right and standard on the left)
In my opinion, that warning is just poor UI design. I assume there would normally be some sort of input field to set a custom flow. However, since you set the flow to auto, this input field is hidden, and instead, you receive a warning stating that you cannot set a custom flow. This doesn’t necessarily mean you have set a custom flow; it simply indicates that you can’t set one because it will be auto-calibrated
It means exactly what it says, set that option to OFF if you want to use a custom dynamic flow value (as in, the value you entered and saved to the printer after doing a manual calibration).
2 Likes
yeah thanks for your input, but there really shouldn’t be a message prompt there, unless you have defined in the slicer / filament profile a custom setting, there is no reason for this to be there, it’s a weird warning to make for no reason at all. i also don’t remember this happening when both nozzles were standard, only when there is a HF installed
searching in the documentation i’ve not found anything related to this, so i’d like to understand why exactly this is showing - ignoring it works just fine, but i want to understand if it messes up with the potential benefits of using the HF nozzle, which so far to me doesn’t look like it has done anything in terms of increasing print speeds
and i know we all like to put hypothesis out there, but i’d really like to know facts 
@SupportAssistant maybe that’s something you can clarify?
1 Like
The message you are seeing is an informational message, to inform you what to do if you wish to use a custom value. But I will forward the feedback and we will find ways to improve it.
In regard to what the setting does when it is on Auto, please check this more extensive explanation.
3 Likes
ok thanks, it certainly looks more like a warning than just a piece of information, so it’s a bit odd, you also can’t really set values at that stage, so i’m not sure what benefit it brings
I have received confirmation that a fix is implemented and will be released in the next update. Thank you for sharing!
3 Likes