Is anyone running OrcaSlicer? Either there’s an issue with my network or access to OrcaSlicer has been broken with the Beta Firmware. I can access but when I try to send a file to the printer I get an FTP error. Have tried it on a couple of different boxes and all give the same error.
Yes , As mentioned above, I’m having the same issue. I’m back to 1.03.0.
Damn you have over a .4 difference in your holes from design to actual physical hole? That is awful! What kind of filament are you using to get such an extreme difference? My Bambu Lab printers are accurate with holes to .1-.15. I design a 3mm hole to be 3.1 to fit a 3mm magnet. I do the same for a 6mm magnet and 10mm magnet.
You can simply go back to your 3mf and adjust the x-y hole compensation.
Well, I recently experienced the impact of these changes. While it’s a fantastic update that enhances the accuracy of parts fitting for the future, it completely disrupts previous settings. I have a business that designs and sells 1/12 scale action figure miniatures, vehicles, dioramas, etc. Most of my parts are already printed and stored in drawers.
Yesterday, I printed a 12” by 10” castle diorama wall with a hole for plugging in various parts like light sconces and tiles. Unfortunately, none of these parts fit into the hole anymore. This change does not seem to be limited to just circle holes but squares also.
Sanding the 2 square holes would be nearly impossible due to its angle. To avoid wasting this 7-hour print, I’ll have to sand down eight different parts to fit the whole. And let me tell you, I absolutely detest sanding! I hate sanding plastic, metal car bodies, and wood. Ever since I was a kid, I’ve had a strong aversion to sanding anything. I do a bit of sanding on the helicopter I build, where the supports hold up the cockpit, but it only takes about 20 minutes. The plastic dust just gets everywhere. I suppose I’ll go outside and do it instead of in my apartment. It’ll probably take an hour to sand eight parts.
The image button is missing so I’m unable to post a picture.
Confirmed that OrcaSlicer is broken with the beta firmware. I downgraded and am once again able to send files to the printer.
Also tried to give feedback regarding the chronic spaghetti detection errors I’m receiving on the firmware and got a canned, adjust settings. I sent a follow up trying to explain that I’m only receiving the errors with the beta firmware, hopefully I was clear enough. I’ve since rolled back to the official release, for those wanting but didn’t receive an invite I’ve seen nothing to make me want to keep it and enough that I decided to roll it back.
I think it would be good, that there would be an option in BS to suppress the new auto hole correction.
That toggle should be default “on” for all projects that have been created for the H2D before a certain time stamp.
New projects for the H2D should have the opposite by default.
We must get through this though period one time to get it out of the way.
I have been running a cold pull in the new beta, and it gives a Z-homing error, when you start the cold pull while the home position is still known (ie. after a manual homing or a print interrupt)?
When there is no home position known (ie. after the normal end of a print), it performs a normal homing sequence and does not run into an error.
Anyone having encountered this issue also?
I already reported an issue @ Bambu Support
There is a similar homing bug on the H2S.
Has this eventually been fixed in the final H2S firmware version?
Still a bit weird that it flows into the H2D beta again.
I just used the Handy app to roll back the firmware. First time I have ever felt the need to do that. I agree Bambu has to put in a toggle option to suppress the hole changes otherwise that is going to mess up everyones prior designs and all of Makerworld designs would be affected.
Thank you for letting me know.
Could you please send me a private message with the ticket ID so we can look into the reported issue?
Thank you.
@JGrimm @edsped @elab-programmer
Could you please let me know if you already opened a ticket to share more information and the log files?
If so, please send me a private message with the Ticket ID.
This helps our team to identify the root cause of the problem and find a solution.
Thank you
Kind reminder to everyone testing the Public Beta versions:
If you find specific issues, bugs, or suggestion for improvement, we would appreciate it if you can share it via the Beta Feedback form.
Opening a ticket is the best way to report a problem, and the fastest way for our team to get the logs and identify the issue.
Thanks to everyone helping us make the firmware better! 
1 Like
This bug has not been fixed in the H2S firmware.
Agreed but I wouldn’t be surprised that the firmware builds probably share a good chunk of common code.
Still this issue was already reported in April for the H2S. There are some fairly simple workarounds like printer restart, or just repeat the cold pull after the error.
Probably nobody encountered this during H2S Beta.
Hopefully this will bring awareness to both bugs and result in a fix
I remember reading somewhere that Bambu’s moving toward a modular-based approach to firmware, so that would make sense.
If there is a ticket opened about this issue, I can look into it and check if others reported it. The team can then put it on the list to verify in the next Beta.
Just as mentioned before, it is important to open tickets via the Beta portal to ensure it is noted. 
I already shared my ticket number with you.