New release: 1.3.11

#1

After three months of development and another two of testing by the community, I’m happy to finally present you OctoPrint 1.3.11. This a maintenance release again, consisting of various improvements and fixes.

It was made possible only through your continued support of my work 💕.

Once again the changelog is on the lengthy side as this release packs a ton of improvements and bug fixes which would be too many to list here. Instead I’ll just present you with a short excerpt:

  • The CuraEngine plugin so far bundled with OctoPrint was unbundled and lives on as the CuraEngine Legacy plugin that’s available on the plugin repository. On board slicing was never a primary focus of OctoPrint and the bundled plugin relied on a very dated CuraEngine version, so it was about time to clean up a bit.

    If you happen to be one of the very small number of people who rely on the CuraEngine plugin for your workflow, make sure to install the CuraEngine Legacy plugin from the repository. Once installed the CuraEngine Legacy plugin will import the settings and profiles from the former bundled Cura plugin automatically on first start.

  • The GCODE viewer will again show the total number of printer layers (I know quite a number of you missed that 😉).
  • Active print events (start/stop/cancel) now get logged, incl. who caused them. This will allow to audit who did what on shared installations.
  • Further hardening against various misconfigurations or misbehaving third party plugins or content.
  • New plugin hooks: octoprint.printer.sdcardupload to allow plugins to override the default SD card upload behaviour and octoprint.events.register_custom_events to allow plugins to cleanly add custom events to the system.
  • The list of GCODE commands on which OctoPrint will pause the print and/or which to suppress is now user configurable via the settings.
  • Performance improvements and more aggressive metadata cleanup in the internal file manager.
  • Support for firmware reporting print chamber temperatures.
  • Notifications will no longer be able to expand past the viewport size and hence should no longer become “uncloseable”.
  • … and various further improvements and of course bug fixes.

The full list of changes can of course be found in the Changelog - as always.

Also see the Further Information and Links below for more information, where to find help and how to roll back.

I also want to thank everyone who contributed to this release, @agrif, @akraus53, @AndyQ, @CapnBry, @DanielJoyce, @devildant, @Fabi0San, @fake-name, @fieldOfView, @gloomyandy, @HarlemSquirrel, @hgross, @jubaleth, @melgish, @rgriebl and @tedder for their PRs.

And last but not least, another special Thank you! to everyone who reported back on the release candidates this time: @arhi, @b-morgan, @CRCinAU, @devildant, @evanquinnalaska, @FormerLurker, @gege2b, @isbric, @JohnOCFII, @kazibole, @nionio6915, @reloxx13, @schnello, @trunzoc, @vfrdirk & @zeroflow.

If you are interested in some numbers, according to the anonymous usage tracking 1.3.11rc1 saw 9540 hours of successful prints on 523 unique instances, 1.3.11rc2 saw 9311h hours of successful prints on 553 unique instances, and 1.3.11rc3 saw a whopping 39578 hours (or 4.5 years) of successful prints on 964 unique instances.

Further Information

It may take up to 24h for your update notification to pop up, so don’t be alarmed if it doesn’t show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.

If you get an error about “no suitable distribution” during update, please read this.

If you have any problems with your OctoPrint installation, please seek support on the community forum.

Links


This is a companion discussion topic for the original entry at https://octoprint.org/blog/2019/05/14/new-release-1.3.11/
6 Likes
Cura OctoPrint Connection plugin
#2
  • Create a backup of working config.yaml after successful startup.

@foosel For the sake of support here, can you describe the filename and location of this backup? (Thanks).

#3

config.backup right next to config.yaml, so usually ~/.octoprint/config.backup

1 Like
#4

Might want to look for any traces of slicing-related references...

39%20AM

Cura problems - wiki
Cura - wiki

#5

You can still slice your STL files directly within OctoPrint. You just need to install a slicer plugin.