[FIXED] V4.1 Bridging Issues

[winchymatt]

Hi, I've just updated to V4.1 and spotted some differences in the generated GCODE files that may be an issue. This concerns bridging settings when using the settings: "Apply bridging settings to perimeters"

V4.0 would generate GCODE such as below which is to be expected:



V4.1 generates some spurious bridging regions which are unexpected.

[SWCNT]

Yeah I've noticed that too, it's applying bridge settings to outlines that aren't bridged and not applying bridge settings to some of the outlines that are bridges. I've gone back to 4.0.1

[S3D-Alex]

Thank you for bringing this to our attention! Can you please provide a Factory File for this particular issue?

[winchymatt]

Hi,

Factory file attached.

Thanks.

[S3D-Alex]

Thank you for providing the Factory File! I was able to reproduce the bridging error in my testing here and have documented my findings for the development team.

In order to work around this in the meantime I have found that turning off the "Coast at end" option and/or the option to "Apply Bridging Settings to Perimeters" will cause the file to slice correctly.

[winchymatt]

Hi,

Ahh ok. I'll try removing the coast at end option. Thanks.

[winchymatt]

Hi, Coast at end option does indeed remove the spurious bridging lines, however, the bridging still isn't as good as V4.0 IMO.

[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 apply bridging settings to perimeters will no longer result in the bridging settings getting applied to non-bridging regions. This was just one of many improvements to the software. All of which are detailed on our Release Notes page.

Technic_brick sliced in 4.1.1

Thank you for your help reporting this issue!