3D Printing News Digest - May 29, 2026
Published
X2D Day 33: PETG data now one day old and stable — community results on record; buyers have empirical answers; Hi Combo Day 16 zero CFS. AGPLv3 Day 11: violations unresolved; baltobu executing; SFC committee June. Prusa INDX Day 7: 13mg/transition three-source confirmed stable; Prusa Edition ships June; first batch sold out. OCL Day 3: Tom's Hardware coverage live; developer counter-license published; OSHWA endorsement pending.
Bambu Lab X2D Day 33 — 13 Post-Plateau Days; PETG Community Results Now Stable; Hi Combo Day 16 (Week 3 Day 3, Friday): 16 Consecutive Days Zero CFS Firmware
The Bambu Lab X2D enters Day 33 (Friday May 29) — 13 days past the Community Evaluation Plateau (Day 21, May 17). The OTA 01.01.01.00 PETG result window CLOSED on Day 31 (May 27). As of today, the community PETG results are published and one day old — stable and available for review on r/3Dprinting and BambuLab forums. Buyers who wanted empirical PETG purge-tower resolution data before purchasing now have a settled record to review. V01.01.00.65 Public Beta remains active as a parallel firmware track. Creality Hi Combo Day 16 (Week 3 Day 3, Friday May 29): 16 consecutive days without any CFS (Creality Filament System) firmware update. The X2D dual-track firmware asymmetry vs. Hi Combo's zero-update baseline is now the widest documented in desktop multicolor comparison history. X2D $649 vs. Hi Combo $599 ($50 premium). Today's key context: the PETG data is one day old and stable — any buyer who reviewed it yesterday has their empirical answer; anyone who hasn't yet reviewed it can now do so with a settled community record.
Day 33 Friday is the first day where the PETG community results are no longer 'new' — they are stable and indexed. Buyers who have been waiting for empirical PETG resolution data now have no analytical reason to delay: the r/3Dprinting and BambuLab forum posts are searchable, the community has had 48+ hours to react, and the results record is settled. Hi Combo Day 16 with zero CFS firmware simultaneously means the X2D/Hi Combo comparison asymmetry is definitive at 16-day depth — two active firmware tracks vs. zero updates across 16 days is not a close comparison.
💡What this means for you
Bambu X2D Day 33 (May 29, Friday): 13 days past Day 21 Community Evaluation Plateau. OTA 01.01.01.00 PETG result window: CLOSED Day 31 (May 27). Community PETG results: published Day 31–32; now one day old and stable as of Day 33. Review location: r/3Dprinting search 'OTA 01.01.01.00 PETG results' + BambuLab official forum. V01.01.00.65 Public Beta: active parallel firmware track — two simultaneous improvement vectors remain in place. Hi Combo Day 16 (Week 3 Day 3): 16 consecutive days zero CFS firmware update. X2D $649 vs. Hi Combo $599 ($50 premium). Dual-track firmware architecture: OTA post-window results stable + beta active = complete firmware evaluation picture for the X2D launch window.
Market Position: Day 33 is the settled-data day for the X2D PETG evaluation — not the day results dropped (Day 31–32), but the first day results are stable, indexed, and reviewed. The buyer decision framework is now complete: PETG results are on record; 16-day Hi Combo firmware asymmetry is definitive; the $50 X2D premium is supported by 33 days of documented dual-track firmware investment. Buyers evaluating PLA/PETG multi-material reliability have all the empirical data they need to decide today.
- Do the settled Day 31–32 PETG community results on r/3Dprinting confirm OTA 01.01.01.00 resolved prime tower instability across diverse PETG brands — or do results show partial resolution, suggesting V01.01.00.65 Public Beta is the intended full fix?
- Does Bambu release V01.01.00.65 Public Beta as a stable OTA in the next 7–14 days, completing the dual-track firmware convergence and signaling the end of the X2D launch-window improvement phase?
- Does the Hi Combo receive any CFS firmware update in the next 7 days (Days 17–23) — breaking the 16-day zero-update baseline — or does Creality's silence continue past the three-week mark?
⏸️ Wait if: You have not yet reviewed the Day 31–32 PETG community results — spend 20–30 minutes searching r/3Dprinting and BambuLab forums for 'OTA 01.01.01.00 PETG' before deciding; the empirical data is now settled and searchable
✅ Buy if: You need PLA/PETG multi-material reliability with confirmed firmware support: X2D $649 with OTA 01.01.01.00 PETG results now stable + V01.01.00.65 beta active vs. Hi Combo $599 with 16 consecutive zero-CFS days; $50 premium backed by 33 days of documented firmware investment
Bambu Lab AGPLv3 Day 11 — Stable Resolution Phase; Two SFC Violations Formally Unresolved; baltobu Executing; SFC Standing Committee June 2026; OrcaSlicer Functional
The Bambu Lab AGPLv3 dispute enters Day 11 (Friday May 29) — stable resolution phase. No new major outlet coverage in Days 10–11; the story has entered its sustained-awareness phase with violations documented, baltobu funded, and SFC committee details pending for June. Two SFC-confirmed violations remain formally unresolved: (1) libbambu_networking — Bambu distributes this proprietary networking library without source code disclosure, in breach of AGPLv3's corresponding-source requirement; (2) cease-and-desist against Paweł Jarczak — violates AGPLv3§10¶3 prohibition on imposing further restrictions on license rights. Bambu's public backtrack statement does not address either violation per SFC. baltobu: $250,007+ raised; funded staff executing libbambu_networking reverse engineering + OrcaSlicer fork + Bambu Studio replacement fork. OrcaSlicer remains functional through Day 11. Hardware (X2D, A1 Mini, P1S, X1C) unaffected. SFC standing committee: details expected June 2026.
Day 11 stable resolution phase means the AGPLv3 dispute has passed through the high-velocity news phase and is now a sustained background factor in the Bambu ecosystem story. The two unresolved violations and the funded baltobu reverse-engineering program represent long-duration open questions — not resolved, not escalating, but not going away. For buyers: hardware is unaffected and OrcaSlicer is functional, but the software-ecosystem uncertainty from two formal SFC violations and a funded reverse-engineering project is the relevant background for any multi-year Bambu ecosystem investment decision.
💡What this means for you
Bambu Lab AGPLv3 Day 11 (May 29, Friday): Violations: (1) libbambu_networking — proprietary networking library distributed without source code; runtime download makes it invisible in published Bambu Studio source tree; AGPLv3 corresponding-source requirement breach. (2) Cease-and-desist against Paweł Jarczak (OrcaSlicer fork restoring cloud printing without Bambu Connect): AGPLv3§10¶3 violation — prohibition on imposing further restrictions on license rights. Bambu backtrack: public statement issued Day 3–4; does not address either violation directly per SFC confirmation. No new major outlet coverage Days 10–11: Tom's Hardware, Notebookcheck, 3D Printing Industry, Jeff Geerling, Slashdot stable; story in sustained-awareness phase. baltobu: $250,007+ raised; funded staff executing libbambu reverse engineering + OrcaSlicer fork + Bambu Studio replacement. OrcaSlicer: functional through Day 11. Hardware: X2D, A1 Mini, P1S, X1C — unaffected. SFC standing committee: details expected June 2026.
Market Position: Day 11 stable phase with two formal violations and $250,007+ in baltobu funding represents the AGPLv3 dispute's long-duration baseline. The high-velocity news phase (Days 1–7) is complete; the sustained documentation and enforcement phase has begun. For buyers: the key June milestone is the SFC standing committee announcement — that is the next event that could materially change the dispute's trajectory. Until then, the status is: violations documented, funding executing, hardware unaffected.
- Does Bambu Lab issue a revised statement between Days 11–30 that specifically addresses libbambu_networking source disclosure and the Jarczak C&D withdrawal — resolving at least one of the two formally unresolved SFC violations before the June committee announcement?
- Does the baltobu fundraiser continue growing beyond $250,007 through Week 3 — or does funding plateau, potentially limiting the scope of the reverse-engineering and fork development program?
- Does the SFC standing committee announcement in June produce a formal enforcement timeline with specific Bambu compliance milestones — or does the June announcement focus on community standards without a Bambu-specific compliance deadline?
⏸️ Wait if: You are evaluating a large Bambu ecosystem investment (multiple printers, Bambu Studio-dependent workflow, cloud features as primary value) — two unresolved SFC violations and the baltobu reverse-engineering program represent open ecosystem uncertainty; wait for June SFC committee details before committing
✅ Buy if: You need X2D hardware for multi-material 3D printing with active firmware support — hardware is unaffected through Day 11; OrcaSlicer functional; the AGPLv3 dispute is a software-ecosystem background factor, not a print-quality or hardware-reliability factor for day-to-day use
Prusa CORE One INDX Day 7 — Bondtech Founders Edition Day 7 Extended Field Reports; 13mg/Transition Three-Source Confirmation Stable; Community Comparison Framework Definitive; Prusa Edition Ships June
The Prusa CORE One INDX enters Day 7 (Friday May 29). Bondtech Founders Edition Day 7 extended-use reports continue accumulating on r/3Dprinting and maker forums. 13mg per toolhead change remains confirmed and stable across three independent sources: Prusa official spec + Bondtech Founders Edition field reports + r/3Dprinting community verification. This three-source confirmation has been stable since Day 5–6 and is now the settled figure for the INDX evaluation. Community cost-per-transition framework is definitive: INDX ~13mg per tool change vs. AMS 2 Pro ~500–800mg purge per transition. On a 500-transition print: INDX wastes ~6.5g total; AMS wastes ~250–400g. CORE One + INDX 4T ~$1,998; 8T ~$2,248. vs. X2D + AMS 2 Pro ~$999 ($999–$1,249 premium for near-zero-purge architecture). 15-second per-toolhead calibration confirmed across all Bondtech field reports. Prusa Edition kits: shipping starts June 2026; first batch sold out. Second batch timeline not yet confirmed.
Day 7 with the 13mg/transition figure stable across three sources and the community cost framework settled is the INDX's mature early-evaluation state: the fundamental data questions are answered. For buyers deciding between X2D + AMS 2 Pro ($999) and CORE One + INDX 4T (~$1,998): the $999 premium buys near-zero purge waste (13mg vs. 500–800mg), open-ecosystem hardware (no AGPLv3 dispute), and a toolhead system with confirmed 15-second calibration. The remaining open question is supply — Prusa Edition first batch sold out, Bondtech Founders Edition available now for immediate access.
💡What this means for you
Prusa CORE One INDX Day 7 (May 29, Friday): 13mg per toolhead change: stable and settled across three independent sources — (1) Prusa official spec; (2) Bondtech Founders Edition Day 5–7 field reports; (3) r/3Dprinting community verification posts. vs. Bambu AMS 2 Pro: ~500–800mg purge per filament transition (purge tower). 15-second per-toolhead calibration: confirmed across all Bondtech field reports; full 8-head recalibration ~2 minutes. Cost-per-transition comparison: INDX ~13mg = ~$0.00026 per transition at $0.02/g PLA; AMS 2 Pro ~500–800mg = ~$0.01–0.016 per transition — 38–62× more waste per transition. CORE One + INDX 4T: ~$1,998 US. CORE One + INDX 8T: ~$2,248 US. X2D + AMS 2 Pro: ~$999 US ($999–$1,249 INDX premium). Prusa Edition kits: June 2026 shipping; first batch sold out. Bondtech Founders Edition: available now.
Market Position: Day 7 stable three-source 13mg/transition confirmation positions the INDX as the definitively proven near-zero-purge system in desktop multi-material 3D printing. No competitive system — AMS 2 Pro, Bambu multicolor, or equivalent — approaches 13mg per transition. The $999–$1,249 premium vs. X2D + AMS 2 Pro is now fully framed against a settled waste figure. The only remaining supply constraint is Prusa Edition availability — Bondtech path is open for immediate access.
- Do the Bondtech Founders Edition Day 7–14 extended-use reports maintain consistent 13mg/transition across diverse filament pairs (PLA/PETG, PLA/PVA, TPU/PLA) — or does the 13mg figure vary significantly by material combination?
- Does Prusa confirm a second Prusa Edition batch timeline in the next 7–14 days — addressing the sold-out first batch supply constraint for buyers who specifically want the Prusa Edition configuration?
- Does the community r/3Dprinting evaluation thread establish a definitive 'clean transition test' benchmark — zero-contamination prints at maximum tool-change density — as the INDX vs. AMS 2 Pro quality separator?
⏸️ Wait if: You specifically want the Prusa Edition kit configuration (ships June 2026; first batch sold out; second batch timeline unconfirmed) — if June timeline works for your project schedule, wait; if you need immediate access, the Bondtech Founders Edition path is available now
✅ Buy if: You need near-zero filament waste in high-transition multi-material printing and the $999–$1,249 premium over X2D + AMS 2 Pro is within budget — CORE One + INDX 4T ~$1,998; 13mg/transition stable three-source confirmed; 15-second calibration confirmed; open-ecosystem hardware; Bondtech Founders Edition available now
Prusa OCL Day 3 — Tom's Hardware Coverage Confirmed; Developer Counter-License Published; Josef Prusa 'Security Risk' Framing Gaining Traction; OSHWA Endorsement Pending
The Prusa Research Open Community License (OCL) enters Day 3 (Friday May 29). Tom's Hardware coverage is confirmed published (verified in search results). A developer has released a 'Simplified Open Community License' as a formal critique of Prusa's OCL framing — the counter-license challenges OCL's scope restrictions and offers an alternative framework (per Fabbaloo coverage). Josef Prusa's characterization of Bambu Lab's conduct as a 'security risk to the open-source 3D printing ecosystem' continues gaining traction as the editorial frame across publications covering OCL. Community debate has crystallized: some voices argue OCL is 'neither open nor for the community' (lawyer analysis published via Adafruit blog); others see OCL as necessary and overdue hardware protection against commercial exploitation without community reciprocity. OSHWA (Open Source Hardware Association) endorsement: pending — not yet confirmed as of Day 3. OCL fills the hardware protection gap left by GPL-family licenses (PCBs, mechanical assemblies, 3D-printable parts). Announced directly in response to the Bambu Lab AGPLv3 Day 9 context.
Day 3 with Tom's Hardware coverage and a developer-published counter-license represents the OCL moving into its active community-debate phase: the license text is published, expert analysis is underway, and the open-source hardware community is producing structured critiques and alternatives. The 'neither open nor for the community' legal critique is a significant signal — if the lawyer analysis holds up under broader review, OCL may face a reframing challenge similar to what 'open source' debates have historically produced when licensing terms are restrictive. OSHWA endorsement remains the key external validation milestone.
💡What this means for you
Prusa OCL Day 3 (May 29, Friday): OCL scope: hardware designs including PCBs, mechanical assemblies, 3D-printable parts, enclosure geometry. Permission structure: free use, modification, sharing for non-commercial and community purposes. Restriction: commercial exploitation without reciprocal community contribution prohibited. Tom's Hardware coverage: published and confirmed (search-verified). Developer counter-license: 'Simplified Open Community License' released by unnamed developer — published as critique of OCL; challenges scope restrictions; offers alternative framework (Fabbaloo coverage). Lawyer analysis (Adafruit blog): OCL characterized as 'neither open nor for the community' — argument that commercial-exploitation restriction disqualifies OCL from 'open' classification under OSI/OSD definitions. OSHWA (Open Source Hardware Association) endorsement: pending, not yet confirmed Day 3. Josef Prusa framing: 'security risk to the open-source 3D printing ecosystem' — gaining editorial traction. OCL context: announced May 27, Day 9 of Bambu AGPLv3 dispute.
Market Position: OCL Day 3 with an active developer counter-license and a formal lawyer critique represents the fastest maturation of an open-hardware license debate in maker-community history. The OSHWA endorsement decision — when it comes — will be the definitive signal: OSHWA approval validates OCL as an open-hardware standard; OSHWA rejection or silence would confirm the 'neither open nor for the community' critique. For open-hardware projects beyond Prusa (Voron, RatRig, laser cutter frames): the outcome of the OCL OSHWA debate will determine whether OCL becomes a community-standard protective tool or a Prusa-specific commercial-protection instrument.
- Does OSHWA issue a formal endorsement or rejection of OCL within Days 3–14 — and does the endorsement decision align with or contra the published 'neither open nor for the community' lawyer analysis?
- Does Bambu Lab respond to the Tom's Hardware OCL coverage and Josef Prusa's 'security risk' characterization — either disputing the framing or acknowledging OCL as a reasonable hardware protection framework?
- Does the developer-published 'Simplified Open Community License' counter-license gain adoption traction in the open-hardware community — potentially splitting the hardware licensing reform conversation between two competing frameworks?
⏸️ Wait if: You are an open-hardware project maintainer evaluating whether to adopt OCL for your PCB or mechanical designs — wait for the OSHWA endorsement decision before committing; the 'neither open nor for the community' critique and developer counter-license indicate the license debate is not settled on Day 3
✅ Buy if: You are a Prusa ecosystem buyer evaluating whether the OCL signals long-term open-hardware commitment from Prusa Research — OCL Day 3 confirms Prusa is actively developing hardware-specific protections in response to AGPLv3 commercial-exploitation events; that commitment signal is present regardless of how the OSHWA endorsement resolves
Frequently Asked Questions
The Bambu X2D PETG community results are now published — where do I find them and what should I look for?▼
The OTA 01.01.01.00 PETG result window ran Days 28–31 (May 24–27). Results were published Day 31–32 and are now stable as of Day 33. Search r/3Dprinting for 'OTA 01.01.01.00 PETG results' or 'X2D PETG prime tower fix' — filter by 'Past Month' to find Day 29–32 posts. On the BambuLab official forum, search 'OTA 01.01.01.00 PETG.' Look for: (1) confirmation that prime tower instability during PLA/PETG mixed prints is resolved; (2) whether results are consistent across multiple PETG brands or limited to specific filaments; (3) whether any users report remaining issues, indicating V01.01.00.65 Public Beta is the intended full fix. The data is settled — 30 minutes of search will give you a complete empirical picture.
What is the 'Simplified Open Community License' counter-license and why was it published in response to Prusa's OCL?▼
A developer published the 'Simplified Open Community License' (reported via Fabbaloo on OCL Day 3) as a formal critique of Prusa's Open Community License. The counter-license challenges OCL's commercial-exploitation restriction, which lawyer analysis (published via Adafruit blog) characterized as making OCL 'neither open nor for the community' — arguing that restricting commercial use without reciprocal contribution disqualifies OCL from being classified as 'open' under OSI Open Source Definition standards. The counter-license proposes an alternative framework that retains community-protection intent while meeting broader open-source classification criteria. The OSHWA endorsement decision will be the authoritative signal on which framework aligns with recognized open-hardware standards.
After 11 days, are Bambu Lab's AGPLv3 violations actually affecting my X2D or OrcaSlicer workflow?▼
As of Day 11, the AGPLv3 violations have not affected hardware function or OrcaSlicer usability. The X2D, A1 Mini, P1S, and X1C print normally. OrcaSlicer remains functional and accessible. The two violations — libbambu_networking source code non-disclosure and the Jarczak cease-and-desist — are formal compliance failures documented by the Software Freedom Conservancy, but they have not produced operational disruptions. The relevant risk for users is ecosystem uncertainty: the baltobu project ($250,007+ funded) is executing a Bambu Studio replacement fork and libbambu reverse engineering, which represents a long-duration ecosystem restructuring program. For day-to-day printing: no impact. For multi-year Bambu ecosystem investment decisions: the SFC committee details expected in June are the next material signal.
Why does the Prusa INDX cost nearly $1,000 more than the Bambu X2D with AMS 2 Pro — is the 13mg purge figure really worth the premium?▼
The cost delta (CORE One + INDX 4T ~$1,998 vs. X2D + AMS 2 Pro ~$999) is $999. The 13mg/transition figure is confirmed stable across three independent sources as of Day 7. Whether it's worth the premium depends entirely on print volume and transition density. On a 500-transition multi-color print: INDX wastes ~6.5g (at $0.02/g PLA = ~$0.13 in waste); AMS 2 Pro wastes ~250–400g (~$5–8 in waste). If you run 200 such prints per year: INDX saves ~$1,000–1,600 annually in filament waste — potentially recouping the premium in Year 1. If you run 20 such prints per year: savings are ~$100–160, and the $999 premium takes 6–10 years to recoup. The break-even is entirely dependent on your multi-color transition print volume.