3D Printing News Digest - May 26, 2026
Published
X2D Day 30: ten post-plateau days; OTA PETG result window Days 28–31 active; V01.01.00.65 beta parallel. AGPLv3 Day 8: resolution phase; violations unresolved; baltobu active. Prusa INDX Day 4: 15-sec calibration confirmed; Bondtech Day 4 reports; ~$1,998 CORE One + INDX 4T. Hi Combo Day 13: 13 days no CFS firmware.
Bambu Lab X2D Day 30: TEN Days Post-Plateau — First Round-Number Milestone; OTA 01.01.01.00 PETG Result Window Entering Final Days (28–31); V01.01.00.65 Public Beta Still Active; Community PETG Reports Forming
The Bambu Lab X2D reaches Day 30 (Tuesday May 26), entering the most significant single-day milestone of its post-plateau period: ten consecutive days past THE Community Evaluation Plateau (Day 21, May 17). Day 30 = ten post-plateau days, a round-number milestone that carries weight in community evaluation narratives. The OTA 01.01.01.00 community PETG result window (Days 28–31, May 24–28) is in its third day — with the most concentrated empirical PETG resolution reports appearing Monday through Wednesday of this week. V01.01.00.65 Public Beta remains active in parallel with OTA 01.01.01.00; beta testers' PETG results are among the most relevant data points this week, as beta units may have had the optimization active for longer than production OTA units. The X2D firmware release history page (wiki.bambulab.com) documents the dual-track firmware cadence for buyers who want to verify the version lineage between OTA 01.01.01.00 and V01.01.00.65. Ten consecutive post-plateau days with zero new systematic issues, active dual-track firmware improvement, and an empirical PETG resolution data window represents the most complete buyer-evaluation baseline of any consumer FDM printer at this price point. The Hi Combo Day 13 comparison: 13 consecutive days without a CFS firmware update, no Day 21 plateau equivalent, no public beta program — the asymmetry at Day 30/13 is wider than any previous day in the comparison's history.
Day 30 Tuesday is the midpoint of the OTA 01.01.01.00 PETG result window (Days 28–31 = May 24–28) — the most data-rich day of the PETG resolution evaluation period. If PETG resolution reports are positive through today, the X2D's data picture shifts from 'ten post-plateau days with one bounded edge case' to 'ten post-plateau days with confirmed firmware resolution of the only flagged edge case' — the most complete buyer-evaluation baseline in the X2D's retail history. For buyers who have been explicitly monitoring PETG: today's r/BambuLab forum and the Bambu community forum PETG thread are the primary data sources. The Day 30 round-number milestone also carries communication weight: community members who post periodic evaluations (Day 7, Day 14, Day 21, Day 30) are more likely to post today than on any other day since Day 21, creating a natural data aggregation point.
💡What this means for you
Bambu X2D Day 30 (May 26, Tuesday — post-plateau Day 10): OTA 01.01.01.00 rolling out (initiated Day 28, Sunday May 24) — PETG result window Day 3 of 4 (Days 28–31). V01.01.00.65 Public Beta: announced ~mid-May, active in parallel. Spec: $649 base / $899 Combo, 256×256×260mm build, 65°C active chamber, MECA dual-nozzle, LiDAR leveling, UL 2904. Post-plateau status (Days 21–30): zero new systematic issues through Day 30. PETG edge case: OTA 01.01.01.00 targets PLA-PETG interface layer, flushing workflow, prime tower stability. Data source for PETG results: Bambu community forum PETG thread, r/BambuLab, V01.01.00.65 beta tester thread. Hi Combo Day 13: 13 consecutive days no CFS firmware; no plateau equivalent; $50 X2D premium ($649 vs. $599) most empirically supported day in comparison history. Round-number Day 30: natural data aggregation point for community periodic evaluations.
Market Position: Day 30 Tuesday with the PETG result window at midpoint is the most technically significant day of the X2D's first retail month. Ten post-plateau days with zero new systematic issues and an active dual-track firmware program addressing the only flagged edge case is the strongest possible data picture at the 30-day retail mark.
- Do the Day 28–30 community PETG reports establish a positive resolution consensus — confirming OTA 01.01.01.00 addressed the PLA-PETG interface edge case — by the time the result window closes at Day 31 (Wednesday May 27)?
- Does the Day 30 round-number milestone trigger any structured community evaluations (periodic 30-day owner reports) that produce the first extended-use data points at the 30-day mark?
- Does Bambu Lab issue any Day 30 communication — a firmware changelog clarification, V01.01.00.65 beta update, or OTA 01.01.01.00 release note — that formally documents what the PETG optimization addresses?
⏸️ Wait if: You want confirmed PETG resolution reports before committing — the result window closes at Day 31 (Wednesday May 27); if you check the Bambu forum tomorrow, the window will be complete; the $649 price and dual-track firmware cadence are already confirmed
✅ Buy if: You want dual-material FDM under $1,000 with the most complete 30-day post-launch data picture available — $649 base; ten post-plateau days; OTA PETG optimization active; V01.01.00.65 beta parallel; Hi Combo Day 13 no-firmware makes the $50 X2D premium straightforward
Bambu Lab AGPLv3 Day 8: Resolution Phase — Major Outlet Coverage Stable; Two SFC Violations Formally Unresolved; baltobu Funded Staff Work Continues; OrcaSlicer Functional Through Day 8
The Bambu Lab AGPLv3 controversy enters Day 8 (Tuesday May 26) in the resolution phase. The Day 7 major outlet coverage (Tom's Hardware, Notebookcheck, 3D Printing Industry, Jeff Geerling, Slashdot) is now stable — no new major outlet publications on Day 8, but the existing coverage remains indexed and actively driving buyer awareness. The two SFC-confirmed violations remain formally unresolved: (1) libbambu_networking proprietary library distributed without source code disclosure (AGPLv3 violation); (2) legal threats against developer Paweł Jarczak restricting his AGPLv3 rights. Bambu Lab's backtrack statement to All3DP acknowledges the legal threat framing but does not address either violation directly. baltobu funded-staff work continues: the $250,007 funded project is in early execution phase for libbambu_networking reverse engineering, OrcaSlicer fork maintenance (Jarczak), and Bambu Studio replacement fork development — a program expected to take several months. OrcaSlicer remains fully functional for all X2D and H2D owners through Day 8. Hardware unaffected. The Josef Prusa 'security risk' framing in Tom's Hardware represents the most mainstream articulation of the controversy's practical buyer implications: buyers who cannot use software with an unaudited proprietary network library face a different evaluation than buyers primarily concerned with print quality and firmware stability.
Day 8 Tuesday in the resolution phase means the controversy has entered the period where major outlet coverage is stable and the baltobu project is in execution mode — neither escalating nor resolving rapidly. For X2D and H2D buyers: Day 8 is the first day the controversy can reasonably be evaluated as a 'background governance story' rather than an active escalating news event. The key buyer question at Day 8: does the Josef Prusa security framing (unaudited proprietary network library) apply to your specific usage context? For professional users with network security requirements: the libbambu_networking violation is a practical concern, not just a community governance story. For home users and makers: OrcaSlicer is functional, hardware is unaffected, and the baltobu project is weeks to months from producing replacement tooling.
💡What this means for you
Bambu Lab AGPLv3 Day 8 (May 26, Tuesday — resolution phase): Major outlet coverage (Day 7 publications): Tom's Hardware (two articles), Notebookcheck, 3D Printing Industry, Jeff Geerling blog, Slashdot, aftermath.site, gsmgotech — all indexed and stable. No new major outlet publications on Day 8. SFC violations (confirmed May 18): (1) libbambu_networking without AGPLv3 source disclosure; (2) legal threats against Jarczak restricting rights — both formally unresolved. Bambu backtrack statement: acknowledged 'came across as legal threat'; did not address either violation directly. baltobu ($250,007 funded): libbambu_networking reverse engineering + Jarczak OrcaSlicer fork maintenance + Bambu Studio replacement fork — months-long execution. OrcaSlicer: functional and downloadable on Day 8. Hardware (X2D, H2D): unaffected. Josef Prusa quote (Tom's Hardware): security risk framing for unaudited network black box.
Market Position: Day 8 resolution phase marks the transition from escalating news event to sustained governance story. The controversy is now stable enough that it can be evaluated as a background factor rather than a day-to-day decision modifier — but the two violations remain unresolved and the baltobu project is in active execution.
- Does Bambu Lab issue any Day 8 or Day 9 follow-up addressing the libbambu_networking source code disclosure — the primary violation that the backtrack statement did not address?
- Does the baltobu project produce any early execution update (a Week 1 progress post, initial libbambu_networking analysis, or Jarczak OrcaSlicer fork milestone) this week?
- Does the Jeff Geerling blog post's reach in the security and open-source community drive any enterprise or professional buyer re-evaluation of Bambu Lab machines in institutional settings?
⏸️ Wait if: Your X2D/H2D purchase is contingent on AGPLv3 full resolution — the baltobu project is months from completion; the violations are unresolved; for security-sensitive institutional buyers, the Josef Prusa framing applies; waiting for resolution means waiting several months
✅ Buy if: You are evaluating X2D based on hardware and software capabilities for home or maker use — OrcaSlicer functional Day 8; hardware unaffected; the controversy is a governance story for home buyers, not a hardware capability story; ten post-plateau days support hardware evaluation independently of the controversy
Prusa CORE One INDX Day 4: 15-Second Calibration Per Toolhead Confirmed — Bondtech Founders Edition Day 4 Field Reports; $1,998 CORE One + INDX 4T Total System; Community AMS Comparison Deepening on r/3Dprinting
The Prusa CORE One INDX conversion kit reaches Day 4 of open orders (Tuesday May 26). A key practical specification is confirmed from Prusa's documentation and Bondtech Founders Edition Day 4 field reports: 15 seconds per toolhead calibration time. The INDX system includes a new toolhead offset calibration reference fixture permanently mounted outside the print area — meaning once initial setup is complete, re-calibration after a toolhead change requires approximately 15 seconds per head. For an 8-tool INDX configuration, full re-calibration takes approximately 2 minutes. This is a significant practical differentiator from the Bambu AMS 2 Pro's single-calibration approach. The combined system cost at Day 4: CORE One ($1,249) + INDX 4T ($749) = ~$1,998 total; CORE One + INDX 8T = ~$2,248 total. Community r/3Dprinting comparison threads are deepening: the near-zero purge waste architecture (~13mg per tool change vs. AMS 2 Pro ~500–800mg per transition) is the dominant comparison metric. Bondtech Founders Edition Day 4 owner field reports are forming the first extended-use calibration time baseline — the practical setup overhead that determines whether the INDX's purge savings justify the system's total cost premium over X2D + AMS 2 Pro ($999 combined).
The 15-second per-toolhead calibration confirmation is the most practically important INDX data point since Day 1: it changes the comparison from 'architectural difference' to 'quantifiable setup overhead.' For buyers evaluating the $999 X2D + AMS 2 Pro vs. the ~$1,998 CORE One + INDX 4T: the $999 premium buys (1) near-zero purge waste architecture at ~13mg per change vs. ~500–800mg, AND (2) a 15-second per-head calibration requirement when heads are changed (2 min for full 4-head re-cal; 4 min for full 8-head). Whether that calibration overhead is 'acceptable' depends entirely on how frequently the user is changing toolheads. For users who configure once and print multiple jobs with the same filaments: the 15-second calibration is essentially irrelevant. For users who frequently change toolhead configurations: the calibration overhead is a real time cost.
💡What this means for you
Prusa CORE One INDX Day 4 (May 26, Tuesday): Calibration: 15 seconds per toolhead (Prusa spec + Bondtech Day 4 confirmation). Full 4-head re-cal: ~60 seconds. Full 8-head re-cal: ~120 seconds. Toolhead offset calibration fixture: permanently mounted outside print area. INDX 4T: $749 tariffs included (US). INDX 8T: $999 tariffs included. CORE One: $1,249. Total systems: CORE One + INDX 4T = ~$1,998; CORE One + INDX 8T = ~$2,248. Vs. X2D + AMS 2 Pro: $649 + $350 = ~$999. INDX premium: $999 (4T) or $1,249 (8T) over X2D + AMS 2 Pro. Purge waste: INDX ~13mg per tool change; AMS 2 Pro ~500–800mg per filament transition. Bondtech Founders Edition: active delivery since early May 2026; Day 4 owner field reports forming. Prusa Edition: June 2026 (5–6 weeks). First batch: end of August 2026. Orders: prusa3d.com.
Market Position: Day 4 with 15-second calibration confirmed and Bondtech Day 4 reports emerging creates the first complete practical cost-of-ownership comparison for INDX vs. AMS 2 Pro. The calibration overhead quantification enables buyers to calculate their personal setup cost: if you swap heads 4 times per week, that's 4 minutes of calibration per week vs. zero incremental calibration for AMS users.
- Do Bondtech Founders Edition Day 4 field reports confirm the 15-second calibration time under production conditions — or does the practical calibration time exceed 15 seconds per head when accounting for physical head swapping and confirmation steps?
- Does the community r/3Dprinting cost-per-transition analysis thread produce a quantitative waste-cost model (total filament waste per print job at typical transition density) that gives buyers a concrete economic decision framework this week?
- Does Bambu Lab respond to the INDX Day 4 community comparison traction with any AMS purge reduction announcement — an OTA that reduces per-transition purge volume or an AMS architecture update?
⏸️ Wait if: You want Bondtech Founders Edition extended-use calibration time data before committing — expect 7–14 day owner reports (June 2–9) establishing the practical per-head calibration overhead; the 15-second spec is confirmed, but the workflow integration overhead is the remaining variable
✅ Buy if: You print high-transition multi-material jobs with expensive filaments where the purge waste math closes in 50–500 prints — INDX 4T $749 (orders open at prusa3d.com); 15-second calibration confirmed; Prusa Edition ships June 2026; near-zero purge waste is architecturally unique
Creality Hi Combo Day 13: Week 2 Day 6 (Tuesday) — 13 Consecutive Days Without CFS Firmware Update; X2D PETG Result Window Midpoint Widens Gap Further; $50 Premium Framework Unchanged
The Creality Hi Combo (K2 Plus with Color Filament System) enters Day 13 (Week 2 Day 6, Tuesday May 26) — 13 consecutive days since retail availability without a CFS firmware update. The Bambu X2D OTA 01.01.01.00 PETG result window is at midpoint today (Days 28–31, Day 3 of 4) — meaning the X2D is in active PETG resolution evaluation while the Hi Combo remains without any firmware update to address its community-flagged CFS calibration behavior. Community Tuesday data: the first full business-week evaluation period of Week 2 (Monday–Wednesday) is now producing structured community assessment data — Tuesday is the second day of the most structured evaluation week the Hi Combo has had since retail launch. The $50 premium framework ($649 X2D vs. $599 Hi Combo) remains unchanged. The structural imbalance at Day 13/30: X2D has 10 post-plateau days + dual concurrent firmware tracks (OTA 01.01.01.00 + V01.01.00.65 beta) + active PETG resolution window; Hi Combo has 13 days retail + zero firmware updates + no plateau equivalent + no beta program.
Day 13 Tuesday with 13 consecutive no-firmware days completes the Hi Combo's first 2-week retail window without a single CFS firmware improvement. The 7-day firmware standard set by the X2D (first OTA at Day 7) and the X2D's current dual-track firmware cadence creates the clearest possible comparison context for buyers still evaluating the $50 premium: the Hi Combo's 13-day no-firmware pattern is now definitively longer than 'first-week launch variability' — it is a Week 2 sustained no-firmware pattern. For buyers whose decision threshold was 'wait for CFS firmware before deciding': Day 13 has exceeded any reasonable 'early launch' firmware grace period. The comparison is now: 'Do I want the machine with 13 days of no firmware and an unknown CFS improvement cadence, or the machine with active dual-track firmware and ten post-plateau days?'
💡What this means for you
Creality Hi Combo Day 13 (May 26, Tuesday — Week 2 Day 6): 13 days retail. CFS firmware: zero updates in 13 days. K2 Plus base: CoreXY, 350mm³ build, 600mm/s, 300°C nozzle, AHT auto-leveling. CFS: up to 12-color. Price: $599. X2D Day 30 comparison: OTA 01.01.01.00 PETG result window (Day 3 of 4, midpoint) + V01.01.00.65 Public Beta — dual concurrent tracks. Ten post-plateau days. Zero new systematic issues. $649 ($50 premium). Structural comparison at Day 13/30: X2D has post-plateau validation + dual-track firmware cadence; Hi Combo has 13-day no-firmware + no plateau equivalent. 7-day OTA standard (X2D): not matched by Hi Combo at Day 13. Next Hi Combo evaluation window: Days 14–21 (June 8–15) for first stable CFS calibration baseline.
Market Position: Day 13 Tuesday completes the Hi Combo's first two retail weeks without firmware. The comparison asymmetry at Day 13/30 is permanent unless Creality releases a CFS firmware update this week. For buyers who have exhausted the 'wait for firmware' patience threshold: Day 13 is the empirical close of the 'reasonable wait' period.
- Does Creality release a CFS firmware update in Days 13–14 (May 26–27) — breaking the 13-day pattern and providing the first post-launch CFS improvement before the Hi Combo enters Week 3?
- Does the Hi Combo community produce any Day 13 structured evaluation threads documenting the first 13 days of CFS calibration behavior — the equivalent of the X2D's Day 21 plateau evaluation?
- Does the Hi Combo's 350mm³ build volume (vs. X2D's 256mm³) drive enough community adoption among large-format multi-color users to sustain the $599 value proposition despite the firmware asymmetry?
⏸️ Wait if: You specifically need 350mm³ build volume with CFS and believe Creality will release a firmware update this week — check Creality's community forum for any CFS firmware announcement; 13 days without firmware is a pattern, not a certainty; the $50 premium savings vs. X2D applies if CFS firmware arrives soon
✅ Buy if: You want the most complete multi-color FDM data picture under $700 today — X2D $649; ten post-plateau days; dual-track firmware; OTA PETG resolution window active; Hi Combo Day 13 no-firmware is the comparison baseline; the $50 X2D premium is empirically supported at Day 13
Frequently Asked Questions
The X2D OTA PETG result window closes at Day 31 — when does that happen and where do I check?▼
Day 31 is Wednesday May 27, 2026. The result window (Days 28–31) closes tomorrow. Check: (1) Bambu Lab community forum PETG thread (forum.bambulab.com — search 'X2D PETG OTA'); (2) r/BambuLab subreddit filter for X2D + OTA + PETG posts this week; (3) Bambu Wiki firmware release history for any V01.01.00.65 changelog that mentions PETG optimization scope. If positive reports dominate the window by tomorrow, the data picture shifts from 'bounded edge case' to 'confirmed resolved edge case.'
INDX calibration takes 15 seconds per toolhead — is this a deal-breaker for high-frequency multi-material users?▼
Depends on your workflow. If you configure once and run multiple print jobs with the same filament set: re-calibration is essentially never needed — 15 seconds is irrelevant. If you frequently swap toolheads between jobs (different materials, different colors per project): 8-head full re-cal is approximately 2 minutes per configuration change. For comparison, AMS 2 Pro requires no recalibration when changing filament spools — but wastes ~500–800mg of filament per transition during printing. The INDX trade-off is: 2-minute setup overhead at configuration change vs. per-print purge waste savings. For users with high-transition long-print workflows, the INDX's advantage accumulates rapidly across multiple prints.
The Bambu AGPLv3 controversy is still unresolved at Day 8 — does this change anything for buyers who bought last week?▼
Nothing practically changed since last week. OrcaSlicer is functional, Bambu Studio is functional, and the hardware is unaffected. The baltobu project is in execution mode (months away from replacement tooling). The two violations remain formally unresolved, but Bambu's backtrack statement (Day 6) represents the first step toward resolution. If you bought last week: your machine works, your slicer works, and the controversy's resolution timeline is measured in months. Monitor sfconservancy.org and baltobu for any material progress milestones.