The ironing feature needs a “lowest surface only” option, to polish the base of something (a podest, not the underside).
Do you mean the undersides that are created using bridging?
You say not the underside, which is good as the build-plate provides that surface.
I imagine the ironing feature would more likely cause an increased issue as it adds heat to the layer which would cause a further melting of the bridge layer, resulting in a droop in the middle or worse.
I can’t really think of a model where you would only want ironing on the lowest top surface, but I think you could accomplish that using modifiers to switch between top surfaces and no ironing.
Here’ a use-case where that exact feature would be nice that I believe @dtmr is suggesting.
Here’s the workaround.
– Use Height Range modifiers and set those layers to ironing.
1 Like
Here’ a use-case where that exact feature would be nice that I believe @dtmr is suggesting
Indeed.
Here’s the workaround.
Nice. Thanks for the help.
My problem was that ironing this (“all top surfaces”) made the slightly slanted hook part with the three “teeth” brittle. Bambu Studio seems to think that every layer of it is a top surface (because it is slanted?) and irons every layer of it:
OK. Thanks for posting that clarification. It changes the “ask” considerably.
I’m afraid there is no mathematical way to achieve your request. if I understand you correctly, you’re saying that smoothing occurs at every layer that you don’t want because of the topographic(stair stepping) affects of 3D modeling.
I’m afraid that won’t work because the ironing feature operates at the “layer” level, not the “surface” level. What I mean is that once a layer is deposited, if ironing is enabled, the nozzle is instructed to go back and forth over that layer to smooth out the nozzle grooves.
I suppose if there were a feature that allowed you to “paint” which layers or surfaces should be ironed, similar to how the supports paint tool works, it might be a viable solution. However, that would be a significant “ask” for something that likely wouldn’t come up often. Still, it’s a thought worth suggesting. 
Here’s my suggestion:
Don’t bother making suggestions to Bambu here. While this forum is great for community discussions like this thread, it’s a waste of time if you’re expecting Bambu to listen. As we saw with the community’s request to disable the chamber lamp, Bambu took the exact opposite, passive-aggressive approach of permanently enabling it despite widespread pleas from members of the Bambu community. I guess they showed us who’s boss, didn’t they? 
Instead, consider bringing this idea to the Orca Slicer community. They’ll expect you to provide clear use cases and articulate exactly what you mean by your request—it’s a technical community, not a place for lightweights. But they are far more likely to explore this request than Bambu ever would.
How to post a feature request to the Orca Developers
Navigate to their issues page, and make sure to select “Enhancement” when you post your message. This will flag it as a feature request. Here’s the link to the page where both bug reports and enhancement requests can be submitted. Sign in to GitHub · GitHub
Click here for feature request.
This is what a correctly posted feature request will look like after posting. If you’re new to Github, it can take a while(up to a day) before you may see your post get approved by their antispam feature.
You only want the green area ironed, correct?
As posed above, the “height range modifier” is a perfect solution.
