Can't create a new filament

[tlhintoq]

OrcaSlicer Version

1.8 and newer through 1.9 dev 231222

OS version

Windows10x64

Additional system information

No response

Printer

Any

How to reproduce

1. From main screen
2. Filament - settings gear icon
3. Try to create a new custom filament

Actual results

You can't select from the drop down as it is disabled.
There's no way to select an existing material or printer.
You get an error popup that you have not yet selected a printer or material.

Expected results

I should be able to make/add TPU as a material

Project file & Debug log uploads

No crash. No project required. Happens at any point

Checklist of files to include

• Log file
• Project file

[tlhintoq]

Oh - also, the create new filament dialog pops up on the primary monitor instead of the monitor where the program is.

[tlhintoq]

Still an issue on 1.9.0 beta

[tlhintoq]

Keep alive - Still an issue in 1.9.0 release.

[tlhintoq]

Keep alive - Still an issue in 2.0 developer/nightly

[robert-stevenson-1]

I've also experienced the same issue.
(Interested in fix, hence trying to get some engagement here)

[Senayna]

Same here. Tried to add some ABS+ by eSUN for my Raise3D Pro3 Plus. Not able to, for the same reason as stated above.

[tlhintoq]

Hey bot, please don't close me - this is still an issue.

[huntervaneck]

I have the same issue. on 1.9 and 2.0. Unable to add any custom filament profiles.

[66mkiqdv]

Same for me too (both v1.9.1 & v2.0.0).

Hardware Information:

• Hardware Model: ASUS All Series
• Memory: 8.0 GiB
• Processor: Intel® Core™ i5-4670K × 4
• Graphics: AMD Radeon™ RX 570 Series
• Disk Capacity: 1.9 TB

Software Information:

• Firmware Version: 1402
• OS Name: openSUSE Tumbleweed
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 45.3
• Windowing System: Wayland
• Kernel Version: Linux 6.7.7-1-default

[imagesurgery]

Same or similar issue where I cannot add a custom filament to Orcaslicer 1.9.1 on macOS Sonoma 14.3 (installed via home-brew):
https://github.com/SoftFever/OrcaSlicer/assets/4323784/a8cf24e8-1f3a-4f3d-a118-b98d42d8df7c

Seems to be the same with any combination of system or user presets, for any printer; only way to proceed is to select the wrong filament type in the dropdown, but I cannot figure out how to change this afterwards to the correct filament.

[samv]

I'm just trying to select ASA for my printer. I was able to add it for "Voron" but not "Sovol SV06 Plus".

What's going on there? Is it something to do with the recommended bed temperature of ASA being 110°C, and the stock SV06+ not supporting that, so someone has decided that it "can't print ASA"? The TH3D Unified firmware adds support for 110°C bed temperature (i.e., not even a hardware mod!) it takes a while but just makes it eventually, and I haven't noticed it affect the bed magnetism.

If I set my printer to a Voron profile, it will happily let me pick the ASA filament:

But if I go back to the SV06+, it switches to another one (this one happens to be the last filament I printed with):

It seems like there are some training wheels on here that I'd just like to take off. I don't need to exclude filaments that don't have a pre–ordained printer profile or whatever. I've had successful prints with it!

If the right answer here is that people like me should ideally be making Pull Requests to add the filament type to the printer, so that the collective library of known good filament/printer combinations gets updated with the stock firmware. Perhaps this could even be an in–app system, to share and rate profiles and settings so that we can all figure things out collectively!

[tlhintoq]

Keep alive. Problem still exists in current 2.0 nightly as of 15apr2024

[Philomorph]

I don't know if it's helpful to say "me too" but I run into this whenever I try to add a new filament for my AD5M. I end up having to select a "system" filament with the Flashforge name and then just edit it and rename on save.

[samv]

FWIW, I found a work around for this. I can edit a profile for a filament type it thinks I can print, such as ABS, and then edit it. In that view, I can enter whatever I like,

Maybe one day I'll have a machine that can do filaments like that. Until then, I can only dream, using this filament entry dialog.

[Madin5]

Same problem. Can't add TPU profile.

[TheIncgi]

Found another workaround based on this reddit post
My selected printer was Elegoo Neptune 4 Max, I temporary switched over to a generic klipper printer and was able to create a TPU preset after that.

To get it to show up under my existing printer preset:
I went into AppData\Roaming\OrcaSlicer\user\default\filament\base to tweak the json for the new profile a bit
I edited these:

• compatible_printers
• filament_settings_id
• name

I used another preset I already had in as reference for the compatible_printers
I also renamed the files to match. (.info and .json)

