I didn't say this is a bug, only that it looks like a bug. I would not dare to blame S3D publicly when I'm not 100% confident that I have paid my dues already. This is up to the vendor to say this word, not me.
Look, I thought this forum is about "Troubleshooting and Bug Reports" (see the name somewhere?). I have put the model here, I said everything I thought was necessary (and presumably it was enough since nobody asked for any more details). The reason I opened this topic is to inform S3D developers something wrong might be going on with 4.1.1.
What did I get? Troubleshooting? No, few clever clogs individuals mumbling about S3D being perfect and blaming the model (which, I repeat myself, every other slicer has no problem with, even earlier versions of Simplify3D) without ANY analysis or proof. Maybe you now think of responding you are not here to analyse anything - well, then better be quiet and leave the space to people who are willing to help, because what you said in your first two posts does not have any added value to this topic. Plus, 4.1.1 release notes say about improved vase mode algorithms, so I thought this place is a good start to say something is wrong with 4.1.1. Still no bug word
you as an example wrote few comments to this thread and it took you 3 attempts to be finally able to produce some sense in your comment. You could spare this forum the first two comments and go straight to the 3rd you posted, because only that one makes sense.
Anyway, I have sorted this one out with S3D support, they know about this, I have rolled back to 4.0.1, which for whatever reason works fine even with my buggy model. I consider this topic resolved
Last edited by s3030150
on Wed Jan 02, 2019 1:40 pm, edited 1 time in total.