3D Printing News Digest - May 25, 2026
Published
Bambu X2D Day 29: nine post-plateau days; OTA 01.01.01.00 community PETG results entering Day 28–31 window; V01.01.00.65 public beta active. AGPLv3 Day 7: baltobu funded; Bambu backtrack across major outlets; two SFC violations unresolved. Prusa INDX Day 3: $749/$999 (4T/8T); Bondtech Founders Edition Day 3. Hi Combo Day 12: 12 days no CFS firmware.
Bambu Lab X2D Day 29: Nine Days Post-Plateau — OTA 01.01.01.00 Community PETG Results Entering Day 28–31 Window; Firmware V01.01.00.65 Simultaneously in Public Beta; First Empirical PETG Resolution Data Expected Today–Wednesday
The Bambu Lab X2D reaches Day 29 (Monday May 25), nine days past THE Community Evaluation Plateau (Day 21, May 17). OTA 01.01.01.00 began rolling out at Day 28 (Sunday May 24) — the community PETG purge result window is now active: the first empirical data on whether OTA 01.01.01.00 resolves the PETG purge edge case is expected in the Day 28–31 range (May 24–28), with the most concentrated report volume expected Monday through Wednesday. Simultaneously, Bambu Lab has released X2D firmware V01.01.00.65 in the Public Beta Program — announced approximately one week ago in mid-May. The V01.01.00.65 beta version may represent a pre-release staging number for the same improvements included in OTA 01.01.01.00, or it may be a parallel beta track targeting additional features beyond PETG optimization. Community beta testers with V01.01.00.65 installed are among the most relevant data points for Monday: their PETG results would be the earliest empirical confirmation of the firmware's actual PETG purge behavior. Nine consecutive post-plateau days with zero new systematic issues and an active dual-track firmware improvement program (OTA + Public Beta) represents the most robust post-launch data picture of any consumer FDM printer at this price point.
Day 29 Monday is the first business day of the post-OTA PETG result window — the most important single day for PETG resolution data in the X2D's post-plateau history. The parallel existence of OTA 01.01.01.00 (rolling out to production units) and V01.01.00.65 Public Beta is notable: Bambu is running two concurrent improvement tracks, which suggests the beta program is testing features beyond the PETG optimization scope of 01.01.01.00. For X2D buyers whose only remaining concern was PETG purge behavior: checking the Bambu Lab community forum Monday evening or Tuesday morning for V01.01.00.65 beta tester PETG reports is the most efficient data-gathering action. If PETG empirical reports are positive by Wednesday, the X2D's data picture shifts from 'nine post-plateau days with one bounded edge case' to 'nine post-plateau days with active firmware resolution of the only edge case' — the most complete buyer-evaluation baseline of the product's retail history.
💡What this means for you
Bambu X2D Day 29 (May 25, Monday — post-plateau Day 9): OTA 01.01.01.00 rolling out (initiated Day 28 Sunday). Community PETG result window: Days 28–31 (May 24–28) — most concentrated results Monday–Wednesday. V01.01.00.65 Public Beta: announced ~mid-May, now in active beta testing. Beta may represent pre-release staging for 01.01.01.00 features or parallel feature track. Specs: $649 base / $899 Combo, 256×256×260mm build, 65°C active chamber, MECA dual-nozzle, LiDAR leveling, UL 2904. Post-plateau status (Days 21–29): no new systematic issues. PETG edge case: targeted by OTA 01.01.01.00 (PLA-PETG interface optimization, prime tower stability, flushing workflow). Hi Combo Day 12: 12 days no CFS firmware — X2D data gap widest. Forum monitoring: Bambu community forum PETG thread and V01.01.00.65 beta tester reports are the primary data sources for Monday.
Market Position: Day 29 Monday with dual firmware tracks active (OTA + Public Beta) and PETG results imminent is the most technically active single day in the X2D's post-plateau period. For buyers monitoring the PETG edge case: today through Wednesday is the data window. The dual-track firmware activity suggests Bambu is actively maintaining the X2D with a cadence that the Hi Combo has not matched at Day 12.
- Do the first V01.01.00.65 Public Beta tester PETG reports appear Monday (first business day post-OTA rollout) — providing the earliest empirical data on whether the firmware addresses the PLA-PETG interface edge case?
- Is V01.01.00.65 a staging version of OTA 01.01.01.00's features, or does the beta track include additional features beyond PETG optimization — and does the beta changelog reveal what Bambu is targeting beyond the community-flagged edge case?
- Does the Hi Combo receive a CFS firmware update in the week of May 25–29 — breaking the 12-day no-firmware pattern and changing the empirical comparison with the X2D?
⏸️ Wait if: You want OTA 01.01.01.00 PETG results confirmed before committing — first empirical reports likely today through Wednesday; if PETG purge is your specific concern, checking the Bambu forum Monday evening or Tuesday morning is the most efficient validation path
✅ Buy if: You want dual-material FDM under $1,000 with an active firmware cadence — $649 base or $899 Combo; nine days post-plateau, zero new systematic issues, OTA 01.01.01.00 targeting PETG; Hi Combo Day 12 no-firmware makes the $50 X2D premium clear
Bambu Lab AGPLv3 Day 7: Sustained Engagement Phase — Bambu Backtrack Statement Published Across Tom's Hardware, Notebookcheck, 3D Printing Industry, Jeff Geerling; Two SFC Violations Formally Unresolved; baltobu Funded Work Beginning
The Bambu Lab AGPLv3 controversy enters Day 7 (Monday May 25) in the sustained engagement phase. The Day 6 milestones — baltobu fundraiser meeting its $250,007 goal and Bambu Lab's official backtrack statement to All3DP — have been picked up and reported across major technology outlets: Tom's Hardware ('Open-source non-profit claims Bambu Lab violated license — move follows cease-and-desist demand on OrcaSlicer fork'), Notebookcheck ('Bambu Lab backtracks after SFC accuses company of AGPL violations and legal threats'), 3D Printing Industry ('Bambu Lab Now Under Formal Investigation for AGPLv3 Violations'), Jeff Geerling's widely-read tech blog ('Bambu Lab is abusing the open source social contract'), and Slashdot ('Open Source Project Shuts Down Over Legal Threats from 3D Printer Company Bambu Lab'). The two SFC-confirmed violations remain formally unresolved: (1) libbambu_networking proprietary library distributed without source code disclosure; (2) legal threats against developer Jarczak constituting AGPLv3 restriction. Bambu Lab's backtrack statement does not address either violation directly. The baltobu funded-staff work has begun: the $250,007 activates SFC dedicated staff for libbambu_networking reverse engineering, Jarczak's OrcaSlicer fork maintenance, and Bambu Studio replacement fork development — a months-long program now with professional staffing.
Day 7 with major outlet coverage active represents a significant escalation in the controversy's public profile: the Day 6 milestones (baltobu goal + Bambu backtrack) were picked up by the outlets that matter most for Bambu Lab's mainstream market. Tom's Hardware and Notebookcheck are primary research sources for the buyers of Bambu Lab machines — their coverage of the controversy reaches buyers who had not been following the community-level thread. The Jeff Geerling blog post ('abusing the open source social contract') carries particular weight: Geerling is a credible open-source community voice with a substantial tech readership that overlaps with Bambu Lab's professional user base. For X2D and H2D buyers evaluating hardware: the Day 7 expanded coverage does not change the practical timeline (OrcaSlicer is functional today; hardware is unaffected; legal resolution is months away) — but it does mean more buyers entering the market this week are aware of the controversy before making purchase decisions.
💡What this means for you
Bambu Lab AGPLv3 Day 7 (May 25, Monday): Major outlet coverage active: Tom's Hardware (two articles), Notebookcheck, 3D Printing Industry, Jeff Geerling blog, Slashdot, aftermath.site, gsmgotech. SFC violations: two confirmed (May 18) — (1) libbambu_networking proprietary library without source disclosure; (2) legal threats against Jarczak restricting AGPLv3 rights — both formally unresolved. Bambu backtrack statement (All3DP): 'We nonetheless regret that our reference to Terms of Service, legal context and a potential C&D understandably came across as a legal threat.' baltobu: $250,007 funded — dedicated staff active for reverse engineering, OrcaSlicer maintenance, Bambu Studio fork development. Josef Prusa quote (Tom's Hardware): warned Chinese 3D printing software poses massive security risks due to un-auditable network black box. OrcaSlicer: functional and downloadable, unaffected Day 7. Hardware (X2D, H2D): unaffected.
Market Position: Day 7 major outlet coverage creates the widest single-day public awareness of the controversy since the SFC announcement on May 18. The Josef Prusa quote in Tom's Hardware adds a competitive voice to the controversy — Prusa's 'security risk' framing reaches a different segment of buyers than the open-source compliance community's 'license violation' framing.
- Does Bambu Lab issue any Day 7 follow-up statement addressing the libbambu_networking source code disclosure requirement — the primary violation that the backtrack statement did not address?
- Does the Josef Prusa 'security risk' framing in Tom's Hardware drive any Bambu Lab enterprise or professional user re-evaluation of their network architecture?
- Does the baltobu funded-staff activation produce any immediate technical communication (libbambu_networking reverse engineering progress update, Jarczak OrcaSlicer fork release, replacement Bambu Studio fork milestone) in the week of May 25–31?
⏸️ Wait if: Your X2D or H2D purchase decision is contingent on AGPLv3 full resolution — the funded baltobu project is a months-long effort; major outlet coverage increases awareness but does not accelerate legal resolution; OrcaSlicer functional today
✅ Buy if: You are evaluating X2D based on hardware and software capabilities — Bambu Studio is functional, OrcaSlicer is functional, the hardware is unaffected through Day 7; the controversy is a governance story, not a hardware capability story; the Josef Prusa security concern is about network architecture, not print quality or firmware stability
Prusa CORE One INDX Day 3: Pricing Confirmed $749/$999 (4T/8T) Tariffs Included — Bondtech Founders Edition Day 3 Owner Calibration Reports Forming; Prusa Edition June 2026 Shipping; Near-Zero-Waste Architecture vs. AMS/CFS Comparison Building
The Prusa CORE One INDX conversion kit reaches Day 3 of open orders (Monday May 25). Pricing is now fully confirmed: $749 for the 4-tool (4T) configuration and $999 for the 8-tool (8T) configuration, tariffs included for US buyers. The EU pricing is €669/€899 (4T/8T) VAT included. Prusa Edition INDX conversion kits for the CORE One/+: shipping June 2026. Bondtech Founders Edition (Bondtech-manufactured, co-engineered): in active delivery since early May 2026, now at Day 3 of the public order window. Community Day 3 activity: first Bondtech Founders Edition owner calibration reports are forming. The community structural comparison between INDX (physical toolchanger, near-zero purge waste, ~13mg per tool change, 20–30g total waste for large multi-material prints) and Bambu AMS 2 Pro (25–40mm purge per transition) and Creality CFS (firmware-dependent purge optimization) is now the dominant r/3Dprinting discussion thread. Prusa's own specification for purge waste: approximately 13 milligrams per tool change — compared to AMS's 25–40mm of filament per transition (≈0.5–0.8g per transition for 1.75mm filament), the INDX's per-change waste is orders of magnitude lower.
Day 3 with the $749/$999 pricing confirmed and Bondtech Founders Edition calibration reports forming is the first day the INDX's community evaluation has quantitative price data alongside early hardware data. The $749 4T pricing means a CORE One + INDX 4T system costs approximately $1,249 + $749 = ~$1,998 (vs. X2D + AMS 2 Pro at $649 + $350 = ~$999). The $999 premium over the X2D + AMS 2 Pro system is the price of eliminating per-transition purge waste architecturally — if your printing involves high-transition multi-material jobs with expensive filaments, the math changes significantly. The ~13mg vs. ~500–800mg per transition comparison is the most concrete data point the INDX has produced: for users printing at 10 transitions per layer × 100 layers, the AMS wastes ~500g of filament vs. the INDX wastes ~13g — a difference that can represent $10–$50+ in filament cost per large print depending on material price.
💡What this means for you
Prusa CORE One INDX Day 3 (May 25, Monday): Pricing confirmed: $749 (4T) / $999 (8T) tariffs included. €669/€899 EU VAT included. Order status: open at prusa3d.com. First batch: shipping end of August 2026 per initial pre-order terms. Prusa Edition: June 2026 (~5–6 weeks). Bondtech Founders Edition: active delivery (early May + Day 3). Purge waste: ~13mg per tool change (Prusa spec). vs. Bambu AMS 2 Pro: 25–40mm filament per transition (≈0.5–0.8g for 1.75mm). vs. Creality CFS: firmware-dependent. CORE One + INDX 8T system cost: ~$1,249 + $999 = ~$2,248. X2D + AMS 2 Pro: ~$999 total. Premium for near-zero waste: ~$1,249. Maximum tools: 8. Community Day 3 focus: calibration time per head, first multi-material print quality, AMS comparison.
Market Position: Day 3 with pricing confirmed creates the first complete price-comparison baseline for CORE One + INDX vs. X2D + AMS 2 Pro. The $1,249 premium for near-zero purge waste is significant but quantifiable for buyers with high-transition multi-material workflows. The community comparison thread that is forming on r/3Dprinting will likely produce the first structured cost-per-transition analysis within 5–7 days.
- Do Bondtech Founders Edition Day 3 owner calibration reports establish the per-head calibration time baseline — the key practical differentiator that determines the INDX's total setup cost vs. AMS single-calibration?
- Does the community r/3Dprinting cost-per-transition analysis thread produce a quantitative waste comparison (g per 100-layer print at typical transition density) that gives buyers a concrete economic decision framework?
- Does Bambu Lab respond to the INDX Day 3 pricing and community comparison with any AMS architecture update — a purge-reduction OTA or AMS Pro 2.1 announcement?
⏸️ Wait if: You want Bondtech Founders Edition calibration time data before committing — expect Day 5–10 reports (May 28–June 3) establishing per-head calibration overhead; the $749/$999 pricing is confirmed, but the practical setup cost (calibration hours × your hourly rate) is the missing variable
✅ Buy if: You print high-transition multi-material jobs with expensive filaments where 13mg per change vs. 500–800mg per change is a meaningful cost difference — the pricing is confirmed; order at prusa3d.com; Prusa Edition ships June 2026
Creality Hi Combo Day 12: Week 2 Day 5 (Monday) — 12 Consecutive Days Without CFS Firmware Update; X2D OTA 01.01.01.00 + V01.01.00.65 Beta Dual-Track Creates Widest Data Gap Yet; $50 Premium Decisively Justified
The Creality Hi Combo (K2 Plus with Color Filament System) enters Day 12 (Week 2 Day 5, Monday May 25) — 12 consecutive days since retail availability without a CFS firmware update. The Bambu X2D now has two concurrent firmware improvement tracks: OTA 01.01.01.00 rolling out to production units (targeting PETG purge) and V01.01.00.65 in the Public Beta Program. The empirical data gap between the two machines at Day 12 represents the widest disparity in both machines' comparison history: the X2D has nine post-plateau days with zero new systematic issues plus a dual-track active firmware program addressing the only flagged edge case; the Hi Combo has 12 days of retail data with no CFS firmware, no Day 21 plateau equivalent, and no public beta program. Community Monday data: weekend Hi Combo community posts from Days 10–11 are now available for review — the weekend community data is the most complete first-11-day Hi Combo dataset for any recent multi-color FDM launch. The $50 premium for the X2D ($649 vs. $599) is supported by the most asymmetric empirical advantage gap since both machines launched.
Twelve days without a CFS firmware update after the X2D activated two concurrent firmware improvement tracks creates an unprecedented comparison asymmetry: one machine has two simultaneous firmware teams working on it; the other has been retail for 12 days with no firmware update from the manufacturer. For Hi Combo buyers who have been explicitly waiting for a CFS firmware update before making the decision: 12 days without firmware means the 'wait for firmware' justification has expired for any buyer whose decision threshold was 'first major CFS firmware update within launch month.' The 7-day firmware update standard established by the X2D's first OTA has not been matched by the Hi Combo at Day 12.
💡What this means for you
Creality Hi Combo Day 12 (May 25, Monday — Week 2 Day 5): 12 days retail. CFS firmware: no update in 12 days. K2 Plus base: CoreXY, 350mm³ build, 600mm/s, 300°C nozzle, AHT auto-leveling. CFS: up to 12-color. Price: $599. X2D comparison Day 29: OTA 01.01.01.00 rolling out + V01.01.00.65 Public Beta active — dual concurrent firmware tracks. Nine days post-plateau. Zero new systematic issues. $649 ($50 premium). Data gap at Day 12: X2D has post-plateau status + dual-track firmware; Hi Combo has 12-day no-firmware + no plateau equivalent. $50 premium decision: most empirically supported day since both machines launched. Community data available: Days 10–11 weekend posts for analysis.
Market Position: Day 12 Monday with X2D running dual concurrent firmware tracks is the most asymmetric single-point comparison in the X2D vs. Hi Combo evaluation. The X2D's firmware activity pace (two concurrent tracks addressing the same period's edge cases) vs. Hi Combo's firmware silence is not a temporary gap — it reflects a structural difference in Bambu Lab's post-launch firmware investment vs. Creality's current Hi Combo firmware commitment.
- Does Creality release a CFS firmware update in the week of May 25–29 — breaking the 12-day gap and providing the first post-launch CFS improvement?
- Does the Hi Combo reach a Day 21 plateau equivalent in the week of June 1–7 — and if so, does the community dataset at Day 21 show improvement from current CFS calibration first-week results?
- Does the Hi Combo community develop any firmware-independent CFS optimization workarounds in Days 12–21 — community-discovered settings that improve CFS performance without waiting for a Creality firmware update?
⏸️ Wait if: You specifically want CFS firmware before deciding — 12 days without firmware suggests no 7-day release cycle; check the Creality forum for any scheduled CFS firmware announcement in the week of May 25–29; the $50 X2D premium is clear but Hi Combo's 350mm³ build volume remains a real advantage for specific use cases
✅ Buy if: You want the most complete multi-color FDM data picture under $700 today — X2D $649 base; nine post-plateau days, dual-track firmware active, zero new systematic issues; Hi Combo Day 12 no-firmware is the comparison baseline; check community data before deciding on the $50 premium
Frequently Asked Questions
OTA 01.01.01.00 is rolling out AND there's a V01.01.00.65 Public Beta — are these the same thing?▼
Possibly not. OTA 01.01.01.00 targets the specific PETG purge improvements flagged by the community plateau evaluation. V01.01.00.65 entered the Public Beta Program approximately one week earlier and may represent a pre-release staging version for the same improvements, or it may be a parallel track testing additional features. The most practical way to know: check the V01.01.00.65 beta changelog on the Bambu Wiki (wiki.bambulab.com/en/x2d/manual/x2d-firmware-release-history) and the community forum beta tester thread for a feature breakdown. If V01.01.00.65 specifically mentions PETG optimization, it is likely staging for 01.01.01.00.
The INDX pricing is confirmed at $749/$999 (4T/8T) — is the $1,249 premium over X2D + AMS 2 Pro worth it?▼
Depends entirely on your per-print transition volume. The INDX wastes ~13mg per tool change; the AMS 2 Pro wastes ~500–800mg per filament transition. For a user printing 10-layer-per-transition multi-material prints across 100 layers: AMS wastes ~50–80g per print; INDX wastes ~1.3g. At $0.05–0.15/g filament cost, AMS waste is $2.50–$12/print; INDX waste is $0.065–$0.195/print. The $1,249 premium pays back in 50–500 large multi-material prints depending on material cost and transition density. If you print occasionally, the premium doesn't justify. If multi-material printing is your primary workflow with expensive materials, the math closes faster than you'd expect.
12 days without a CFS firmware update — should Hi Combo buyers give up waiting?▼
If your threshold was 'first major CFS firmware update within launch month,' Day 12 is past that threshold. The X2D's first OTA arrived approximately 7 days post-retail — Creality has not matched that cadence. The decision framework has shifted: it's no longer 'wait for firmware' but 'compare current Hi Combo community data vs. X2D Day 29 post-plateau data.' If the Hi Combo's 350mm³ build volume or 12-color CFS capability are primary for your use case, the machine's current-firmware community data is the available baseline. Check r/3Dprinting for Hi Combo Days 10–11 weekend posts today.
The Bambu AGPLv3 controversy is now in Tom's Hardware and Jeff Geerling's blog — does this change the X2D purchase calculus?▼
For most buyers: no. The hardware, Bambu Studio, and OrcaSlicer are all unaffected through Day 7. The controversy's mainstream coverage in Tom's Hardware and the Josef Prusa 'security risk' framing reach buyers who weren't following the community thread — but the practical impact is months away, tied to the SFC's funded reverse-engineering of libbambu_networking. If you are a security-sensitive professional user who cannot use software with an unaudited proprietary network library, the Josef Prusa security concern is your decision point today. For print quality evaluation, hardware reliability, and OrcaSlicer workflow: no change.