As the title says, there’s no point on having classic as default wall generator in Bambu Studio. Arachne is far superior regarding quality and dimension accuracy so leave classic as the legacy option. Gosh, it’s even creating noobish quality comparisons where people simply doesn’t know about it and complain that the x1c is unable to print fine text while others can (as prusaslicer is actually using arachne as default generator):
It’s so simple of a change that I can’t imagine why it hasn’t been done yet
If all models pre-dating Arachne wall generation were developed to print well against classic wall generation, you might imagine that changing Arachne to be the default could cause a lot of pre-existing models to print unpredictably.
Arachne has been found in my personal experience to have generated unexpected holes on some surfaces, holes that obviously don’t exist in the STL model.
Making blanket statements based off of some linked YouTube video feels a bit short sighted without consideration for years and years of prints based on classic wall generation.
People claiming the X1/P1P can’t do this and that are likely ignorant and that’s not a problem you can solve by changing defaults.
Following your very logic, as you said OLD models tend to modify its geometry to stand to a flawed generation where certaing bodys could only be done with a minimum divisor of the wall width or filling gaps.
So when you have a superior wall generator, what you need to change is the very few models that doesn’t fit in it, and not sticking on using a legacy method just because those models are there.
With your blanket free long sight we still would be using mainframes from the 70’s. Or floppy disks, or CD’s. They work and we only have to give the data a form so it fits in them.
There are some reason that classic is still available, sometime it suit better than arachne even if I am a fan of arachne.
Also I would suggest to set outer perimeters a bit thinner (0.35mm) when using arachne, at least in some case I got artifacts using 0.42mm oute wall width + arachne mode
I think the best way to handle it is to create your own “standard” profiles based on system profiles and change some of the settings to make more sense.
Arachne is one.
Another is to change the default infill pattern to one that does not overlap lines on the same layer (which creates so many questions on the forum when the nozzle hits the bumps).
I imagine some might want a different seam position.
I change elephant foot because it is to small for my use.
Indeed. I honestly don’t know how so many people are able to use the default profiles with no changes – and achieve amazing prints. Or so they say the prints look amazing. I suppose everyone has different standards though.
Don’t worry, we will call you from the Tower of Jerusalem and accept you.
Again, I am not vouching for banning classic, just for making Arachne default in default profiles. Of course you can make custom profiles and fine tune whatever you want, but the only thing i am saying is that for starters, right now, having arachne as default would be much more useful and intuitive than having classic,and a step forward in the right direction.
After all Prusaslicer is already doing it … and not only for Prusa printers.
Things that Arachne brought were (almost all) introduced few years before by Simplify3D with 4.0 while they still had some developers working for them and going forward to 4.1.2 they perfected it so this thin wall, gap filling, thing works like a charm for years (contrary to number of other things) and is available, of course, in 5.0 too with some changes that broke whole bunch of stuff, ppl reported, S3D kinda fixed things and now in 5.1 it works ok (not worth the penny but …). Now ignoring S3D, the point is that whatever issue new slicing engine introduces to “old designs” the proper course of action is to report these issues (everywhere, cura, slic3r, prusaslicer, bambustudio… so it does not get missed) so that the algorithm can be fixed. Switching temporarily to the “old style slicing” is ok to solve the problem you encounter but you should always use the latest slicing algorithm and report any issues you find (object, settings, code, images…) as that is the only way to fix things… if S3D without any developers could get their slicing engine to work ffs we can make cura/slic3r and the forks to work as well with so many developers having access to the code
with so many developers having access to the code