Page 1 of 1
[FIXED] S3D 4.1 - bridging perimeters in weird places
Posted: Thu Nov 08, 2018 3:23 pm
by guywhodoescad
I'm getting some weird perimeter settings on the latest version of S3D, has anyone had something similar with this version?

The part is symmetric and the bridging issue inst happening on the other side.
Turning perimeter bridging off fixes this but this clearly shouldn't be happening
Factory file:
FFF profile:
Re: S3D 4.1 - bridging perimeters in weird places
Posted: Fri Nov 09, 2018 1:31 pm
by S3D-Jake
Thank you for bringing this to our attention. I've tested various changes and documented the issue for our development team.
In the current version (4.1.0), I've found that toggling coasting off corrects the errant behavior of bridging perimeters in this factory file.
Re: S3D 4.1 - bridging perimeters in weird places
Posted: Thu Nov 15, 2018 7:11 pm
by dmitry_sorkin
I have the same problem with all models, even with becnhy. When the problem will be fixed?

Re: S3D 4.1 - bridging perimeters in weird places
Posted: Fri Nov 16, 2018 2:22 pm
by S3D-Jake
Did disabling coasting or apply bridging settings to perimeters not fix the issue for you?
Re: S3D 4.1 - bridging perimeters in weird places
Posted: Fri Nov 16, 2018 3:26 pm
by dmitry_sorkin
Disabling coasting fixes problem. But instead of poor surface quality due to buggy bridges it causes poor surface quality due to disabled coasting. I think it's not how it must work for 150$ software.
Re: S3D 4.1 - bridging perimeters in weird places
Posted: Wed Dec 12, 2018 2:27 pm
by S3D-Jake
I’m happy to state that this issue should be resolved now in the latest 4.1.1 release. Our team successfully tested your factory files from threads mentioning this issue. The combination of coasting and bridging applied to perimeters will no longer cause bridging settings to be applied to perimeters that aren't actually bringing sections. This was just one of many improvements to the software. All of which are detailed on our
Release Notes page.

- y3 sliced in 4.1.1

- benchy sliced in 4.1.1
Thank you for your help reporting this issue!