OK, I’ve an H2D, 2 AMS2 and an HT. One AMS2 on each nozzle and the HT on the Left Nozzle.
I sync the filaments, and they show properly. Then I slice. But ALWAYS the filament setup is BACKwards to what is in the machine. I put the support filament in the right AMS and the main material in the left and It will inevitably swap positions. If I happen to swap places, it does the exact opposite. I select convenience mode and it works correctly with ZERO alterations to the material used or the time consumed. (2 color print) It drives me insane. Makes zero sense that the slicer won’t look at where the filaments are and PROPERLY slice under the filament savings mode. Stupid software. Rant off.
You almost certainly have a physical PTFE swap or a AMS configuration issue.
On your printer, go to the filament screen and hit the screw driver wrench button in the bottom right corner. Make sure your AMS units are shown to be connected to the print heads you expect.
Trace your PTFE tubes from the AMS units by hand all the way to the PTFE inlets. The left nozzle is fed by the bottom inlet, the right nozzle is fed by the top inlet.
Inside the printer, make sure the tubes are also connected correctly at the bufffer - left nozzle should be the bottom, right nozzle should be the top.
If all of this has been verified correct, on the printer go to the control panel, settings, AMS options, scroll down and select Arrange AMS order.
BS dude, BS, Left is left, right is right, I have 2500 hours on the printer. AMS with the support is on the left nozzle plain white pla is on the RIght nozzle. It shows in the slicer exactly how it is properly set up at the machine. I have to go in and reslice using convenience mode to get it to slice with the correct placement (what it reads from the machine btw) it is entirely the slicer programming.
Ok, so is that a justification for your behavior? I’m trying to help you, I’m just a another Bambu owner, am I not allowed to come to a conclusion you don’t like? Am I allowed to make mistakes?
We’re all just trying to help each other out, don’t be a ■■■■■.
Well, I guess, this happens when using Filament Saving Mode while slicing. As mentioned by @J.lifer, using Convenience Mode the issue is fixed. So the slicer does exactly what it is supposed to do and the little window showing the options states exactly so - using Filament saving mode you have to place the filament accordingly, using Convenience Mode the slicer uses the configuration of the printer.
And these two are the supposed filament savings. OVER 21 Hours of print time and 390 gr of filament. That is almost double the filament. and well over 2x the time used. And on this set of models, it happens every slice. STUPID
Okay, so there is a bug in the filament savings calculation - but do you agree that the filament savings explanation (it expects you to rearrange filaments in the AMS units) now makes sense, or is there a separate issue there as well?
I’d really like to help you, but I use the Filament Track Switch, so I can’t reproduce it. The FTS seems to prevent this issue from ever happening.
First of all, thank you so much for providing the screenshots - they really helped clarify what’s going on. With that information, I was able to track down the issue on GitHub right away. It turns out to be a bug in the current Slicer software. The bug has already been logged and assigned to a Bambu team member.
Bambu has already released a fix for the H2C devices. For the H2D, the issue remains unresolved, as it was only recently reported.
According to Bambu, the fix is supposed to be included in the next release: Unfortunately, the person who reported the problem hasn’t responded, which is, of course, the worst-case scenario. Quote from a Bambu programmer:
Just a quick note for you: it really would have helped if you had shared the screenshots yourself instead of venting your frustration at others. Also, your post is in the wrong section, respectively, not correctly tagged.
Altogether, this gives the impression that you’re not actually looking for a solution, but mainly wanting to vent.
Without dann2707’s help, no one would know exactly what this is all about - you can thank him.
Being honest the custom mode doesn’t annoy me that much on reflection. It was the fact that pressing convenience mode did the exact same thing and ironically made it significantly more inconvenient.
Dude, I vented at the system… and then at someone who gave silly advice. I’ve had this machine for 13 MONTHS. It’s not an AMS setup, never was. And this has been this way since the beginning. Early X1CC owner, and 2 nozzles really made for lots of bad programming. I cannot believe this hadn’t been reported 12 months ago, But yeah, I can see Bambu ignoring it. The H2D is a good printer, with numerous bugs that have been slightly fixed. I still have major stringing on my multi color prints (tower) if I use anything but pla and petg. Haven’t figured that out yet either. The H2D just seems to have become a stepchild after the quick intro of the H2C. Updates are slow, and lag behind the more expensive machine. I guess being a quick adopter was again wrong thing to do.
You might have posted the issue directly on GitHub yourself, reaching the developers just as everyone else on the forum does. Even if you weren’t aware of that option, someone here would have pointed it out to you right away. You could have done that right now, but instead you decided to go on another rant.
As mentioned above, the fix for the H2C has already been released. However, there are still implementation issues with the H2D because users experiencing the problem, like you, often choose to complain rather than support the developers by providing logs or screenshots. The developers even specifically requested feedback in the GitHub thread, but unfortunately no one responded.
I understand your concerns, but it’s hard to make progress for developers when feedback only comes in the form of rants rather than contributions. Have you submitted a bug report or opened a thread about the issue earlier on? No, none. I don’t see any topics from months ago; in fact, I only see one topic, this.
Everyone understands your frustration, but it’s also clear to others whether you’re genuinely trying to work toward a solution or doing the opposite by directing your frustration at the community, which isn’t at fault.
I’d really encourage you to share the information the developers need instead of holding it back, because that makes it harder for anyone to take your concerns seriously.
