supermerill / SuperSlicer

G-code generator for 3D printers (Prusa, Voron, Creality, etc.)
4.1k stars 519 forks source link

[Feature request]Add PETG to filament type list #4198

Closed Nesquirt closed 5 months ago

Nesquirt commented 6 months ago

It would be nice to add PETG in filament list instead PET, or adding over PET. It would fix the spoolman plugin advice "The material of the selected filament does not match the selected material in the slicer. Are you sure you want to continue?". I tried after slicing the stl, to manually change from PET to PETG in gcode and the advice disappear Thanks in advice mate

sboehle commented 6 months ago

Hmm, isn't it possible to enter it manually? image

When you don't use the dropdown, but click in the field and enter "PETG" - will this be removed or corrected in any way?

Nesquirt commented 6 months ago

Hmm, isn't it possible to enter it manually?

image

When you don't use the dropdown, but click in the field and enter "PETG" - will this be removed or corrected in any way?

Uhm i dont think it keep the value stored in gcode,ill give a try this evening!

anonymousaga commented 5 months ago

The value isnt stored. When you type in a custom value, it doesnt let you save and it reverts back to the old choice.

anonymousaga commented 5 months ago

Something that does seem to work is going into the filament's .ini file and editing it to a custom value. For macOS the ini files are at ~/Library/Application Support/SuperSlicer/filament/

And now spool man no longer has an issue:

image
AlejandroRivera commented 5 months ago

I can confirm that changing manually the value to PETG doesn't seem to be correctly stored, as the GCODE generated still shows "PET" instead of "PETG". This becomes a problem when using something like Spoolman to manage spools, which tries to match the filament_type with the inventory of filaments in it's database.

anonymousaga commented 5 months ago

I can confirm that changing manually the value to PETG doesn't seem to be correctly stored, as the GCODE generated still shows "PET" instead of "PETG". This becomes a problem when using something like Spoolman to manage spools, which tries to match the filament_type with the inventory of filaments in it's database.

Try editing the ini files directly. For me editing the ini files directly worked.

sboehle commented 5 months ago

Very strange. I tried it again with the latest sc version. I entered "abcdef". It was saved in the filament preset and the generated gcode contained "abcdef" as filament_type.

image

image

Nesquirt commented 5 months ago

I can confirm that changing manually the value to PETG doesn't seem to be correctly stored, as the GCODE generated still shows "PET" instead of "PETG". This becomes a problem when using something like Spoolman to manage spools, which tries to match the filament_type with the inventory of filaments in it's database.

Try editing the ini files directly. For me editing the ini files directly worked.

FIXED WITH THIS COMMENT

AlejandroRivera commented 4 months ago

I can confirm that changing manually the value to PETG doesn't seem to be correctly stored, as the GCODE generated still shows "PET" instead of "PETG". This becomes a problem when using something like Spoolman to manage spools, which tries to match the filament_type with the inventory of filaments in it's database.

Try editing the ini files directly. For me editing the ini files directly worked.

Yes, i had done this, but every time i saved something in the filament section, the PETG type was replaced with PET :/

anonymousaga commented 4 months ago

@AlejandroRivera This doesnt happen to me. As long as i leave the filament type untouched I can modify the rest of the profile and save and nothing happens to that field.