[tlhintoq]

Bot nudge.

[WillingSpy]

The current workaround is to create it as a PLA/ PETG.

It seems only some filament types don't have the printer option for some reason.

using 2.0.0

[dockrbyter]

Same problem here with 2.0.0.... Will this be fixed in the upcoming version? 🤔

[tlhintoq]

Here's what happens for me in 2.1.0-beta

Try to make a new material.

Click Create New on the next dialog

The next popup jumps location way over to another monitor and half off the screen

It offers to make a material based on an existing material for an existing machine.

Then I'm stuck because I have to make up a serial number for a material. Huh? "BlahBlah black PETG" has to have its own serial number? Anyway, no way to enter this, so stuck.

So I canceled and started over. Again and again started over. Thinking I could fill out the box in reverse order or something before it flew off the screen, just so long as I could click [done] when done.

But in the end changing just about anything like the maker, or material type makes the dialog fly off.
Then there is the whole inheritance lineage to mess with. Seems a new material is going to inherit from something different for every machine. PETG-Generic on one Generic-PETG on another My PETG... Standard PETG.

All of these materials at some point... at some point there had to be a top level material that didn't inherit from others, right? Something had to be first. So if I'm making a NEW material, can't it be a top level material that doesn't inherit from anyone? Can't my new material be genuinely new?

[dcchillin46]

Just dropping by to say that as of 6/4 in 2.1 nightly build im still having this issue. I can edit an existing profile and save it but thats a bit of a hassle.

[dockrbyter]

Why isn't here any reaction from @SoftFever? It's not that this topic is just few hours old 🤷🙎

[RayzenOri]

OrcaSlicer 2.1 can't add filament because the program doesn't display any printer.

[obertini78]

I can confirm the same issue as with 2.1.0

[MuteKnee3D]

My current solution to this problem (Orca 2.1.1):
Choose an existing filament (i.e. "generic PLA")
Edit the filament by choosing the little pencil and paper icon next to the filament.
Change the color and then click the "save" (floppy disk) icon.
Name the filament anything you like (i.e. SUNLU Transparent 0.4mm)
Run your calibrations and edit your new filament profile accordingly.
With all of it's features and active development Orca is my favorite slicer but it has some missing functions that seem like they would be easy to fix. Makes the software feel unfinished. Hopefully the devs can work on the boring stuff to make this software feel more mature.

[pkysela]

I found a work around, open OrcaSlicer 1.9.1, add your new custom filament, open OrcaSlicer 2.1.1 and hey presto it's in the list ready for fine tuning. (works on Windows)
I assume OrcaSlicer stores its data is user's AppData? It would be good to know, in case I need to switch computers in the future.

[MuteKnee3D]

@pkysela

I found a work around, open OrcaSlicer 1.9.1, add your new custom filament, open OrcaSlicer 2.1.1 and hey presto it's in the list ready for fine tuning. (works on Windows) I assume OrcaSlicer stores its data is user's AppData? It would be good to know, in case I need to switch computers in the future.

Yes
C:\Users"yourname"\AppData\Roaming\OrcaSlicer\user\default
3 folders = filament, machine, process

[lousassole]

