Seriously interested, how many bugs are you coming into using Studio?
I’m finding something “up” about once a week at the moment.
The issues page has over 3000 open bugs logged.
Luckily, only resulting in 1 failed print but material selection, slicing quality/print quality issues that have been a bit of a pain.
Are serious users moving to another slicer for accurate and reliable prints?
I’ve used Studio for every print I’ve done on my H2C since I got it. I really haven’t found any bugs that caused any issues for me, but I do all my model manipulation outside of studio, and only paint supports and do move/scale, assign filaments and slice stuff inside studio. I guess I have had some problems with Studio crashing importing rather large .stp files, but I export them as .stl, and they import fine.
For everything other than the H2C, I use Orca. It’s not really significantly better, it just supports all of my other printers more easily than Studio does.
I usually try to avoid supports if I can but sometimes use height modifiers which caused one of the failures.
I have been importing at 3mf, but given some nuances with materials and colours I may revert to stl.
Your post assumes that 3,000 open reports equals 3,000 actual bugs. That depends on how we define “bug.” In plain terms, I would define a bug as:
Using that definition, the number of true bugs is likely smaller. Many reports I’ve read are feature requests, usability improvements, or workflow preferences rather than defects that break functionality.
Regarding slicers: most free options such as Cura, PrusaSlicer, Bambu Studio, and OrcaSlicer share common open-source roots in Slic3r and have influenced each other over time. OrcaSlicer is a fork of Bambu Studio, which itself incorporates work derived from earlier open-source projects from Prusa and Cura that Bambu left out when they forked Prusa and Cura.
The paid slicer that comes up most often is Simplify3D. It has faced criticism for slow development cycles and for lagging behind open-source competitors in feature updates. There are several long-form reviews discussing this history, including YouTuber Teaching Tech’s post that although five years ago, is still on point:
View his other posts on slicers to get a good view of the industry slicer landscape.
The broader issue is economic: competing against capable free software makes sustained commercial development difficult in this space. It’s hard to establish value wen the current product is "Chabuduo" (差不多).
Although I’m a huge fan of open source and an active Linux supporter, I cite some of my favorite technologies such as Linux(Ubuntu and Mint distros), FreeCAD (in development for 20+ years) and now I ad Slicers, as example of the upside and the downside of open source. On one hand, you get decent product with a full money back guarantee!!! 
But on the other, you get what you paid for. shrug:man_shrugging:
You won’t like this answer: This is normal for any large software project. There are always more bugs than there are engineers available to fix them. This is not a problem unique to Bambu.
Check the issue list for OrcaSlicer: Over 1,500 open issues. PrusaSlicer’s issue list has over 5,000 open issues (and they aren’t even as well categorized as Bambu’s).
Doesn’t mean I like it. But that’s the reality of software development.
I think it’s also good to remember that these aren’t all actual bugs. Across all these slicer platforms there are lots of “the software doesn’t do exactly the one little thing unique to my workflow” issues.
some enterprises would sacrifice chickens and goats over active volcanos if it meant they only received 1 bug/wk. To an open-to-the-public system with maybe a million users, they’re doing fine in this regard
The more people who interact with a piece of software, the bigger the issues list will be. Some issues will be actual bugs. Some will be “it doesn’t have a way to do this thing I want to do”. Some will be duplicates. And some will be operator-error.
You can’t judge the quality of the software based on bug reports alone, you also have to consider the denominator, how many systems are in operation and capable of generating bugs.
Bambu has a massive user base. Actual numbers aren’t available but they recently said there are 10M active monthly users on MakerWorld. Lets assume they’re all slicing with Studio and posting issues when they “discover” one, and that’s where 3000 “bugs” come from.
3000 bugs out of 10M users, assuming one user per bug, accounts for a scant 0.03% of the user base, one out of every 3333 users. The real number is likely quite a bit larger, since some users are going to be reporting multiple issues. If on average a typical user reports two bugs, it’s one out of every 6666 users.
3000 issues represents an tiny percentage of the total user base who are reporting “problems”. It is not suggestive of a quality issue with the software.
I’m generally really sorry for triggering so many software developers and management consultants here.
I get it I do. Bambu Studio and Bambu’s printers aren’t the first things I’ve used that have software which is developed. Ive used Prusa Slicer for many years, Cura before that, I didnt pay or support either. I moved away from Cura not necessarily because it had issues but because Prusa Slicer matched my use case better and facilitated better results. I didnt own an UltiMaker printer. When I used Prusa Slicer I didnt own a Prusa printer. So many open source products, too many to list. And yes, they weren’t perfect.
But, can I recall encountering behaviour that caused me to spend time troubleshooting, retracing my steps, trying to reproduce, or just wondering “wtf happened there?”, not very frequently. Often issues are uncommon ans/or inconsequential. The same goes with all the other software I use, Mint (mentioned in a reply and I use this), Windows, Firefox, really low volume software for control systems, forked firmware for IoT devices, and so on. At work I’m responsible for systems that depend on software from people like Microsoft, and yes, I have had to raise issues with Microsoft, but rarely.
I get that bugs, feature, requests, mistakes, whatever, scales with volume, but what else scales with volume is the development and test programs. So in the end, the number of issues you encounter as 1 of 10 million is rare, like lottery rare. I’m also aware that 1 bug report might represent 1 or 10,000 instances so it’s not a metric that can be used anywhere (but it is the same for all software).
I didnt make any assumptions. The Git page is managed, if its not a “bug” then it can be recatogorised. The figure I offered was for those categorised as “bugs”. There is some conjecture about what’s the normal amount of issues. What is the normal amount of issues? And your right, this might be normal. Who want to raise bug reports, its a real pig so what you see in reported issues is a slice of reality. In most cases as a bug reporter you will have to evidence:
And thats on the bug reporter. 
yay.. wheres the gasslight emoji
Bambu, from the marketing approach and how users (and influencers) feel they interact with the product, is not targeting the fixer, or engineer, they are targeting the click-and-play adopters, people that want a 3D printer as a means to an end, not part of the journey. If you’re not an Apple user and you ask someone that will only use Apple kit they’ll tell you “It just works”. I’d say Apple have had some success. And actually, one of the main reason for buying Bambu was that most people’s experience is that it just works (and well most of the time 
).
Ive read some posts and some bug reports, there’s a lot going on. I work in a very niche engineering business (if it helps call it aerospace). They will spend $20,000 on a printer, not because its special but because it just works all the time every time exactly how they expect. And if it doesnt the manufacture takes the lead and runs with it. I’m not saying a $2k printer (and software) is comparable to a $20k one (they are closer than they used to be), but if the competitors product struggles with consistency they wont buy it. That’s not conjecture, I can tell you I’ve been in the room when that decision was made. And thats fine, its not a target market, and bugs will be recognised as “undocumented features”.
I think Jon is right.