rongith

I don't find a way to change the status of a print from success to failed. Then I supposed it is not implemented. And I'm not sure that the 3rd...

Octodash is working on a fresh new install for me. Hardware: - RPI4 - RPI official 7" touchscreeen What I've done: - Octopi copy octopi 1.0.0 image with the Raspberry...

Check there: https://github.com/emorybarlow/pygcode

@jschuh, I'm interested in your PR. I'm trying to find ways to improve corner overhang that curls up. The main issue is that too much cooling stress the corners and...

Just to say @wavexx is not the only person that find it an issue. The more people have different printers, the more there will be demandings on that. Tooks me...

Templates are a very welcomed feature. :-) Just few things: - The way we activate templates is not so obvious. We have to got through the configuration wizard first. -...

You would need to provide some CAD files from a Filametrix. Then I may see how difficult your request is.

I suppose the tip for inserting a global variable {chamber_temp} in filament "Start G-code" doesn't work for the same reason filament "Start G-code" is invoked after printer "Start G-code". Then...

Chamber temperature is now available beginning with the 2.8 release. It solves the issue for me but not for the OP who wants more custom variables like "Filament Color".

@shkup, you can define your own parameters beginning from https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.9.3-beta1 See section "Custom G-code Parameters" for help. @yonitjio, I think you can close this issue too like the https://github.com/prusa3d/PrusaSlicer/issues/11550