PrusaSlicer VS OctoPrint-MeatPack

I do this with my Prusa MK3S with MMU2S. It cannot be done without this fix in PrusaSlicer, however (which hasn't been merged into a release).

If you’d like to support my request https://github.com/prusa3d/PrusaSlicer/issues/11102 and leave a comment or a 👍. Any support is welcome and helps to get this feature implemented in PrusaSlicer. Thank you in advance!

That's it. I haven't seen many mentions of global variables other than This GitHub page from March so I hope this helps people.

Example: "The feature was ported from BambuStudio, thanks to @bambulab for the initial implementation." https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.0-beta4

It may be worth filing a feature request issue for your use case with the PrusaSlicer project.

There is an issue with PrusaSlicer that needs to be fixed to make it work for true multi-material printing. At this time, the nozzle can jam when switching from a high temperature to a lower temperature filament, because the purge is attempted at the lower temperature, which can cause the nozzle to jam. I fixed it in this PR (so that purging happens at the higher of the two temperatures) but it never got merged into the current release, and given the PR backlog, I doubt it ever will. In any case, that fix converts the MMU into a true multi-material printer. I can now print PLA with PETG supports, for example. Or mix PLA with PLA+. I have to use my own PrusaSlicer build to do this, however.

Hi, I have a project based on https://github.com/prusa3d/PrusaSlicer/tree/master that I want to create a .app for to try on another laptop. however i just can't figure out how. it seems like xcode build will do that for you, however upon using cmake with -GXcode it does create a project and I can debug/run my app with it. but there is no .app within the file structure.

I thought of meatpack and chuckled

Further improvements can be made with MeatPack, if one is game to goof with printer firmware.

I designed and implemented a g-code compression algorithm which nearly doubles serial throughput for OctoPrint, reducing stuttering.

In the readme.md of the github project:

The software engineer in me is always looking for optimization opportunities so I spent some time staring at the G-code. I think I've found a couple ways to compress about 3% more without firmware changes (although have not tested it). Not sure if you saw it but left an issue in your repo describing it: https://github.com/scottmudge/OctoPrint-MeatPack/issues/13

Besides, there is absolutely no reason to overclock the 4B SoC for OctoPrint. The quality bottleneck is the Einsy board's serial port. I've been working on a project to help improve that though: https://github.com/scottmudge/OctoPrint-MeatPack . But OctoPrint is only going to use ~5-15% of the 4B's computational resources, even at its standard clock rate. Even with a webcam attached.