Ver 1.1.7 Missing support structures

[NinjaCross]

I'm usingslic3r-mswin-x64-1-1-7-stable on Windows 7 x64 Pro
As you can see in the attached screenshots, support structures are completely missing on some overangings:

Please see the STL files and configurations used:
http://www.dogmasolutions.com/public/Temp/Slic3r_Issue_2222.zip

I'm using these settings:
[printer:Duplicator 4 (singolo)]
[print:Duplicator 4 (0.1mm - infill 0.40)]
[filament:1.75 - BIANCO 210°]

[whosawhatsis]

This relates to a larger problem with the way the need for supports is evaluated, and I think it relates to the automatic brim discussion in #1316. The problem here is that the overhang does not exceed the support threshold angle because both sides slope up at steeper angles than that threshold. Because there are no downward-facing faces, just the edge that is completely unsupported, the support algorithm is not triggered, though the automatic brim algorithm we discuss in that issue should detect these, as well as solving for the area that needs to be included in the support structure around the overhanging edge.

[NinjaCross]

Thanks for the feedback.
Unfortunately this is a big problem for me at the moment, since I need to urgently print that object.
Do you know a fast workaround/trick/setting to force Slic3r to generate the needed supports without manually create them directly into the model ?

[NinjaCross]

Please note that inclinating the model, the missing support structures are generated.
Unfortunately this doubles the build time... so this is not an acceptable solution.

[whosawhatsis]

The quickest solution would be to design in some structures to support the edges rather than depending on Slic3r-generated supports to do the job.

[NinjaCross]

Thankyou for the reply.
Unfortunately, as I said, manually creating the support structures is not a suitable solution

[lordofhyphens]

Is this still a problem on 1.2.9?

[NinjaCross]

Unfortunately, due to this (and other problems) I had to abandon the usage of Slic3r in favour of a different software, so I hadn't had the chance to check it.

[xoan]

@lordofhyphens:

Is this still a problem on 1.2.9?

Seems to be solved.

[lordofhyphens]

Thanks