This continues to be an issue, and has been an issue since the beginnings of Orcaslicer (at least on every machine I've had it on).

It seems the same (or a closely related) issue presents itself when attempting to import filament profiles. Orcaslicer will deny you the ability to import them half the time for no apparent reason (reading through the JSON doesn't help either). Then if you manually jam them in, Orcaslicer will tell you they aren't compatible with the current printer even if they were created on a printer with the exact same name, or a parent printer. The whole filament/printer/process tree is a great idea, but needs a complete rework as in it's current state it is at best moderately functional and at worst impedes use and consistent tuning.

[NeWFieKaNaTa]

Same issue here. Posting for more attention.

[jotape26]

Found a workaround that worked for me on Mac:

• I've created a custom profile using a printer that I can select under "Copy Current Filament Preset", in my case I used Sovol SV06 0.4 Nozzle.
• This created a .info and a .json file under /Users/<user name>/Library/Application Support/OrcaSlicer/
• Rename both files. Don't know if this affects anything but I renamed both files to use Voolt3D PLA Velvet @Creality K1 (0.4 nozzle)
• On the .json file, I've added the compatible_printer that I use: Creality K1 (0.4 Nozzle) [I've added the parenthesis as well in case it needs to match the name of the printer preset]
• Restart Orca and verify that it worked.

Is not an elegant solution and it doesn't even copy the Manufacturer's preset but at least it something you can expand upon.

[AlejoMSP]

so, is this issue being looked after?
I'm ready to jump back into CURA if this si not resolved, seems pretty easy fix

[tlhintoq]

so, is this issue being looked after? I'm ready to jump back into CURA if this si not resolved, seems pretty easy fix
After all this time - I assume its not.

### Not worth the lobotomy of going back to Cura.

• Pick an existing filament.
• Make changes you want
• Save as new filament

Not awesome but gets the job done

[dbloemhard]

So many people having this issue and for so long... But not a peep from the developers. Doesnt make you feel confident that this software will get fixes for other issues.

[dockrbyter]

It seems to be a wide spreaded problem...
#3947 for example. And there are more.

[tlhintoq]

Its has been... and you're right about confidence.
I suspect a lot of the silence comes from the fact that Orca is a branch from another program. I suspect that the source of the problem is in the parent program Orca inherits from. And thus rewriting much of that inherited problem meaning opening a BIG can of worms and ongoing maintenance.
But if that's the case then Orca development just needs to be transparant about that. Respond to all the threads & tickets with honesty. Just say:

The material handling and management comes from Prusa slicer base code that we inherit and as such we're not going to try to re-write that entire subsystem as it is beyond what we have the developmental resources for at present.
or something like that.

[dbloemhard]

I tried the workaround suggested (manually adding my filament by copying another one) and it was one of the worst tpu prints I've done. Obviously missed a few important settings and I'm not experienced enough to know which ones they are (UI seems to hide basic stuff like retraction and print speed or I am too dumb to find it). I just installed Cura Slicer and it has good profiles for that and all other filaments out of the box. Problem solved!

…

On Wed, 21 Aug 2024, 07:49 SgtSaint, ***@***.***> wrote: Its has been... and you're right about confidence. I *suspect* a lot of the silence comes from the fact that Orca is a branch from another program. I *suspect* that the source of the problem is in the parent program Orca inherits from. And thus rewriting much of that inherited problem meaning opening a BIG can of worms and ongoing maintenance. But if that's the case then Orca development just needs to be transparant about that. Respond to all the threads & tickets with honesty. Just say: The material handling and management comes from Prusa slicer base code that we inherit and as such we're not going to try to re-write that entire subsystem as it is beyond what we have the developmental resources for at present. or something like that. — Reply to this email directly, view it on GitHub <#3242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJNVQE6GAAX7IOG4DOYP2E3ZSPBYJAVCNFSM6AAAAABBAIHNJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJZHA4TAMBZGA> . You are receiving this because you commented.Message ID: ***@***.***>

[timnolte]

so, is this issue being looked after? I'm ready to jump back into CURA if this si not resolved, seems pretty easy fix
After all this time - I assume its not.

### Not worth the lobotomy of going back to Cura.

• Pick an existing filament.
• Make changes you want
• Save as new filament

Not awesome but gets the job done

Yeah, this is essentially what I've ended up doing. Which works fine for the most part but these are just custom user presets tied to a specific base filament profile and it doesn't show that I have any custom filaments in Orca. 🤷‍♂️

[samv]

To be honest, the whole system of filament profile management in Orca Slicer needs an overhaul. What's asinine to me, even without this bug, is that:

1. my workaround above does not work when you move to multiple printers; these "forked" filaments created by saving a filament with a changed material field are basically "second class filaments" that cannot be easily used by other printers
2. when coping a filament profile from one printer or nozzle to another, it requires that there be an existing profile of the same type on the destination printer. IME there might be some settings which are custom to the printer, but honestly, the print settings for filament are mostly a property of the filament, and any adjustments for each printer's nozzle like flow or thermistor for temperatures are likely to be systematic, at least at a first pass. It should at least copy across the commonly listed filament properties like the recommended temperature range.

To solve this, for a start each property in the filament properties dialog could show where it is being inherited/set from. When creating a new preset for a filament, it could allow copying all the properties from the source printer, and if there are profiles for similar materials on the destination printer, the properties could be compared and merged. In fact if there are many filaments on the target printer of the correct type, it could even provide some kind of statistics: eg: "temperature ranges for ABS on this printer: 230 - 280" / "for other ABS of the same manufacturer: 230 - 260." then "temperature range on source printer: 230 - 260". "Use 230 - 260?"

I want to see, instead of rejections that there is no profile for that type of filament yet, warnings like "No PPS-CF filaments defined on this printer yet. Create a new profile from scratch?"

[lyr0x]

MacOS 14.6.1 same problem with Orca Slicer 2.1.1. Filament created with Klipper can't be used for other printers. Please rework the filament section