Slic3r has perm bugs in every version (Page 1 of 2)

used Cura Engine instead to slice files. only Cura has no way to set angle of support like Slic3r.

I cant get good screen shots of how crazy Gcode looks but my older versions would not slice one of the models without error 'out of memory' and another stl file wouldnt do support right. so I tried my other laptop with newer versions and it was worse on support and infil on both files so I installed the latest version of RH with all new slicers and still had to use Cura due to newest Slic3r just messed up infil and walls too, instead of helping. I tried hundreds of settings the last 2 days and never fixed Slic3r issues but 20mins in Cura did it and I never used it b4 lol. if they would add a couple features Slic3r has Id switch for good. been working with Reem from 'make it printable' lately (there app is on Thiniverse now for repairs) I signed as beta tester and he's been helping me test bad files I have for repairs with his software. these files are the ones had issues with so some of it may be file errors hidden that even Netfab dont see but seems Slic3r has a couple bugs that have given me problems since the 1st version once in a while and it seems related to its bad habit of Caching old Gcode/settings and mixing them in with next couple slice attempts til over writen a couple times like most users have noticed. hence lots more slicer apps trying to do better. Slic3r acts like it has ghost settings left even after saving new settings. it causes some very odd results as posted in OP. the support shelves as I call them are very odd mostly like fender extensions on cars plus some stray mid air support around model even at top of models. then deleting thin peremeters not just windows but walls etc and not making any infil no matter how hard you set it to do so it wants to make whispy shells with large holes and details missing. cant take that BS anymore. I did not get into 3D printing so I could redesign all apps that are needed to just use printer. at that rate only Rocket scientists should consider a 3D printer as viable hobby.

I broke down each step of slicing starting at bottom (Raft) and tried lots of settings one at a time and could not find one that worked as it should and has with past models/stl files. then done same for peremeters, layers, infil, support etc. only got a few worse results but none that could be printed correct if at all using any version of Slic3r for these repaired files.

but within 1st 30min of use of Cura Engine and a couple setting tweaks got great Gcode results.

that tells me Cura knows something about stl files that Slic3r still dont. now if we just knew what that is.

I cant get Slic3r to make usable Gcode to print.
yep done printer and nozzle sizes.
I dont understand how support and raft can be ignored or extend support beyond model like it trys to do with only these repaired files. also infil is ignored and parts of details and walls deleted during slicing, just on files that had errors and dont now. same for old versions saying 'memory full' what memory? files are not that huge must be an error acting like unmanifold object trying to map entire print area or something. had these same issues b4 on a few files but mostly thoughs still with errors showing in Netfab etc. odd how repaired files cause this only in Slic3r all versions. some error invisible to repair apps and Slic3r must be doing it but Cura has no problem with it some how. seems Slic3r has a bug that never got fixed after all the updates same as the changed settings being forgotten for a couple trys on half the old versions.

just when you get comfortable using an app they "update" part of it and have to learn again how to use but still has some old bugs.

wish I could post a 3D movable image of the weird Gcodes it makes. cant see it good in still image the Support once you force it looks like a short wall around areas that use it and its about 4mm-6mmbeyond outer edges of model. plus some in mid air like odd shaped towers to top of model but not connected to model in random spots not where any is needed and some spots its needed get none. there is no way to make this happen in settings. saw similar once on a bad file with unmanifold item where short boxes on model got extended to top layer height. but never on repaired model & never away from model body where nothing is above or below the excess material. it looks like material is even laid on top of brims.

its not my computers or anything as I can still slice other files just fine same as b4 with same apps. just this type files are too much for Slic3r to handle, and Myself nor Reem (make it printable) nor Netfab can see any reason for these files to cause it. that only leaves Slic3r as the issue. is there a beta library running in back ground for Slic3r that may have corrupted data in all versions packaged with install maybe? I am sure I am not the only one to have these issues even if most likely never had a bad file repaired b4 or at least not very bad multiple errors. maybe they just trashed the file giving issues instead of working through it. I am sure Slic3r has a small glitch causing this rare freak event. and after installed complete all new version which also packaged other slicers which do the job fine and on a PC with up to date Comodo security, all else is ruled out.

RH 1.6.2 is the newest ver I just installed and used for this, it comes with the Slic3r ver 1.2.9 and all prev vers on web site say they have bugs not fixed but I also have used most versions with no real issues except for some of these bad files even after repaired to Netfab satisfaction.

how do I upload an stl?

I would like to try having somebody slice it with Slic3r and see how it goes. its for my SD2 with .35mm nozzle, rectilinear support 1.5mm spaed angled 20 degrees plus 1 layer raft and brim. 30 percent infil

mine only has "upload image"

maybe a zip

excellent work, as usual, Pirvan

Seems pretty obvious to me that there are some major problems with that model - and not the slicing software...

One would think that if you keep having the same errors with different versions of a software one might actually consider the model as the source of the problem, not the software.  Or at least investigate the possibility a little more.

Just because something is manifold does not mean it is suitable for 3d printing.

but hey, I am not an "expert" by any means...

also the thicker perimeters your printer makes as thinnest capable the more holes there will be in Gcode since it cant print that thin. and 1mm thin walls are useless as model anyhow. but if repair apps nor slicers dont see or show this and why its so, how can we know what needs done to fix it?

I said the apps dont see many of these errors nor do they let user know why commands or errors did not get done or why app failed to slice/repair. it does not mean model is the reason for said failures just because app did not see/fix/report them. your taking it out of context.

and as for " address your concerns with the program and it's shortcomings to the authors of said program" I tried that but never get reply likely due to being free apps. or in the case of Skeinforge there is nobody to contact and hasnt been for at least over 2 years. thats why most dont use it like myself.

and statements like this "As for new people being "run off" because of a few setbacks and/or crappy models? To me, those that are that easily discouraged don't really belong in the industry to begin with. " is why 3D printing will NEVER be user friendly/plug N play as many printer makers try to sell it. also why your last comment of troubles faced by yourself at the beginning.

We (users like on this forum) are not responsible for apps made/sold by makers of said apps that have short comings, as to files with errors on depository sites those are the responsibility of designers of said files if they will take that responsibility (not likely).or moderators of said sites to delete bad files so others dont waste time with them.

as to Win10, thats another issue that has lots of documentation online to support my posts and my position on it and MS. there are many thousands of people that feel the same or worse about it after trying it. its a very bad security risk to say the least.

not going off half cocked, I been working on these issues and researching the route causes for a couple of years and this topic is my conclusion of those findings. and I still dont see anything to explain it or prove my conclusions wrong. these apps are supposed to do the job intended and they have short comings in several areas of this. seems I am one of the few to discover them and say so. its not unreasonable to ask the makers of these apps to correct them to do as designed. even if just telling user "file is damaged or improperly designed beyond repair/use". instead of pretending to repair/slice and give an UN-useable file or Gcode to waste our time and material on.

also this is the largest active 3D printing forum online (navigable) and any company in the industry watches its users posts. and my past experience with business economics/sales/marketing etc has shown both the old adages still holds true "the customers always right" and "the squeaky wheel gets the lube". I think this is the quickest way to get issues corrected.