Finally it's here and it's working. Thanks to great work of Alexey Cluster!

So here is the source: https://github.com/ClusterM/open-bambu-networking

And I've compiled it for Orca Slicer 2.3.2 and above (tested on dev build 2.4.0): https://github.com/Lojza007/open-bambu-networking/releases

It works with Alexey P2S and mine P1S. Now you can access files on printer and time lapses too. And I hope it'll be soon included in Orca Slicer.

If you want to compile by your self you need:

- GIT: https://github.com/git-for-windows/git/releases/tag/v2.54.0.windows.1

- Visual Studio 2019 Community Edition: https://aka.ms/vs/16/release/vs_community.exe (and select Desktop development with C++)

- VCPKG: https://github.com/microsoft/vcpkg (and after clone execute bootstrap-vcpkg.bat)

And then you need to open Developer PowerShell for VS 2019 and execute:

$env:VCPKG_ROOT = "C:\path\to\vcpkg"
.\configure.ps1 -ClientType orca_slicer
cmake --build   build --config Release
cmake --install build --config Release

Hello everyone!

As governments are trying to control our 3D printers, and as BambuLab seems to be taking a sharp turn towards enshitification, I wanted to share something I worked on over this weekend that's got me feeling a whole lot safer about my BambuLab P1S.

As I was not aware about BambuLab's bad track record and general direction, I wanted to have a closed system that would keep functionality while retaining privacy. Because of this, I've set up a Raspberry Pi 4 (8GB model) as a little home server that allows me to control my printer without BambuLab having access to it. This is the idea:

1. Raspberry Pi is hardwired to network, then uses Wi-Fi antenna to broadcast a hotspot
2. This hotspot is cut off from internet access, making sure no one but you can access the 3D printer.
3. The Raspberry Pi runs a Tailscale client and broadcasts the 3D printer as a subnet
4. Your other devices can access that 3D printer as if it were on LAN mode.

It took me some heavy troubleshooting, and admittedly I did have Claude guide me through this, but the results are very much so real and as far as I can tell, stable. Below is a link to a github repo with what are essentially step by step instructions I had Claude generate and which I reviewed. If something is off or doesn't work, feel free to point it out and I'll do my best to correct it.

Repo: https://github.com/joel-sgc/Offline-BambuLab-Project

This box comes up every time I open a new model. The way it's worded and the options it presents is always confusing to me.

What I think it's trying to say is "Hey! We know you have your usual preset settings in your orcaslicer. This project has slightly different settings built into it. Do you want to use the settings you normally use, or do you want me to change the settings to the ones inside this project?" Is that correct?

If that's what it's trying to ask, the wording is very confusing. I haven't "changed" any settings yet - I've just opened a project. I don't know if I want to "save or discard the preset values I have modified" because I haven't modified any settings yet. I don't know if I want to "transfer the values I have modified" because I haven't modified any values yet. I don't understand what "old" and "new" value mean in the context of the question, does it mean "my usual settings" and "the settings saved in this STL"?

How am I supposed to properly understand this dialogue box, and which is the right answer? Thanks!

Here is a video with the new Z contouring setting:

https://youtube.com/shorts/Z7DBJlsTbqE?feature=share

I'm printing something that needs a specific grain -- with 100% infill aligned in one direction. In Prusa Slicer, that means using Aligned Rectilinear infill. In OrcaSlicer, the Aligned Rectilinear algorithm doesn't seem to do that. Is there some way to force it to make EVERY bit of infill be aligned, like Prusa Slicer does?

0.4 HF nozzle.
PLA Matte, calibrated and dried.

220c nozzle, 55c plate

, 0.8mm retraction

Sliced in Orca 2.3.2.

I've getting insane about this!

Hi all, I've been getting these irritating line issues when printing parts that have supports / overhangs (shown in picture 1). They seem to correspond to decreases in fan speed for just those layers, which seem to correspond to the presence of overhangs or support interfaces in those layers.

You can see this in-person in picture 2, but this has been happening for a while now, always in the same places. I'm printing Elegoo's PETG-Rapid at 250C with plenty of drying time on an AD5M. 0.2mm layers, 0.4mm nozzle, most everything else set to Orca's "Elegoo PETG Rapid" preset.

Any ideas on how to stop Orcaslicer from altering the fan speed for the rest of the layer while still cooling the overhangs/interfaces properly?

Any other critiques on print quality, settings, etc. are appreciated!

I’m adding a negative part for a magnet. I’ve got my dimensions in and the pause but for some reason it’s adding a color change around my part. In the area of the print where the magnet will sit is all one color. Why is the slicer making that area red and how can I fix it?

I’ve been considering to switch from Cura to Orca since I’ve started to upgrade the overall speed of printer (Ender 3 S1 Plus) and I can’t seem to get my prints matching the Cura quality. Left (Orca) and right (Cura) the print settings are nearly identical. The print time from Orca is about 30% less but I don’t want my print quality to suffer.

Any tips on how to work with the Orca slicer and the what to change for its engine?

Thanks in advance!

Dear Tinkerers,

Im having an issue i cant quite understand. Im using a clean stl model with quite a lot of surfaces. When orca slices it its somehow roughening the surface. Anyone know a solution?

OrcaSlicer fork with native Creality K1/K2 CFS filament sync

I forked OrcaSlicer 2.3.2 to add a feature I'd been missing: a one-click "Sync filaments from CFS" button that talks directly to the Creality K1/K2 CFS over Moonraker, just like the AMS sync works for Bambu Lab printers.

What it does

Press the existing AMS sync button in the filament toolbar with a Creality printer selected, and OrcaSlicer queries /printer/objects/query?box, parses the four CFS slots (T1A through T1D, with multi-unit support up to T4), decodes the proprietary Creality material codes (001001 → PLA, 002xxx → PETG, etc.), strips the leading-zero color prefix Creality uses (0FF1E1E → #FF1E1E), and updates the project filaments live — no restart, no closing the slicer, no editing config files.

Requirements

• A Creality K1, K1C, K1 SE, or K2 with the CFS attached
• Moonraker running (the printer needs Helper Script / fluidd / mainsail installed; stock firmware doesn't expose Moonraker)
• Printer host configured in OrcaSlicer as http://<printer-ip>:7125

Why I built it

Creality Print works fine but I prefer Orca's slicing engine, profile system, and tree supports. Until now using Orca with the CFS meant clicking each of the four slot color circles by hand every time you swapped a spool. Annoying when you have three boxes daisy-chained.

The official OrcaSlicer Moonraker integration handles AFC and Happy Hare already but doesn't know about Creality's box Klipper object, which is a proprietary structure (T1/T2/T3/T4 units with parallel arrays for material, color, vendor and remaining length). The patch adds a fetch_creality_box_filament_data method to MoonrakerPrinterAgent plus a small bypass in Sidebar::build_filament_ams_list that talks to Moonraker directly so it works regardless of which agent is active.

Patch

The actual changes are minimal: ~250 lines of C++ across MoonrakerPrinterAgent.cpp/.hpp and Plater.cpp. I'll send a PR upstream once I've cleaned it up — interested to hear if anyone with a K2 wants to test multi-unit chained CFS support, since I only have one CFS unit.