Possible Speed Bug?
Mk3S, MMU2S (3.7.2 1.0.6)
Before the latest profiles updates (that said they were for the SL1) PrusaSlicer (v2.0.0, 201805201652) would give almost spot on time estimates for printing.
Well, after the profiles update, now it seems my times are not being listed properly. A print that said it would take 26 hours has taken more then 40. A print that said it should be an hour has taken 3+. No changes have been made. Does not matter if I use OctoPrint or sneakernet the SD card over to it.
One thing that sticks out as a possible cause is when I export my GCODE, the name of the GCODE contains PLA instead of PETG. (I have PLA loaded in MMU slot 1, PETG in Slot 2, these prints are only using PETG). The reason that stuck out was the max volumetric speed is different between the two, so I am wondering if PrusaSlicer is basing the time off of PLA instead of PETG.
Anyone else experience this or willing to replicate?
RE: Possible Speed Bug?
Not an MMU user. So my knowledge is limited.
I can see where mixing materials can cause issues ... I'm not even sure the slicer tracks which nozzle has which material. I'd guess the assumption is made that all material is the same, and whatever is in the default extruder gets timed. So printing with PETG will take longer that the predicted time if the default lists PLA (which is implied in the filename). But the problem I see is that you've selected PLA - so how does the slicer know what is actually in the buffer?
In any case, this seems more like a feature request. I'd suggest you post it over on GitHub and see what the developers say.
RE: Possible Speed Bug?
But the problem I see is that you've selected PLA - so how does the slicer know what is actually in the buffer?
What I meant by that was although slot 1 has PLA and slot 2 has PETG, I have my parts in PrusaSlicer marked to use the PETG in slot 2 (which it does)
I will make a report on GitHub tomorrow if no one else chimes in. It is an odd bug that popped up as soon as I got that profile update.