Detect bridging perimeters
When I create my models there are times when I put in built-in supports for FDM printing. I typically leave a .2mm gap between the support and the layer it is supporting. I've been doing this for quite some time so that makers can print my models 'out of the box'.
I am now running PrusaSlicer 2.6 and have been having an issue with the support adhering too tightly to the model (flat surface to flat surface) which I had not experienced before. I see that PrusaSlicer has a parameter called "Detect bridging perimeters" with a comment that it is experimental, and it is set on by default. When I disable this parameter my supports are they way I would expect them to behave.
So, my question is, is this a new parameter for 2.6 or was it already available in the previous releases (and on by default)? I do not want to reload an old PrusaSlicer to avoid potentially messing up my setup.
I know I can tell the makers simply to uncheck the option but I would like to know root cause as well.
Teamwork,
Steve
RE: Detect bridging perimeters
The setting is new for 2.6 and was not available in 2.5.
In future if you want to run older/different versions you can do so by running them with a modified start and defining where it uses for its datadir. That way you can have as many versions as you want and they all use different settings locations.
For example if you create a batch file in the same folder where you extract a PS version that has the following in
"prusa-slicer-console.exe --datadir settings" when run it will start PS and create a settings folder in the local directory and use that.
RE: Detect bridging perimeters
Thank you for the quick reply as well as that added info!
I was doing so many test printing of different versions of my supports and was losing my mind until I noticed that parameter.
Interesting that it is on by default and called 'experimental' as well. I understand the rationale behind it and under normal circumstances would welcome it.
For what it's worth, I ran into a similar issue with the arachne setting being on by default. Apparently that uses the 'detect thin walls' option which also affects older models that are designed to slice properly without the thin wall parameter set.
Growing pains I guess.
Teamwork,
Steve