New release: 1.3.3
Rollout temporarily halted while I’m following up on some reports I got about a (rare?) issue with this release.
After three release candidates I’m happy to finally present you OctoPrint 1.3.3. This a true maintenance release again, consisting of various improvements and fixes.
Some highlights from the release notes:
- The webcam stream now (finally ;)) has a fixed height in landscape/unrotated mode as well, meaning no more jumping controls when it loads! The aspect ratio is selectable between 16:9 (the default) and 4:3 via a new setting. And the rotated view is now properly centered. Additionally a little notice informs you about whether the stream is still loading or if loading failed (and if so, what to do about that).
- A new delete confirmation for the timelapses prevents you from accidents, and in order to still allow you quick and easy clean-up when you actually DO want to delete stuff, a new bulk delete option allows you to remove a lot of timelapse related clutter all at once.
- It’s happened a couple of times in the past that plugin authors approached me because there was something up with their plugin that required some manual action from their users - e.g. a misconfigured automatic update or things like a popular plugin looking for a new maintainer. So far the @OctoPrint3D twitter feed was the only option to reach some of you that were affected by this. Not any more - the plugin manager now also fetches plugin specific notices from the plugin repository and will display them to you if you have the relevant plugin installed (optionally limited to specific versions). Note that not every plugin author can freely send such notices - they’ll need to do a pull request against the plugin repository for this, so you shouldn’t have to worry about drowning in notices :)
- And of course there is a long list of bugs that got fixed too, from simple typos over issues with the gcode analysis to race conditions that have been driving me crazy for months now. Good riddance :)
Since Github experienced a major service outage earlier today, a small heads-up that will hopefully resolve itself over the course of today (May 31st, 2017) - to quote the Changelog:
Current Github hiccups might impede updating for a bit (May 31st, 2017)
This might resolve itself within the next couple of hours: Github currently still appears to suffer from some hiccups (they had an outage earlier today, May 31st 2017). That might cause your update to take longer than usual or maybe even not run properly at all - the update mechanism is based on Github’s releases API & repositories being available. So: if you happen to run into any issues during updating, please just wait a couple more hours. I sadly have no influence there at all and can just hope that those issues will be resolved soon.
There is also a note for those of you who run a Malyan M200 or Monoprice Select Mini printer, to quote the Changelog:
Note for owners of Malyan M200/Monoprice Select Mini
OctoPrint’s firmware autodetection is now able to detect this printer. Currently when this printer is detected, the following firmware specific features will be enabled automatically:
- Always assume SD card is present (
- Send a checksum with the command: Always (
Since the firmware is a very special kind of beast and its sources are so far unavailable, only tests with a real printer will show if those are sufficient settings for communication with this printer to fully function correctly. Thus, if you run into any issues with enabled firmware autodetection on this printer model, please add a comment in #1762 and explain what kind of communication problem you are seeing. Also make sure to include a
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. Thanks!
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 are running 1.2.7, get an “Update Now” button but the update is immediately reported to be successful without any changes, read this.
If you are running 1.2.16, get an “Update Now” button but the update is immediately producing an error message, read this.
- Changelog and Release Notes
- Contribution Guidelines (also relevant for creating bug reports!)
- How to file a bug report
- How to roll back to an earlier release (OctoPi)
- How to roll back to an earlier release (manual install)
- 31 May 2017