you must have a separate issue, It only takes a minute or so to level the entire bed for me, on the latest beta firmware v01.01.02.04
Thanks of this, I must check it out.
1 Like
@SupportAssistant Since the latest beta I am experiencing the same behaviour. But even worse for me; the blob stuck to the nozzle, dried, hardened and forcefully stopped the little ooze lid ( the one that switches from one nozzle to the other) from moving. It bend the lid so badly I had to replace it.
3 Likes
I think I’m having multiple issues related to the toolhead and/or wiring going to the tool head. My Left nozzle temps are off 10-15*c from the right nozzle. Its to the point where I don’t print with it at all right now. My probing works good sometimes and others it takes a really long time to probe as it does certain spots 5-6 bumps in one spot.
I have done a hand full of higher temp prints so I hope thats not what caused it and I just ended up getting a unit with some sort of defect that can be replaced or fixed for good.
@SupportAssistant Yes this is super important to get addressed. I’ve noticed huge blobs as well so I have to revert my firmware now.
1 Like
I waited to reply to this. Part of the beta process “is x testing out new features. That’s, on top of, as said " trying” catch bugs, testing stability, and other mechanical things that are inherent in new builds. Or at least that’s what I was told at the beginning of my 12 year beta test period with Adobe and Matrox Electronics, in addition to my 5 years with Motorola as far as electronics are concerned. I also flew beta (test) fuels in rc helicopters for about 3 years, which also, involved bring sent raw materials at times, and mixing up my own fuel(which was awesome)!
It goes without saying that part of the point of having betas is to expand the footprint of the device and it’s software. You will see more(hopefully) in a 1000 group beta, than you will in 100. Simply “because” not everyone uses the device the same, or at the same level. And for sure, if you’re on beta, you do not(should not for sure) skip any builds. There are things underneath, that are just as important as on the surface, as far as “bug list improvements or features”… There’s allot to beta, if you want to make it so. And then, there can be nothing to it also, if a person isn’t active. Inherently these “tinkering” type of things appeal to me… Always has, and always will!
1 Like
I agree with this as the main tenet, and I disagree with both regarding the other issues. You aren’t improving your yield by weeding people out. You’re narrowing it. And, besides, it should be Bambu setting policy, if that’s what they want, not random others. But, this isn’t the hill I’m going to die on or fight for, so, I’ll happily still take myself out at the next stable rlease just because I don’t need the aggravation.
I purchased my printer to use it, not to slave it to a beta process. I’m happy to help identify non-obvious bugs that I may run across in the course of using it, but if there’s an apparently flawed beta release that will reportedly cause major interference in my use of the machine, that’s not my fault. I’m sorry, I have real work to do. If you don’t, then good for you. Enjoy your retirement and your second career as a full-time beta tester, regardless of how it affects your productivity or ability to use your machine.
I enrolled in beta because the prior stable release had a number of significant shortfalls of relevance to me that the good beta I did install helped resolve. I didn’t and don’t have time to just sit around a wait for the next stable release that includes those features, especially when they’re mission critical. So, no, I don’t apologize. Not at all. This is fully legitimate usage, especially under the circumstances.
I think you’re misunderstanding my stance. Personally, I don’t think you should leave. You have valuable feedback “in your usage”… That is the point. Putting it simple: you don’t use your machine like me and vice versa. And the betas are to avoid pushing out updates that will crash or hinder “all the machines in the wild”. Small group as a test, then increase in size…
And I use Handy “A TON”! It’s my primary vehicle. I don’t use the desktop, unless I have to, because I work a ton of hours at my full-time job. So, I don’t have a ton of spare time myself, even at work. But I can go glance at Handy to make sure everything’s going the way it should. I have real work to do, as you said also. But if something weird happens in the “context of my workflow”, I would like to report it.
2 Likes
Fair enough. In that case, I only disagree with @Mac3D . This isn’t a zero sum game. Quite simply, if Bambu wants more yield, they should just accelerate adding more new people or stratifying who they release to and when. They gain nothing by dropping beta testers.
1 Like
Yes, I meant to advise(but forgot), that my response was in no way directed at you.
Except I would say, if you don’t want to run the risk of your machine going completely down, then you may want to exit. That was my only thought, as betas can be very unstable at times…
Yes, That’s why I’ve decided to wait it out on 01.01.02.00 until either another not-obviously-problematic-beta arrives, or a stable release exit materializes, whichever happens first.
For the record, I have submitted one ticket, which got resolved, and I will submit more to whatever degree I run across more problems.
1 Like
Understandable… I don’t blame you…
Prime tower, or skirt until layer 10, this is my solution for now, but they REALLY need to fix this annoying behavior. @SupportAssistant can we have an update on this? as it’s really a very minor and easy fix, simply shift the coordinate a couple mms away?
i wasnt able to join the beta on the p1s and now im also not able to join on the h2d… i activated beta about 2 years agon in the app LOL
Our team is working hard on a new Beta build which should be fixing a few of the issues encountered. I will share an update as soon as it becomes available.
We appreciate everyone who is helping us make this better!
6 Likes
It’s extremely frustrating that they continue to call it an “open” beta when there is absolutely nothing open about it. At this point, it’s closer to a locked-down internal test disguised as public access.
Many of us are ready and willing to test the features that should already be part of the stock firmware. But they’ll likely repeat the same mistake they made with the X1 Carbon—pushing out a firmware packed with fresh bugs that any properly managed beta should have caught long before release.
1 Like
Uhm, no, and I don’t think you would want to have this particular beta ver anyway, it has 1 severe bug that would damage your printer and 1 mildly severe bug that would ruin your print quality from time to time, so no don’t feel frustrated for not being fked up yet 
Also even if it’s an open beta, it simply means that you’re in a pool and it’s very common practice to draw from the pool for, as an example, 10000 testers and then release it in waves. And they would usually stop pushing new waves if any severe bug has been detected or reported. Which is for the users good.
2 Likes
Thank you everyone for your help in testing this Public Beta version.
The final firmware is now available as v01.01.02.04
A new Beta version will be available soon.
11 Likes