emkay wrote:Hi. Not sure I can help
even just bouncing ideas helps so

thanks
emkay wrote:It seems to me that the behaviour you're running into is the fact that "Tops" and Bottoms" are always inside perimeters. And what you're doing is a "bridge" of sorts, but even more significantly/specifically it's more of an "Unsupported Top". Which is an overall limitation of this manufacturing process and is partially the reason for supports/infills/etc. The design doesn't necessarily take into consideration the limits of FDM in a few areas.
yes, and no. for start, to remove the "limits of FDM" thing - let's say that cura and slic3r print this without a problem

.. so I would move to limits of s3d and how to overcome them as FDM prints this, without a problem, when sliced differently.
I found few threads that talk about this perimeter / bridge issue with s3d but I hoped that 50% of overlap would solve that problem. if there's a 50% overlap between infill and perimeter the "line" of the infill should start at the middle of the perimeter and end at the middle of the perimeter on the other side. what I see in g-code preview is that infill goes up to perimeter so .. where's overlap? (might be bug in g-code preview and not in slicing as I was not looking at g-code but only at preview, but again, I see that in print they don't overlap so..)
if I make a wall thicker wrt "min extruded line" (without changing model just reduce the extruded line width) then it prints 2 perimeters and then lays the bridge over the rest of the wall, so the algo here is almost decent, but why not going over perimeter if perimeter overlap is set is imo bug.
emkay wrote:
design the model with thicker walls so that it can accommodate your chosen number of perimeters, but also more so that it can build a structure onto which identified bridges can be built. Since the software will rightfully never compromise the number of perimeters, there simply is no room to incorporate your chosen overrides. And even then, the size of the model may be asking a lot for the bridging capabilities of your material choice.
why "rightfully never compromise number of perimeters", I doubt that's rightfull in most cases. in most cases it would be better to cut on a perimeter or two and print infill .. in my experience in 99% cases when you print a "solid layer" only 1 perimeter is best option.. it increases many quality aspects of the print. so
feature request separate number of perimeters for "solid layers" and rest of the print

.. even better separate top layers, bottom layer, solid layers and other layers
emkay wrote:
Use some sort of support. Yes, this is tricky in this case since it's inside and needs to be removed. Unfortunately that's one of the biggest puzzles when working with FDM. Things like dissolvable support materials are some of the more complicated solutions to this problem. D) Design and assemble it completely differently
soluble support is not big of a problem but support is not needed in this case (as I already said, other slicers get this done ok) and even s3d would get it done ok just if it respected the 50% overlap, I'm looking it print, it stops extruding at the edge of the print, the bridge looks perfect, and then it start printing from that side back and kills the previous line as it was not stuck to the wall properly .. adding another half of perimeter there would solve the problem in this case completely .. why is there no overlap is imo bug..
support system is why I purchased s3d really, as (I tried "fixed" version of s3d first of course) it looked like the only one that properly give you a choice where you want your support and where you don't want it .. without me having to post process the g-code, edit skeinforge source for every tricky print etc ... (and I hate python with all my heart so it's not a pleasant thing to do for me) ... and while I'm not yet tested the support system of s3d yet, so far I'm very happy with it .. just that in this case, support is not necesary

and different design .. also not necesary .. this as is should work flawlessly really

... just requires calibrated machine and properly configured slicer. imo I'm having issues configuring s3d as I'm used to bit different terminology so stuff like "extra inflation distance" make zero sense to me

(ok trial and error shown me what it does but.. nice that app has a small question mark in top right menu but it does nothing when you click it to a option)
emkay wrote:
I thought I'd also point out that for some reason the model still has flipped normals despite being marked as "fixed".
yeah I know, I sent object designer a (repaired) version

netfabb allows you to solve that easily, but does not change the way s3d sliced it

( ... the part that's repaired is available
http://infinit.io/_/ZFtQ8Qa
emkay wrote:
I also wanted to point out that this also demonstrates the major broken feature in that other post you linked to. Even if you, for instance, modelled it with thicker walls, or used some other solution: Simplify3D still won't identify the more common "bridges" that are at the air entry and exit points of the whistle. So no matter what we do, we don't have control over those areas until this feature is developed to completion.
well on this whistle object s3d properly detected all bridges! it didn't handle them the way I'd liked to but they are properly detected, that whole layer is marked in g-code as bridge (except perimeters of course, I do agree with the other bug about perimeters not being part of the bridge) and is printed slowly etc .. as bridging config sets .. and depending on how big you set the area the bridge is imo properly detected. now it only needs to be handled better .. solving that different perimeter number on different type of layers would help improve greatly, also giving few more options for bridge..