Where "Limit support retractions" feature gone with 5.3.x ?

[V3DPrinting 11]

Hi to all

 

I am not able to find the "limit support retractions" setting in the 5.3 or 5.3.1 settings.

In 5.1.1, it's under the Travel section. (I don't remember in 5.2 and I haven't it installed anymore)

 

I have currently an issue with a dual extrusion print (support interface is printed in Breakaway).

To avoid having oozed breakaway in my print, it avoids printed parts, but as there is no retractions, Breakaway oozes and gets into the print.

 

Previously, turning off the "limit support retractions" features solved that issue.

But it looks like the feature is not anymore there in 5.3.

 

Thanks for your feedback.

Edited May 8 by V3DPrinting

[GregValiant 1,044]

It's gone.  My understanding is that it was causing more problems than it solved.

 

[V3DPrinting 11]

1 minute ago, GregValiant said:

It's gone.  My understanding is that it was causing more problems than it solved.

 

 

OK we're on the same page. But that should mean that travel between support structures is behaving as standard travel.

 

I am pretty sure that there is no retraction when traveling between two support interface structures though it should (tree supports, different interface extruder or same interface extruder)

Even combing set to not in skin for both extruders, the move is done without any retraction, traveling around the printed part and also over printed parts (though it should avoid printed parts)

 

 

I'm fine with removing the feature and keeping the retraction between supports, but it fear it's not the case at least for tree supports with or without different interface extruder.

 

No problems with normal supports though.

 

 

So there's a bug with the tree supports. But the 'limit support retractions' seems to have properly been removed.

[GregValiant 1,044]

You can report it on GitHub.  It won't be the only bug found with tree supports (although they seem to be getting better).

[V3DPrinting 11]

1 hour ago, GregValiant said:

You can report it on GitHub.  It won't be the only bug found with tree supports (although they seem to be getting better).

I will !

Thanks for your inputs that helped me find out the issue.