{"id":585,"date":"2023-12-04T00:22:19","date_gmt":"2023-12-03T23:22:19","guid":{"rendered":"https:\/\/simplyprint.io\/blog\/?p=585"},"modified":"2023-12-04T01:06:46","modified_gmt":"2023-12-04T00:06:46","slug":"post-december-maintenance-whats-new","status":"publish","type":"post","link":"https:\/\/simplyprint.io\/blog\/post-december-maintenance-whats-new\/","title":{"rendered":"Post-December-maintenance: what's new?"},"content":{"rendered":"\n<p>Hey there SimplyPrint'ers - it's time for another update from the SimplyPrint team!<\/p>\n\n\n\n<p>A <strong>lot <\/strong>has happened since our last update in October, and after the completed <strong>Dec. 2. maintenance<\/strong>, resulting in some downtime <em>(a little more than we had hoped for!)<\/em>, we're here to detail why this update - though it may not seem so at first glance - is a <em>big<\/em> deal!<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>!! <em><strong>Note: we're still ironing out some general issues in the platform. We're aware that some are experiencing some connection issues.<\/strong> <strong>Please reach out via our live-chat if you're experiencing bugs or issues after this update - we're eager to fix them!<\/strong><\/em><br>We apologize for the inconvenience of the maintenance downtime, and any issues that have followed. We're hard at work making sure everything runs smoothly.<\/p>\n<\/blockquote>\n\n\n\n<p>To keep this blog post from morphing into a full-blown encyclopedia entry, we've trimmed the details. For the full saga, peek at the changelog at the end. Now, to highlight a few of the cool new, smaller, but cooler changes that don't get their own section <em>(let's call them \"Honorable mentions\")<\/em>;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Auto-tagging:<\/strong> on newly-uploaded files, we can now - for files sliced in most slicers, automatically apply <strong>material<\/strong> and <strong>nozzle size<\/strong> tags to your files, as well as <strong>colors <\/strong>for multi-color prints!<\/li>\n\n\n\n<li><strong>Gcode Analysis update: more info<\/strong>. We now know the <strong>total layers<\/strong> and <strong>layer height<\/strong> of your files among more new details!<\/li>\n\n\n\n<li>We <strong>moved the print queue to its own page<\/strong><\/li>\n\n\n\n<li><strong>Temperature margin settings<\/strong> added<\/li>\n\n\n\n<li>\"1-click print\" &amp; AutoPrint update<\/li>\n\n\n\n<li>3 new queue match criteria<\/li>\n<\/ul>\n\n\n\n<div style=\"height:17px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>What we'll talk about in this update<\/h2><nav><ul><li class=\"\"><a href=\"#getting-the-file-system-ready-for-whats-to-come-bambu-lab-integration\">Getting the file system ready for what's to come (Bambu Lab integration)<\/a><\/li><li class=\"\"><a href=\"#what-was-the-maintenance-all-about-new-platform-base-performance-optimization-more\">What was the maintenance all about? New platform base, performance optimization &amp; more<\/a><ul><li class=\"\"><a href=\"#so-what-did-this-update-do\">So, what did this update do?<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#bambu-lab-direct-prusa-integration-update\">Bambu Lab &amp; Direct Prusa integration update<\/a><ul><li class=\"\"><a href=\"#bambu-lab-integration-status\">Bambu Lab integration status<\/a><\/li><li class=\"\"><a href=\"#direct-prusa-integration-status\">Direct Prusa integration status<\/a><\/li><\/ul><\/li><li class=\"\"><a href=\"#changelog\">Changelog<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n<div style=\"height:37px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"getting-the-file-system-ready-for-whats-to-come-bambu-lab-integration\">Getting the file system ready for what's to come <em>(Bambu Lab integration)<\/em><\/h2>\n\n\n\n<p>Let's first start with the updates we have made to the file system in SimplyPrint.<\/p>\n\n\n\n<p>In this update, we have <strong>changed how SimplyPrint thinks of a file<\/strong>.<\/p>\n\n\n\n<p>Before, we split files in to 2 categories;<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Printable files<\/strong> <em>(.gcode, .gco, .nc, .npg)<\/em><\/li>\n\n\n\n<li><strong>3D model files<\/strong> <em>(.stl, .3mf, .obj)<\/em><\/li>\n<\/ol>\n\n\n\n<p>And that's all that we supported just a couple of weeks ago. But putting files in boxes based on their file type \/ extension, just didn't work anymore; as we wanted an integration for <strong>Bambu Lab<\/strong> - whose printers use the <strong>.3mf<\/strong> file format as printable files - even though it's a 3D model file type - we had to <strong>change the foundation<\/strong> of our file system, to not be so \"black and white\".<\/p>\n\n\n\n<p><em>\"But how hard can it be to add new file formats to the accepted list of 3D-printable files?\"<\/em>, one might ask. And it's a fair question!<br>The answer; somewhat hard, but very time-consuming if you want to do it right.<\/p>\n\n\n\n<p>A backbone of the SimplyPrint platform since day 1, has been our in-depth <strong>Gcode Analysis<\/strong>. It's a feature that - although often overlooked - we're very proud of, and that helps make sure you start the right prints on the right printers. It's at the center of our recent automation updates, and just got more powerful in this update! <em>(more on that further down the post)<\/em>.<br>And as SimplyPrint wants to analyze your Gcode file before you print it - to both alert you in case something's wrong, and to know more about the job <em>(such as filament usage)<\/em>, adding support for the Bambu Lab 3MF files posed a challenge... Either we needed to simply say; <em>\"No Gcode Analysis for Bambu Lab prints\"<\/em> - and take a lot of the SimplyPrint features away from Bambu users - or go all-in. And we went <strong>all-in<\/strong>.<\/p>\n\n\n\n<p>And to make matters worse; SimplyPrint officially supports over <strong>420 different 3D printers<\/strong>, and not all of these can print the same file types; certainly most wouldn't know what to do if we asked it to 3D print a 3MF file...<\/p>\n\n\n\n<p>So, to make a long story short; <strong>we now fully support 3D-printable 3MF files<\/strong>, as well as the new Prusa Gcode format; <strong>.bgcode<\/strong>! Both these files, although not directly readable by our analysis, are now unpacked &amp; decoded, the Gcode file\/content <em>(which still exists, in the almost-usual format, inside both files)<\/em>, are analyzed when uploading the file!<\/p>\n\n\n\n<p>Furthermore, when uploading a 3MF file that include multiple Gcode files <em>(in BambuStudio and OrcaSlicer it's called \"plates\")<\/em>, we allow you to extract each plate into one separate file when uploading it to the SimplyPrint system, or simply select which of the plates you want to print!<\/p>\n\n\n\n<p>This is a huge step in the right direction for SimplyPrint integrations with printers that aren't natively supported by our platform, due to no \"serial printing\" capabilities!<\/p>\n\n\n\n<div style=\"height:37px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"what-was-the-maintenance-all-about-new-platform-base-performance-optimization-more\">What was the maintenance all about? New platform base, performance optimization &amp; more<\/h2>\n\n\n\n<p>On Dec. 2., we had our big, long-advertised server maintenance, which required the SimplyPrint servers to be completely unavailable - which is not something we have had to do before.<\/p>\n\n\n\n<p>Having downtime is a last resort, and like any cloud service, our goal is to minimize it. Prior to this maintenance, our uptime-stats were great! 99.99% over the past 90 days <em>(can always be tracked on our <a href=\"https:\/\/status.simplyprint.io\/\">status page<\/a>)<\/em>, but, the whole reason we had to take the servers offline for a while; <strong>it wouldn't have been that way for long.<\/strong><\/p>\n\n\n\n<p>SimplyPrint is growing. And fast. Faster than our systems could really handle. Our servers were starting to struggle - months ago, even.<\/p>\n\n\n\n<p>So, over the past 5 months, we have dedicated most of our development resources towards a major update of our platform. We turned the whole thing upside down, and - to get technical - started over on our backend &amp; system architecture implementation.<\/p>\n\n\n\n<p>This meant doing pretty much everything we have already done, again... Cause the truth is; it wouldn't have been long before we couldn't just throw money at more powerful servers to meet the increasing demand - our foundation had to change, so we wouldn't have to <em>(and it wouldn't really have been sustainable for a small startup, either!)<\/em>.<\/p>\n\n\n\n<p>But we did it, and - although the launch was a bit rocky, <strong>this huge update is now live!<\/strong> After a couple more hours of downtime than planned for, a dozen more issues than hoped for - and some still ongoing that we're still ironing out.<\/p>\n\n\n\n<div style=\"height:14px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"so-what-did-this-update-do\">So, what did this update do?<\/h3>\n\n\n\n<p>As mentioned, it fixes a bunch of underlying issues our old system and code had. Now, our platform can handle <em>a lot<\/em> more, and is - to put it in \"human\" terms; <strong>healthier<\/strong>.<\/p>\n\n\n\n<p>This <strong>allows us to focus our energy on developing cool features, faster<\/strong>, as the development experience for our team has increased tremendously, and the rate at which we can develop <em>good, solid<\/em> and <em>awesome<\/em> features and additions, have improved drastically.<\/p>\n\n\n\n<p><strong>Speed<\/strong> is also on the menu in this update. We have been able to see load &amp; speed increases of up to <strong>15.39 times faster than before!<\/strong> As you'll see in the graph beblow, the performance-increase is quite substantial, and while most don't mind waiting a few extra milliseconds <em>(or, in the worst cases; seconds)<\/em>, this is a great sign of health from the platform - it's now in much better shape than before!<\/p>\n\n\n\n<p>And while you as a user may not spot the difference day-to-day just yet, the impact this update will have on the future of SimplyPrint is the real gift of this update.<\/p>\n\n\n\n<div style=\"height:14px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"693\" height=\"429\" src=\"https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/Initial-page-load-time-before-vs-after-update.png\" alt=\"\" class=\"wp-image-607\" style=\"width:693px;height:auto\" srcset=\"https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/Initial-page-load-time-before-vs-after-update.png 693w, https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/Initial-page-load-time-before-vs-after-update-300x186.png 300w\" sizes=\"(max-width: 693px) 100vw, 693px\" \/><figcaption class=\"wp-element-caption\"><em>Difference in platform loading speed before (<mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">blue<\/mark>), and after (<mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">red<\/mark>), this new update.<\/em><br><em>The smaller the pillar, the better!<\/em><\/figcaption><\/figure><\/div>\n\n\n<div style=\"height:37px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"bambu-lab-direct-prusa-integration-update\">Bambu Lab &amp; Direct Prusa integration update<\/h2>\n\n\n\n<p>You all deserve an update on where we stand with the Bambu Lab and Direct Prusa integrations. We have been more silent on the development progress than we would've liked, so, here's the latest news;<\/p>\n\n\n\n<div style=\"height:17px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"bambu-lab-integration-status\">Bambu Lab integration status<\/h3>\n\n\n\n<p>The Bambu Lab integration is <strong>almost finished<\/strong>. As detailed in the <em>\"Getting the file system ready for what's to come\"<\/em> section of the blog, a big part of this integration didn't necessarily have to do with the direct integration with the Bambu machine, but moreso supporting all things around it; its files, understanding its slicer, proper AMS \/ multicolor support and \"Start print options\".<\/p>\n\n\n\n<p>To cut to the chase; the first round of Bambu Lab Integration <strong>Beta invites<\/strong> will be sent out <strong>early december<\/strong> - hopefully within max 2 weeks!<\/p>\n\n\n\n<p>We start by inviting those who have waited the longest <em>(those who signed up first)<\/em>, but we'll ramp it up very quickly and let everyone in after a very short beta round; we want everyone to be able to enjoy this integration, and take their Bambu Lab printers to the next level!<\/p>\n\n\n\n<div style=\"height:8px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"direct-prusa-integration-status\">Direct Prusa integration status<\/h3>\n\n\n\n<p>This integration has been marked \"Coming soon\" for a while - and we haven't even opened for beta signups yet! So, what's new with this?<\/p>\n\n\n\n<p>The Direct Prusa integration is meant to allow you to connect your Prusa MK4, XL, MK3.5, MK3.9 and Prusa Mini printers <strong>directly <\/strong>to SimplyPrint, <strong>without needing a Raspberry Pi<\/strong>.<\/p>\n\n\n\n<p>This is possible as the new mainboards that the Prusa printers ship with are more powerful than before, and now have access to the internet.<\/p>\n\n\n\n<p>But, as you - unlike with Bambu Lab printers - are still able to use a Raspberry Pi for SimplyPrint with the Prusa MK4 and XL printers, getting this update out to the general userbase has not been a big priority for us. With that said, we do have a ~95% working integration, that is currently running on about 50 MK4 printers all around Denmark, and we do believe we'll be ready to release this to everyone soon as well.<\/p>\n\n\n\n<p>But, there's one thing about this that we had hoped to avoid, but that we simply can't get around; it will require <strong>custom firmware.<\/strong><\/p>\n\n\n\n<p>This is not what we hoped for initially, but we simply cannot get around it. This means, if you want to save the Pi, you'll have to install our custom firmware.<\/p>\n\n\n\n<p>This firmware will be 99.9% the stock Prusa firmware; we don't change a lot, but we have to make it connect to our servers instead theirs.<\/p>\n\n\n\n<p>The issue with this is, that you <strong>break the warranty<\/strong> of your printer if you flash non-official firmware, and you have to <em>physically<\/em> break a \"safety pin\" inside Prusa.<\/p>\n\n\n\n<p>This means, that when we release this, we're asking people to break the warranty of their printers, and physically break a part their mainboard off... That's a lot of pressure, and it has to be done <strong>right<\/strong>. This is why we're taking our time with this one, gathering feedback and not pulling the trigger too fast - especially while the Prusa firmware team are making <em>a lot<\/em> of fundamental changes to their firmware, which may mean we have to start somewhat over with the integration soon...<\/p>\n\n\n\n<p>So, while we're not ready to say exactly when this would be out yet, we <em>are<\/em> making progress, and now that this new update has been launched, we're closer to being able to dedicate more time to getting this integration launched.<\/p>\n\n\n\n<div style=\"height:42px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>As usual, we'll close this update off with a comprehensive list of changes that we have released over the past couple of weeks - most of them released Dec. 2.<\/p>\n\n\n\n<div style=\"height:14px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"changelog\">Changelog<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Queue match criteria upgrade<\/strong>\n<ul class=\"wp-block-list\">\n<li>Added 3 new queue match criteria settings;\n<ul class=\"wp-block-list\">\n<li>Match nozzle size<\/li>\n\n\n\n<li>Match material color<\/li>\n\n\n\n<li>Match material type<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>These were all under the umbrella of \"Match tags\" before, but now they have their own settings<\/li>\n\n\n\n<li>We also updated the documentation for queue item matching (<a href=\"https:\/\/help.simplyprint.io\/en\/article\/auto-matching-queue-items-to-printers-xdn526\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/help.simplyprint.io\/en\/article\/auto-matching-queue-items-to-printers-xdn526\/<\/a>) and added hoverable help-tooltips to all criteria<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Added 2 new filament &amp; material type settings; temperature margins<\/strong>\n<ul class=\"wp-block-list\">\n<li>When matching a material to a printer, SimplyPrint used to allow for a 10\u00b0 degree C. margin <em>(so if the print should be printed with 210\u00b0 on the nozzle, but printer-assigned filament had its nozzle temperature set to 205, 220 or 200, we'd still match it)<\/em><\/li>\n\n\n\n<li>There are now 2 account-wide settings for temperature margins; one for nozzle and one for bed<\/li>\n\n\n\n<li>The same 2 settings can be found per material type in your <a href=\"https:\/\/simplyprint.io\/panel\/settings\/filament\">filament settings<\/a><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>1-click print UI update<\/strong>\n<ul class=\"wp-block-list\">\n<li>In the 1-click print UI, we have now made it easier to see why an item, or no items, are matched with a printer<\/li>\n\n\n\n<li>A blue warning box will now show if no queue items are matched with a printer, if there are simply no more queue items <em>(queue has \"run out\")<\/em><\/li>\n\n\n\n<li>On no matches, you can now click to learn more, and see exactly what matching criteria was not met<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>AutoPrint \"Troubleshooting &amp; debugging\" section<\/strong>\n<ul class=\"wp-block-list\">\n<li>In the AutoPrint widget on the control panel of a printer, in the bottom you'll now see a section called \"Troubleshooting &amp; debugging\" - if AutoPrint is enabled<\/li>\n\n\n\n<li>This section shows all the details about the state of AutoPrint, which print it wants to start next, as well as any possible reason it may have for <em>not<\/em> starting a print<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Panel performance &amp; loading speed optimized<\/strong><\/li>\n\n\n\n<li><strong>Bugfixes &amp; general improvements, that were now possible with this update<\/strong>\n<ul class=\"wp-block-list\">\n<li>\ud83d\udc1b <strong>Sorting<\/strong> for printers, print queue &amp; more; this has been a bit... buggy, for a while - but all the things behind this update allowed to finally squish this bug!<\/li>\n\n\n\n<li>\ud83d\udc1b On import of file from file system to slicer, the file could end up just being called \"SimplySliced.gcode\" once sliced; this has been fixed<\/li>\n\n\n\n<li>\ud83d\udc1b Fixed issue where saving file via the slicer might fail<\/li>\n\n\n\n<li>\ud83d\udc1b Fixed issue when toggling from dark- to light-mode, some UI keeping their dark-mode properties<\/li>\n\n\n\n<li>\ud83d\udc1b Fixed bug where we did not reconnect you to the printer server if you briefly lost internet connection<\/li>\n\n\n\n<li>\ud83d\udc1b Fixed files \"Printer select\" not showing after being saved <em>(thanks to community member @johnsdiy for pointing this out!)<\/em>\n<ul class=\"wp-block-list\">\n<li>The selected printers of a file now get selected automatically when you click the \"Print file\" button<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>In the <a href=\"https:\/\/simplyprint.io\/blog\/farm-overview-gcode-macros-rework\/\" target=\"_blank\" rel=\"noreferrer noopener\">print farm overview cards<\/a> we now show a \"paused\" icon for \"Next printer finish\" if the printer is paused<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Moved Print Queue to its own sidebar item \/ page<\/strong>\n<ul class=\"wp-block-list\">\n<li>The print queue is now located at <a href=\"http:\/\/simplyprint.io\/panel\/queue\">simplyprint.io\/panel\/queue<\/a>, and the queue buttons on the printer page have been removed in favor of this<\/li>\n\n\n\n<li>This move was made to allow the queue to have more space to expand, as we add more features to it, along with the placement of it on the \"Printers\" page being an issue when using permissions to allow a user to see the print queue, but not the \"Printers\" page...<\/li>\n\n\n\n<li>We know this change may take some getting used to - don't hesitate to provide your feedback!<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Moved the \"1-click-print\" button to the left side of the \"Printers\" page<\/strong>\n<ul class=\"wp-block-list\">\n<li>1-click-print has become a very popular and powerful feature - but feedback shows that many newer users overlooked it, in the button-bundle on the right side of the printer's panel - now it has more space to shine!<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Moved \"Your files\" page file \"Start print\" &amp; \"action\"-buttons further up<\/strong>\n<ul class=\"wp-block-list\">\n<li>In the sidebar <em>(on PC)<\/em> or popup <em>(mobile)<\/em> that shows when you click on a file on the \"Your files\" page, the \"Start print\" or \"Slice &amp; print\", \"Add to queue\" and delete, download, move &amp; rename buttons, have now been moved above the file-preview box, to avoid them being pushed down so you'd have to scroll to reach them<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Gcode analysis \/ file info<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>New info that we now gather on all Gcode files uploaded to SimplyPrint;<\/strong>\n<ul class=\"wp-block-list\">\n<li>Layer height <em>(and first layer height, if it differs)<\/em><\/li>\n\n\n\n<li>Total layers<\/li>\n\n\n\n<li>Slicer version<\/li>\n\n\n\n<li>Nozzle size sliced for<\/li>\n\n\n\n<li>Filament details; color, type, density<\/li>\n\n\n\n<li>Gcode flavor sliced for <em>(gathered, not yet used)<\/em><\/li>\n\n\n\n<li>Printer model sliced for <em>(<em>gathered, not yet used<\/em>)<\/em><\/li>\n\n\n\n<li><em>This is best-supported for the SimplyPrint slicer, PrusaSlicer, SuperSlicer &amp; BambuStudio, as other slicers such as Cura don't embed a lot of information in the Gcode file for us to use<\/em><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Added support for reading tool &amp; bed temperatures from the Klipper macro \"START_PRINT\" in Gcode files<\/li>\n\n\n\n<li>We now start gathering print information only once the first layer begins, to avoid alerting you about start lines, \"purge poop\" etc.<\/li>\n\n\n\n<li>Fixed the analysis for filament usage not working well for multi-extruder prints<\/li>\n\n\n\n<li>For PrusaSlicer, we now use the filament usage estimate that is included in the Gcode file, rather than relying on our own analysis, as PrusaSlicer knows more when the print is being sliced, allowing it to produce a more precise estimate<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Auto-tag applying on files;<\/strong>\n<ul class=\"wp-block-list\">\n<li>Possible because of the Gcode analysis update, where we now gather the nozzle size and filament details<\/li>\n\n\n\n<li><strong>Nozzle<\/strong> <strong>size tag is automatically applied<\/strong><\/li>\n\n\n\n<li><strong>Material type tag is automatically applied<\/strong><\/li>\n\n\n\n<li><strong>Material <span style=\"text-decoration: underline;\">color<\/span> tag is applied <em>if<\/em> <\/strong>the print is sliced for multiple colors<\/li>\n\n\n\n<li>Works for multi-extruder\/color prints too!<\/li>\n\n\n\n<li><em>This too is best-supported for the SimplyPrint slicer, PrusaSlicer, SuperSlicer &amp; BambuStudio<\/em><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Support for the new Prusa \".bgcode\" file format <em>(binary Gcode)<\/em><\/strong>\n<ul class=\"wp-block-list\">\n<li>About a month ago, Prusa announced, and released an alpha version of their firmware supporting, their new \".bgcode\" file format, promising - and delivering - greatly minimized file sizes<\/li>\n\n\n\n<li>SimplyPrint now accepts this filetype, decodes it and finds the Gcode content inside and analyzes it - so it'll essentially act like any Gcode file in your system, but only printable on printers that support this format, which is currently just MK4 and XL printers from Prusa<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Improved the way we think about files...<\/strong>\n<ul class=\"wp-block-list\">\n<li>Added support for <strong>.3mf files being printable in certain cases<\/strong><\/li>\n\n\n\n<li>Added \"3MF-splitting\" support; allowing us to extract each \"plate\" as its own file<\/li>\n\n\n\n<li>Added <strong>Prusa .bgcode file support<\/strong><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>The platform now loads even if we can't connect you to the Printer API server<\/strong>\n<ul class=\"wp-block-list\">\n<li>For a while, if you tried to load the \"Printers\" page while unable to connect to the printer API server for real-time communication with your printer(s), the page simply did not load<\/li>\n\n\n\n<li>Now, the whole panel - except for printer-action-specific things, such as starting prints - will work even without this<\/li>\n\n\n\n<li>We load the last known state of all your printers<\/li>\n\n\n\n<li>This is only relevant when unable to connect to our printer server, which can happen if;\n<ul class=\"wp-block-list\">\n<li>Your firewall blocks it<\/li>\n\n\n\n<li>We're applying an update or have scheduled downtime on just the Printer API server, but not the rest of the panel<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Hey there SimplyPrint'ers - it's time for another update from the SimplyPrint team! A lot has happened since our last update in October, and after the completed Dec. 2. maintenance, resulting in some downtime (a little more than we had hoped for!), we're here to detail why this update - though it may not seem [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":609,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","footnotes":""},"categories":[7],"tags":[26,17,25],"class_list":["post-585","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-changelog","tag-bambu","tag-changelog","tag-maintenance"],"rankmath_description":"","category_names":["Changelog"],"uagb_featured_image_src":{"full":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update.jpg",1024,1024,false],"thumbnail":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update-150x150.jpg",150,150,true],"medium":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update-300x300.jpg",300,300,true],"medium_large":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update-768x768.jpg",768,768,true],"large":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update.jpg",1024,1024,false],"1536x1536":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update.jpg",1024,1024,false],"2048x2048":["https:\/\/simplyprint.io\/blog\/wp-content\/uploads\/2023\/12\/sp-december-post-maintenance-update.jpg",1024,1024,false]},"uagb_author_info":{"display_name":"Albert M\u00f8ller Nielsen","author_link":"https:\/\/simplyprint.io\/blog\/author\/albert\/"},"uagb_comment_info":0,"uagb_excerpt":"Hey there SimplyPrint'ers - it's time for another update from the SimplyPrint team! A lot has happened since our last update in October, and after the completed Dec. 2. maintenance, resulting in some downtime (a little more than we had hoped for!), we're here to detail why this update - though it may not seem&hellip;","_links":{"self":[{"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/posts\/585"}],"collection":[{"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/comments?post=585"}],"version-history":[{"count":58,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/posts\/585\/revisions"}],"predecessor-version":[{"id":648,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/posts\/585\/revisions\/648"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/media\/609"}],"wp:attachment":[{"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/media?parent=585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/categories?post=585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/simplyprint.io\/blog\/wp-json\/wp\/v2\/tags?post=585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}