Louis Rossmann backs OrcaSlicer dev

3D printing software is supposed to be the hackable part of the hobby. That is the whole culture — tweak the slicer, tune the profile, swap parts, make the machine yours. But Bambu Lab has spent the last year pushing users toward a more controlled setup, and now that fight has spilled into legal threats. The new flashpoint is Louis Rossmann stepping in with a public offer to fund a developer’s defense after Bambu Lab pressured him to pull an OrcaSlicer fork. ### What is OrcaSlicer, exactly? OrcaSlicer is a popular third-party slicer used by a lot of serious hobbyists because it moves fast and exposes more knobs than the official software. The family tree matters here — OrcaSlicer is a downstream fork of Bambu Studio, and Bambu Studio itself comes from PrusaSlicer, which is open-source under AGPL-3.0. That shared lineage is why people see this as more than a random vendor dispute. (tech.yahoo.com) ### What changed in 2025? In January 2025, Bambu Lab rolled out a new authorization model for “critical printer operations” and pushed third-party workflows toward Bambu Connect, a separate middleware app. Bambu said the point was security and said third-party tools could still work through Bambu Connect or through Developer Mode in LAN mode. But for many users, the practical result was that direct cloud-style control from OrcaSlicer got worse or disappeared. (forum.bambulab.com) ### What did the developer do? Paweł Jarczak built a fork called OrcaSlicer-bambulab that aimed to restore the old behavior — basically, direct internet access and printing “just like before,” without routing everything through Bambu Connect. His GitHub repo says the work used Bambu Studio’s public source plus his own integration layer, and he argues the “User-Agent” string at issue came from Bambu’s own public code. (blog.bambulab.com) ### Why did Bambu Lab object? Bambu Lab said the fork crossed a line. Jarczak’s archived explanation says the company accused his project of impersonating the official Bambu Studio client, bypassing authorization controls, violating terms of use, and creating infrastructure and security risks. That is the key split in the story — Bambu frames this as unauthorized access to a cloud service, while critics frame it as a user restoring functionality on hardware they already bought. (github.com) ### What happened to the fork? Jarczak shut the project down after the legal threat. The Bambu forum thread summarizing the dispute says he voluntarily shuttered OrcaSlicer-bambulab following pressure from the company. His GitHub page now reads like a postmortem, not an active release page. ### Where does Rossmann come in? Rossmann turned this from a niche slicer fight into a broader right-to-repair story. (github.com) Over the weekend he posted a video blasting Bambu Lab and pledged $10,000 toward the initial legal defense for the threatened developer. That matters because Rossmann has a large audience and a very clear framing — if a company can lock down features after sale and threaten the person who restores them, ownership starts to look conditional. (forum.bambulab.com) ### Why are makers so touchy about this? Because the analogy is simple — people can tolerate a closed cloud, or they can tolerate open hardware with rough edges, but they hate a company taking open-source benefits on the way up and then tightening the gates later. In desktop 3D printing, software freedom is not a side issue. It is part of the product. That is why this dispute landed so hard. (tech.yahoo.com) ### Bottom line? This is not just about one fork. It is about whether printer makers get to redefine what ownership means after the machine is already on your desk — and whether the open-source community will let them. (forum.bambulab.com 1) (forum.bambulab.com 2)