I am trying to add a custom filament (Inland PLA, I just got some and want to start the dialing process) to my H2C’s AMS. I created the custom filament and added a profile based on the Generic PLA for the H2C 0.4mm nozzle. When I try to add it, I get the following error:
“You need to select the material type and color first.” Screenshot below.
From here, I go to add it in the AMS and get the error.
This is becoming incredibly annoying because in addition, custom filament profiles I have been using for months are now throwing this error as well. Screenshot from my Polymaker HTPLA-CF, which I have been using successfully for months:
Which version of Studio are you using? Latest release 2.5.0.66?
I can’t recreate the exact issue you’re describing. However, from looking at the relevant Studio code, I can see there are only a few reasons why this alert may come up. If I can recreate the issue, we may be able to find a workaround.
Could you post one of the filament profile files which is having the issue? The new one you set up would do nicely.
Forgive me if you know already, but the files are stored in your Studio configuration folder – easiest way to get there is via the Help → Show Configuration Folder menu item. From there find the user folder. If you use Studio while logged in to BL account, there will be a sub-folder with a user number there, and another named default. Inside those will be filaments\base folder where the custom profiles live. They’ll have a .json file extension.
Also to attach a file here it must have one of the few allowed file extensions (stupid). So just rename it to add .3mf at the end.
I am using v2.5.0.66. Screenshot of that below and filament profile attached; renamed as you suggested. I also attached the filament profile of an existing filament that WAS working, but now suddenly is not. Thank you for your help!
Thanks for the followup. Well, this seems to be a tricky one. I can’t recreate it here, unfortunately, even with the profiles you uploaded. A bit stumped so far.
There are only a few reasons that error would pop up, and none of those seem to be the true cause here. Specifically, that error comes up if (Studio thinks) the filament_id or filament_type properties of the selected filament are empty, or if the nozzle temperature min/max field entries aren’t valid. (The selected color isn’t even checked, ironically.)
I also can’t determine what would have changed in the code since it had worked last – which version was that, do you recall? The last v2.4? There were definitely some changes in there for v2.5, but nothing obvious that would break existing setups.
This leaves something in your particular setup, I think, as most likely cause. I’m also not finding the same complaint/issue filed by others (although that would be easy to miss with 6K+ logged issues). My best long-shot guess so far is that some other filament profile(s) you have are interfering with the program being able to determine which filament is actually selected. How many do you have?
Are you using cloud sync with the printer? I’m not… not seeing that matter here, but it may help narrow it down.
Does it make a difference if you try to assign to an AMS slot vs. external spool?
Some things I may try if I were you… depending on patience level
Try selecting just a “Generic” filament in the AMS Material Settings dialog… does that work?
Turn off cloud sync in Studio (if enabled) and shut it down. Move most of your custom filaments out of the “user” folder into some other temporary location. Leave one for testing. Then open Studio and try to assign that filament.
I’ll keep mulling it over and update if I think of anything else. I hate unsolved riddles Any more details you coudl provide may be helpful. Perhaps zipping up all your custom profiles and posting (or DM me). Ideally I could recreate here. Mine’s an H2C also, BTW.
Okay, you’re going to hate me here… because it works perfectly now. I changed nothing. I did nothing differently. The printer and my PC have been idle all night. I didn’t even power cycle the printer or my PC! The problem has just vanished after I woke up this morning.
For what it’s worth, selecting “Generic” filaments did work before.
I think you were probably on to something with the cloud sync issues. That’s the only way I could think of that profiles that were working before might have suddenly stopped working - maybe during some cloud “trip,” they got corrupted somehow - but then re-synced overnight to good versions?
You’ve been incredibly helpful, and I will reach out if it happens again. As someone who likes to solve mysteries myself, the resolution of “it just works now idk” is incredibly unsatisfying! If there is a next time, I will reach out with the information you requested (all profiles, cloud sync status, etc.) and we can go from there.
LOL! I guess it was the sunspots… No worries, glad it’s working now, even w/out the satisfaction of solving anything. I think the profiles being somehow corrupted or not loaded correctly is the most logical so far, though why or how is a mystery (and the files you sent were fine). Keeps life more interesting I guess!
Came to the forums as I’m having the exact same issue when trying to add profile for a roll of Polymaker filament. I have a bunch of custom profiles already, so not sure what’s changed recently that’s causing this problem. It’s been a day and no luck on it fixing itself, so I’ll have to experiment and power cycle everything to see if it will sync up.
@Choggomac , I wanted to let you know that I was having exactly the same problem where I couldn’t get any of the Polymaker filaments to be accepted as a custom filament. I started of from the presets that Polymaker themselves provide and imported these into BambuStudio
Seems like I cannot add links so I advise you to google ‘Orcaslicer issues #9112’
The workaround which is described at this location solved it for me. Please ignore it’s under the Orca Slicer github, I had the problem in BambuStudio and the same workaround applied.
After I added the presets again everything worked.
e.g. Panchroma PLA@BBL P2S (doesn’t work) & Panchroma PLA @Bambu Lab P2S 0.4 nozzle (does work)
Hi @truckeic , I’ve reproduced (and worked around) the problem with the (Polymaker) Polylite PLA Pro profile. Below are the steps I took. I’m on BBS 2.5.0.66 and a P2S
I’m new to 3d printing myself so I’m not sure whether this is basic knowledge or a bug. On OrcaSlicer they graded this a bug (references in my previous post).
Disclaimer, as the Bambu Forum sees me as a new user I’m not allowed to insert screenshots so I need to be descriptive. If would still advise you to google ‘Orcaslicer issues #9112’.
One of the top proposals will take you to the Orcaslicer github but you will see that the screenshots look very similar.
Info from that location:
The AMS filament selection it doesn’t handle the printer compatibility properly. It does not read the compatible printers from the profile dependencies settings, but only from the profile name. Your profile is named “PolyLite PLA Pro @ BBL P2S”, however it’s looking for “@ Bambu Lab P2S 0.4 nozzle”, which causes this problem. By re-adding the profile, BBL will create a new profile with the full suffix which makes it usable.
In your Custom Filament overview you need to click the green edit button and add preset
Populate according to your printer and nozzle combination
Confirm that the filament info now has an entry that has the printer type and nozzle included.
Example for a P2S with 0.4nozzle:
Bambu Lab P2S 0.4 nozzle
____PolyLite PLA Pro @ BBL P2S (originally there)
____PolyLite PLA Pro @Bambu Lab P2S 0.4 nozzle (generated in step 2)
Close the interface and try to select the filament now on your AMS
Hi @demux, are you sure the “fix” isn’t simply adding a new profile? Thereby causing a re-sync with the cloud/printer perhaps, or whatever else is the underlying issue. Don’t get me wrong, I like it as a solution & explanation, but for example the original post on this thread already used the @Bambu Lab format/syntax on the file names. And whatever “fixed” it didn’t involve any actions at all.
[If the forum still doesn’t allow you to post links/images, try logging out and then back in.]
-Max
PS. This? https://github.com/OrcaSlicer/OrcaSlicer/issues/9112 ? Match '25, interesting… nice find, I didn’t think to check Orca repo. But I think the name workaround is a red herring… forcing a re-sync is the fix. And the issue with filament selection that the workaround post mentions doesn’t seem to be in the code anymore.
Hi @MaxThreeD
Thanks for the response and taking the time to look up and reference the GitHub link that showed me how to fix my problem with the Polymaker presets file.
I’m not sure what was the root cause of the behavior the OP was observing, the only thing that’s certain is that we shared the same error message. I assume that Choggomac and truckeic (both using Polymaker) are experiencing the same problem I had and can hopefully benefit from it.
Specific to the problem with the Polymaker presets file I believe syntax is a problem and not syncing. The workaround described in the GitHub is an easy way to get the syntax correct.
How I encountered the problem (reproduced with Polymaker PLA Pro, Panchroma PLA Matte, Panchroma PLA Satin & Panchroma PLA Silk all downloaded from presets.polymaker.c om
-go to File>Import and select the one you would like to add (PolyLite PLA Pro was used in this example)
This will look like:
Bambu Lab P2S 0.4 nozzle
__PolyLite PLA Pro @ BBL P2S
-If you would now like to select the Polylite PLA Pro as a filament under the Device tab it throws the error. Fairly certain it synced because I wouldn’t expect to find PolyLite Pla in the dropdown menu in case it hasn’t synced.
In general my conclusion is that you need to have the ‘@bambu Lab nozzle’ (e.g. @Bambu Lab P2S 0.4 nozzle) in the filename or it won’t work.(similarly as stated on the GitHub)
You can do this by either doing the ‘+Add Presets’ workaround or you can do this by renaming the .json & .info file manually under /AppData/Roaming/BambuStudio/user/ **/filament/base/
You’ll need to close and open BBS if you take the latter option.
This combination doesn’t throw the error:
Bambu Lab P2S 0.4 nozzle
___PolyLite PLA Pro @ BBL P2S
___PolyLite PLA Pro @ Bambu Lab P2S 0.4 nozzle
If you delete the preset that you artificially added at the bottom, the error is back.
-I reproduced this behavior on the recently released BBS 2.5.3.61.
-I tried to log out and log in again but still cannot add links nor media in my post…
ok I finally figured out what you meant by adding the .4 nozzle to the profile. That worked perfectly! Maybe I should start a new thread but if it’s ok I would like to ask it here.
So me being new to this AMS wanted to maybe get the sequence of how I need to do things. So I have download a file from Makersworld and when I open in BS it adds the filaments in the filament list. These are numbered, is that the AMS slot? or just random number? When I loaded my custom filament (Poly HT PLA-GF) into the AMS the label in the AMS just shows PLA, kinda confusing since I have several types and they all just say PLA. In the filament list though it does list the correct name. Also, there are filaments (such as TPU-90) that are in the filament list that I don’t have loaded should those be removed from the list?
Great to hear you figured it out @truckeic , and kudos to your perseverance.
Would you mind pasting a screenshot of what it looks like currently (the one that has the nozzle size explicitly in it). Hopefully this helps others to understand what the goal is.
(still not allowed to add media in my posts myself)
I also fixed the issue by readding the preset. Didn’t have to delete anything first. I selected preset (1) below in the “copy preset from filament” menu during the process to keep existing settings. Then I renamed the one it generated (2) which created (3). BUT now I can’t delete (2) because it was “inherited” by (3). However, it allows me to delete (1).
I don’t know whether this is part of the process or a workaround on bug, opinions differ within this thread. It’s the only reliable way I found to get rid of pop up message. Feel free to keep us posted on your progress
*I’m a trusted member in the meanwhile so I’m allowed to add screenshots in my posts.
