Avisos
Vaciar todo

PrusaSlicer problems with XL 5 Toolhead  

  RSS
generic0000
(@generic0000)
Miembro
PrusaSlicer problems with XL 5 Toolhead

I'm having problems with PrusaSlicer and my new XL 5 head. If I change the colors of each extruder and save the printer settings, it saves it as "Original Prusa XL - 5T Input Shaper 0.4 nozzle - Copy" under "user presets" and changes all the filaments to "default". When I try to change the filament back to what it's supposed to be, the only option is "default". I have tried changing the profile dependencies for some of the system presets, with no luck. "All" is checked for compatible printers. I've tried selecting the "Original Prusa XL - 5T Input Shaper 0.4 nozzle - Copy" specifically. I've deleted the "compatible printers condition" argument. I've check the "show incompatible print and filament presets" setting. Even the filament profiles I've created don't show up. NOTHING will let me change the colors of the extruders, save, then select ANY filament other than "default". With the "copy" printer profile selected, if I click "add/remove filaments" it just opens the setup wizard, and will add the prusa SLA printer for some reason unless I make sure to disable that. I understand not being able to change the prusa profiles, but not being able to save your current filament configuration without prusaslicer crapping all over itself is pretty ridiculous.

 

 

EDIT: I'm using PrusaSlicer 2.8.0 by the way.

Best Answer by generic0000:

I found a workaround. Creating a user preset for the XL, creating a user preset for PLA, deleting ALL dependencies for PLA, selecting "All" for compatible printers, and selecting just the user preset for the XL under compatible printers; all of that has done nothing. The solution is to click "detach from system preset" in the filament dependencies tab. That makes the PLA profile show up under my copied XL profile. Apparently if a filament preset is inherited from a system preset you cannot use it with a non-system-preset printer profile, even if the printer profile is inherited from a system preset and has all the appropriate dependencies and keywords. There is no option to detach the printer profile, by the way. This definitely seems like a bug, otherwise the dependencies are meaningless for inherited profiles, since deleting them all did not actually remove them. Also, the copied and barely changed XL profile should have met the required dependencies regardless.

Posted by: @diem

The colours are property of the Filament presets.  Edit, then save a new preset copy as, eg, 'PLA red' and it will survive a restart.

Cheerio,

When I replied earlier I wasn't in front of a computer with prusaslicer on it. My original question was poorly worded. The issue is not changing the color assigned to the filament preset (PLA, PETG,...), it is changing the color assigned to each extruder in the printer profile. That's why I needed to save a copy of the XL profile, with the extruder colors changed. I still don't know why that broke all compatibilities, other than it being a bug.

Posted by: @baconfase

So PS is having issues reading config files and can't even run the built in config wizard correctly? Something fubar'd and its probably easier to figuratively turn it off and back on again.

I'd go clean slate restart: full uninstall/delete of PS, including all the saved profiles and folders in your %appdata% assuming Windows, reinstall PS, and reconfig from scratch. If you had custom profiles that you wanted to keep then make a backup beforehand and throw them back in afterwards.

I think these issues are bugs. I think there is a problem with how PS handles inherited profiles. Unfortunately, this means that my printer and filament profiles wont be updated by prusa. Now that I know the work around, it's not that hard to manually update the profiles, it's just not a seamless.

Respondido : 24/07/2024 4:31 pm
Diem
 Diem
(@diem)
Illustrious Member

The colours are property of the Filament presets.  Edit, then save a new preset copy as, eg, 'PLA red' and it will survive a restart.

Cheerio,

Respondido : 24/07/2024 10:40 pm
Acht me gusta
generic0000
(@generic0000)
Miembro
Topic starter answered:
RE: PrusaSlicer problems with XL 5 Toolhead

Thanks for the response. So you're saying I need to create a seperate filament preset for every color of every plastic type? 

That also doesn't change the fact that ALL the filament presets disappear when I save a modified version of the printer preset. That means if I ever change ANYTHING in the printer preset and try to save it, I will have to manually recreate all the filament presets. This is either a bug, or a really weird system that even removes my modified filament presets from the modified printer preset.

 

Also, clicking add more filament opens the setup wizzard, which adds the SL1 to prusaslicer if you don't go to the SLA tab and unselect it. That's probably a bug too.

Respondido : 24/07/2024 11:04 pm
BaconFase
(@baconfase)
Reputable Member
RE: PrusaSlicer problems with XL 5 Toolhead

So PS is having issues reading config files and can't even run the built in config wizard correctly? Something fubar'd and its probably easier to figuratively turn it off and back on again.

I'd go clean slate restart: full uninstall/delete of PS, including all the saved profiles and folders in your %appdata% assuming Windows, reinstall PS, and reconfig from scratch. If you had custom profiles that you wanted to keep then make a backup beforehand and throw them back in afterwards.

XL-5T, MK3S MMU3 || GUIDE: How to print with multiple-nozzlesizes do read updated replies || PrusaSlicer Fork with multi-nozzlesize freedom || How Feasible is Printing PETG for PLA supports on XL very

Respondido : 26/07/2024 7:45 am
generic0000
(@generic0000)
Miembro
Topic starter answered:
RE: PrusaSlicer problems with XL 5 Toolhead

I found a workaround. Creating a user preset for the XL, creating a user preset for PLA, deleting ALL dependencies for PLA, selecting "All" for compatible printers, and selecting just the user preset for the XL under compatible printers; all of that has done nothing. The solution is to click "detach from system preset" in the filament dependencies tab. That makes the PLA profile show up under my copied XL profile. Apparently if a filament preset is inherited from a system preset you cannot use it with a non-system-preset printer profile, even if the printer profile is inherited from a system preset and has all the appropriate dependencies and keywords. There is no option to detach the printer profile, by the way. This definitely seems like a bug, otherwise the dependencies are meaningless for inherited profiles, since deleting them all did not actually remove them. Also, the copied and barely changed XL profile should have met the required dependencies regardless.

Posted by: @diem

The colours are property of the Filament presets.  Edit, then save a new preset copy as, eg, 'PLA red' and it will survive a restart.

Cheerio,

When I replied earlier I wasn't in front of a computer with prusaslicer on it. My original question was poorly worded. The issue is not changing the color assigned to the filament preset (PLA, PETG,...), it is changing the color assigned to each extruder in the printer profile. That's why I needed to save a copy of the XL profile, with the extruder colors changed. I still don't know why that broke all compatibilities, other than it being a bug.

Posted by: @baconfase

So PS is having issues reading config files and can't even run the built in config wizard correctly? Something fubar'd and its probably easier to figuratively turn it off and back on again.

I'd go clean slate restart: full uninstall/delete of PS, including all the saved profiles and folders in your %appdata% assuming Windows, reinstall PS, and reconfig from scratch. If you had custom profiles that you wanted to keep then make a backup beforehand and throw them back in afterwards.

I think these issues are bugs. I think there is a problem with how PS handles inherited profiles. Unfortunately, this means that my printer and filament profiles wont be updated by prusa. Now that I know the work around, it's not that hard to manually update the profiles, it's just not a seamless.

Respondido : 26/07/2024 3:14 pm
Compartir: