3D Printing News Digest - May 27, 2026
Published
Bambu X2D Day 31: OTA PETG result window final day — first resolution data publishing today; 11 post-plateau days. AGPLv3 Day 9: two violations unresolved; baltobu executing. Prusa INDX Day 5: 13mg vs. 500–800mg per transition. NEW: Prusa launches Open Community License to protect open-source hardware.
Bambu Lab X2D Day 31: OTA 01.01.01.00 PETG Result Window — FINAL Day (Day 4 of 4); First Empirical PETG Purge Resolution Data Expected Today; Eleven Days Post-Plateau; Hi Combo Day 14 Enters Week 3
The Bambu Lab X2D enters Day 31 (Wednesday May 27) — eleven consecutive days past THE Community Evaluation Plateau (Day 21, May 17). The OTA 01.01.01.00 PETG result window (Days 28–31) reaches its FINAL day today: the community data collection window is closing. First empirical PETG purge-tower resolution data — the primary test for whether OTA 01.01.01.00 solved the reported PLA/PETG prime tower instability — is expected to be published today as Day 29–31 users post results. Simultaneously: V01.01.00.65 Public Beta remains active as a parallel firmware track. Hi Combo Day 14 (Week 3 Day 1, Wednesday May 27): the Creality Hi Combo K2 Plus CFS enters its third week in retail hands with 14 consecutive days and zero CFS firmware updates. The X2D dual-track firmware asymmetry (OTA 01.01.01.00 + V01.01.00.65 beta vs. Hi Combo zero CFS updates) represents the widest single-point comparison gap in desktop multicolor printer evaluation history. X2D $649 vs. Hi Combo $599 — the $50 premium is decisively supported by the firmware investment evidence.
Day 31 PETG result window closing today is the most significant single-day firmware validation event in the X2D's post-launch history. If the Day 28–31 community posts confirm OTA 01.01.01.00 resolved the PLA/PETG prime tower instability, the X2D's first major OTA update will have closed its highest-visibility open question within 4 days of release. Hi Combo Day 14 with zero CFS firmware simultaneously creates the clearest evidence picture: X2D = active firmware investment at Day 31; Hi Combo = no CFS update through Week 3 Day 1.
💡What this means for you
Bambu X2D Day 31 (May 27, Wednesday): Eleven days past Day 21 Community Evaluation Plateau (May 17). OTA 01.01.01.00 PETG result window: Day 4 of 4 (Days 28–31 = May 24–27) — final day. V01.01.00.65 Public Beta: active parallel firmware track (may represent staging for next OTA or separate feature track). Primary PETG test: whether OTA 01.01.01.00 resolved prime tower instability during PLA/PETG mixed-material prints. First empirical data expected today from Monday–Wednesday users (Days 29–31). Hi Combo Day 14 (Week 3 Day 1): 14 consecutive days no CFS (Creality Filament System) firmware update. X2D dual-track (OTA + beta) vs. Hi Combo zero: widest single-point firmware asymmetry in evaluation history. X2D $649 vs. Hi Combo $599 ($50 premium).
Market Position: Day 31 with PETG result window closing today is the firmware-investment validation day for X2D buyers who prioritized PLA/PETG mixed-material capability as a primary use case. If OTA 01.01.01.00 results confirm PETG resolution, the X2D's first major post-launch update cycle will have been completed within 10 days of release — a meaningful benchmark vs. the Hi Combo's 14-day no-update baseline.
- Do the Day 28–31 community PETG results confirm OTA 01.01.01.00 resolved the prime tower instability for PLA/PETG mixed prints — and is the resolution consistent across multiple X2D users and PETG filament brands?
- Does the V01.01.00.65 Public Beta represent a staging version for the next OTA after 01.01.01.00 — or a parallel feature track addressing different firmware components independent of the PETG prime tower fix?
- Does the Hi Combo receive any CFS firmware update in Week 3 (Days 14–21, May 27–June 3) — or does the 14-day no-update baseline extend further, widening the X2D firmware investment asymmetry?
⏸️ Wait if: You want to see the Day 31 PETG result data before deciding between X2D and Hi Combo — results should be available today; if OTA confirms PETG resolution, the X2D case is validated; if results are inconclusive, Day 32–35 community data will extend the picture
✅ Buy if: You prioritize multi-material PLA/PETG performance and active firmware investment — X2D $649 with OTA 01.01.01.00 now in final PETG validation vs. Hi Combo $599 with 14 consecutive days zero CFS firmware; $50 premium is supported by firmware evidence
Bambu Lab AGPLv3 Day 9: Sustained Resolution Phase — Two SFC Violations Formally Unresolved; baltobu Reverse-Engineering and Fork Work Executing; OrcaSlicer Functional Through Day 9
The Bambu Lab AGPLv3 controversy enters Day 9 (Wednesday May 27). The resolution phase established on Day 8 continues: major outlet coverage (Tom's Hardware, Notebookcheck, 3D Printing Industry, Jeff Geerling, Slashdot) is stable with no significant new publications Day 9. Two SFC-confirmed violations remain formally unresolved: (1) libbambu_networking proprietary source code disclosure — Bambu has distributed this networking library without releasing source for years, breaching AGPLv3; (2) legal threats against developer Paweł Jarczak's OrcaSlicer fork (OrcaSlicer-bambulab) that restored cloud printing without Bambu Connect. Bambu Lab's backtrack statement does not address either violation directly. The baltobu project (SFC-organized, community-funded at $250,007+) has active funded staff work executing: libbambu_networking reverse engineering, OrcaSlicer fork maintenance, and Bambu Studio replacement fork development — a months-long program. OrcaSlicer remains fully functional for all hardware through Day 9.
Day 9 with two violations formally unresolved and baltobu executing is the moment where the AGPLv3 dispute transitions from media controversy to sustained enforcement and alternative-ecosystem development. The baltobu project at $250,007+ funded means the SFC has operational resources for months of reverse-engineering work — this is not a one-week controversy but a multi-month open-source enforcement effort. For Bambu hardware owners: OrcaSlicer functional through Day 9 means no workflow disruption; the baltobu forks will take months to reach feature parity.
💡What this means for you
Bambu Lab AGPLv3 Day 9 (May 27, Wednesday): Two SFC-confirmed violations: (1) libbambu_networking — AGPLv3 requires complete corresponding source for all distributed software; Bambu has not released libbambu_networking source. (2) Legal threats against Paweł Jarczak's OrcaSlicer fork (OrcaSlicer-bambulab) that re-enabled cloud printing without Bambu Connect — cease-and-desist + GitHub removal demand = restriction of Jarczak's legal AGPLv3 rights. Bambu backtrack statement: does not resolve either violation. baltobu project: $250,007+ funded; staff work executing on libbambu_networking reverse engineering, OrcaSlicer fork (Jarczak collaborating), and Bambu Studio replacement fork. Coverage: Tom's Hardware (two articles, Josef Prusa 'security risk' quote), Notebookcheck ('Bambu backtracks'), 3D Printing Industry ('Bambu Lab Now Under Formal Investigation'), Jeff Geerling ('abusing the open source social contract'), Slashdot. OrcaSlicer: functional through Day 9.
Market Position: Day 9 with two violations unresolved and baltobu executing represents the long-term governance phase of the AGPLv3 dispute. For Bambu hardware owners evaluating the ecosystem risk: OrcaSlicer functional through Day 9 means no immediate workflow impact; the baltobu forks are months-long development programs. For prospective Bambu buyers: the AGPLv3 controversy adds ecosystem lock-in risk to the Bambu purchase calculus, which Prusa's OCL (announced recently) directly addresses.
- Does Bambu Lab release any new official response after Day 8 — directly addressing the two SFC violations (libbambu_networking source and Jarczak legal threats) — or does the backtrack statement remain the company's last communication?
- Does the baltobu libbambu_networking reverse-engineering work produce any initial technical findings within the first 30–60 days — establishing a public baseline for what the library does and how to replace it?
- Does the Prusa Open Community License (OCL, announced this week) reference the Bambu AGPLv3 case explicitly — positioning Prusa's open-source hardware framework as a response to Bambu's licensing behavior?
⏸️ Wait if: You are considering a new Bambu Lab purchase and are concerned about the ecosystem lock-in implications of the AGPLv3 violations — Day 9 with two violations unresolved and baltobu executing adds a multi-month uncertainty period to the Bambu ecosystem investment calculus
✅ Buy if: You already own Bambu hardware and are evaluating workflow continuity — OrcaSlicer is fully functional through Day 9 with no hardware impact; Bambu Studio hardware unaffected; baltobu forks are months away from feature parity; current workflow has no disruption
Prusa CORE One INDX Day 5: Community 13mg vs. 500–800mg Cost-Per-Transition Analysis Forming on r/3Dprinting; Bondtech Founders Edition Day 5 Field Reports; Prusa Edition Ships June 2026
The Prusa CORE One INDX enters Day 5 (Wednesday May 27). Community cost-per-transition analysis is forming on r/3Dprinting with Day 4–5 Bondtech Founders Edition field reports contributing data: INDX = approximately 13mg per tool change; AMS 2 Pro = approximately 500–800mg per purge transition. The ~38–60× purge-waste reduction per transition is the defining technical differentiator for high-color-count professional workflows. 15-second per-toolhead calibration confirmed (Day 4 Bondtech field + Prusa spec). Full 8-head re-calibration: approximately 2 minutes. CORE One + INDX 4T total: approximately $1,998; CORE One + INDX 8T total: approximately $2,248 — vs. Bambu X2D + AMS 2 Pro at approximately $999 ($999–$1,249 INDX premium for near-zero-purge architecture). Prusa Edition upgrade kits ship June 2026. First batch INDX kits sold out; second batch timeline pending.
Day 5 with community cost-per-transition data forming is the analytical maturation point for the INDX vs. AMS debate. The 13mg vs. 500–800mg comparison is not a marginal improvement — it's a purge-waste architecture difference that scales directly with the number of tool changes in a production run. For professional users printing 50–100+ color transitions per build plate: the INDX's near-zero-purge advantage represents potentially 25–40g of filament saved per print vs. AMS, justifying the $999–$1,249 INDX premium in high-volume scenarios.
💡What this means for you
Prusa CORE One INDX Day 5 (May 27, Wednesday): Pricing: $749 (4T) / $999 (8T) tariffs included; €669/€899 EU VAT. First batch shipped (sold out); second batch timeline pending. Prusa Edition: June 2026. Bondtech Founders Edition: shipping (field reports Day 5). INDX per-tool-change waste: ~13mg. AMS 2 Pro per-purge-transition: ~500–800mg. 15-second per-toolhead calibration confirmed. Full 8-head re-cal: ~2 minutes. Toolhead offset calibration fixture: permanently mounted outside print area. CORE One + INDX 4T total: ~$1,998. CORE One + INDX 8T total: ~$2,248. X2D + AMS 2 Pro: ~$999 ($999–$1,249 INDX premium). August 2026 shipping for first INDX batch.
Market Position: Day 5 with community cost-per-transition data forming is the most important analytical week for INDX vs. AMS comparison buyers. The 13mg vs. 500–800mg purge difference — if confirmed consistently across Bondtech Founders Edition field data — establishes the INDX as the only near-zero-purge multi-material architecture in desktop 3D printing. The $999–$1,249 premium is justified by waste-filament savings in high-volume professional applications.
- Do Bondtech Founders Edition Day 5 field reports confirm the 13mg per tool change specification across a range of filament types — including PETG, TPU, and support materials — or is the 13mg figure PLA-specific?
- Does the community r/3Dprinting cost-per-transition analysis produce a break-even calculation — i.e., how many tool changes per month does a buyer need to justify the $999–$1,249 INDX premium vs. AMS at standard filament cost?
- Does Prusa communicate a timeline for the second INDX batch — and does the first batch sell-out pace suggest the second batch will ship before or after the August 2026 first-batch delivery window?
⏸️ Wait if: You print fewer than 20–30 color transitions per build plate in a typical workflow — at low transition counts, the 13mg vs. 500–800mg advantage shrinks in absolute terms; the $999–$1,249 INDX premium vs. AMS is harder to justify at low volumes
✅ Buy if: You run high-color-count professional multi-material builds (50+ transitions per print) and need near-zero purge waste — INDX 13mg per transition vs. AMS 500–800mg scales directly with volume; $749/$999 INDX kit pricing; first batch (sold out); Prusa Edition June 2026
NEW: Prusa Research Launches Open Community License (OCL) to Protect Open-Source 3D Printing Hardware from Commercial Exploitation
Prusa Research has introduced the Open Community License (OCL), a new licensing framework designed to allow designers to share open-source hardware while protecting it from commercial exploitation. The OCL permits users to freely use, modify, and share hardware designs — but restricts commercial entities from exploiting those designs without contributing back to the community. The announcement arrives in the direct context of the Bambu Lab AGPLv3 controversy (Day 9 today): the AGPLv3 dispute exposed how existing open-source licenses can be circumvented by well-resourced commercial actors. Prusa's OCL directly addresses this gap by adding commercial-protection provisions that standard GPL-family licenses lack. The OCL is designed for hardware (PCBs, mechanical assemblies, 3D-printable parts) where existing software-centric open-source licenses (GPL, LGPL, AGPL) provide incomplete protection. Josef Prusa's public statement characterized Bambu Lab's conduct as a 'security risk' to the open-source 3D printing ecosystem.
The Prusa OCL is the most significant open-source hardware licensing development in desktop 3D printing since the original Prusa MK series was released under GPL. Coming in the direct context of the Bambu AGPLv3 violations, the OCL represents a proactive governance framework: Prusa is not just criticizing Bambu's behavior but building the licensing infrastructure to prevent similar exploitation of Prusa-ecosystem designs. For the maker community: the OCL defines a new category of 'community-protected open source' hardware that is free to use but commercially locked from exploitation without reciprocal contribution.
💡What this means for you
Prusa Research OCL: permits free use, modification, and sharing of hardware designs (PCBs, mechanical assemblies, 3D-printable parts); restricts commercial exploitation without reciprocal community contribution. Designed for hardware where GPL-family software licenses provide incomplete protection. Josef Prusa statement: Bambu Lab's AGPLv3 violations and legal threats represent a 'security risk' to the open-source 3D printing ecosystem. OCL application: Prusa's own hardware designs (MK series, CORE One, INDX toolhead system) will be covered. Context: Bambu AGPLv3 violations confirmed by SFC on May 18 — two violations formally unresolved through Day 9.
Market Position: The OCL positions Prusa as the governance leader in open-source desktop 3D printing — not just producing open hardware but defining the licensing framework to protect it. For the Bambu vs. Prusa ecosystem comparison: Bambu has AGPLv3 violations under SFC enforcement; Prusa is introducing new IP governance tools. The OCL adds a new dimension to the ecosystem choice for buyers who value open-source hardware principles.
- Does the OCL have legal enforceability against large commercial actors in key jurisdictions (US, EU, China) — or does it rely primarily on community pressure and reputational enforcement?
- Does Prusa apply the OCL retroactively to existing hardware designs — or only to new designs released after the OCL's introduction?
- Do other open-source 3D printer manufacturers (Creality, Bambu, etc.) respond to the OCL with their own licensing frameworks — or does the OCL create a Prusa-specific governance differentiation?
⏸️ Wait if: You want to evaluate the OCL's legal enforceability before making an ecosystem decision based on open-source hardware principles — the OCL is new and untested in commercial disputes
✅ Buy if: You prioritize open-source hardware governance and want the 3D printer ecosystem with the strongest demonstrated commitment to open-source principles — Prusa's OCL plus the INDX open toolhead system vs. Bambu's two AGPLv3 violations positions Prusa as the clear open-source choice
Frequently Asked Questions
What does the Bambu X2D OTA PETG result window closing today (Day 31) mean for buyers comparing the X2D vs. Hi Combo?▼
The Day 28–31 window is the community's 4-day period to test and publish results from OTA 01.01.01.00 — specifically whether it fixed PLA/PETG prime tower instability. If today's posts confirm resolution, the X2D's first major OTA cycle completed its primary test in 10 days. Hi Combo at Day 14 with zero CFS firmware updates is the comparison baseline. Watch r/3Dprinting and Bambu Lab Community Forum today for the first consolidated PETG results.
The Bambu Lab AGPLv3 controversy is on Day 9 — do I need to worry about my existing Bambu hardware or OrcaSlicer workflow?▼
No immediate workflow disruption. OrcaSlicer is fully functional through Day 9. Bambu hardware is unaffected by the software licensing dispute. The two unresolved violations (libbambu_networking source disclosure + Jarczak legal threats) are governance issues — not user-experience issues today. The baltobu forks are months-long development programs. Current Bambu hardware owners: no action required today. Prospective buyers: the violations add ecosystem lock-in risk to consider alongside the AGPLv3 governance picture.
What is the Prusa INDX 13mg vs. 500–800mg per transition comparison, and why does it matter?▼
INDX uses physical tool-swapping (one toolhead replaces another) with ~13mg of ooze per swap. AMS uses filament purging (the active nozzle extrudes old filament before loading new) with ~500–800mg per purge. For a build plate with 50 color transitions: INDX wastes ~0.65g total; AMS wastes ~25–40g total. The INDX advantage scales with transition count. At standard PLA ($20–25/kg), the waste difference is $0.05–$0.50 vs. $0.50–$1.00+ per build plate — meaningful in high-volume production.
What is the Prusa Open Community License (OCL) and how does it differ from GPL/AGPL?▼
OCL is a hardware-specific open-source license that permits free use, modification, and sharing of mechanical and electronic designs — but restricts commercial exploitation without reciprocal community contribution. Standard GPL/AGPL licenses were written for software and provide incomplete protection for hardware designs (PCBs, mechanical assemblies). OCL fills this gap, directly addressing the type of commercial exploitation that the Bambu AGPLv3 situation demonstrated. Announced by Prusa Research in direct response to the broader open-source licensing environment.