Update to OrcaSlicer 02.07 + native-Windows network bridge#40
Conversation
2902882 to
931bfe3
Compare
|
Why did you close your Request? |
|
It had a problem that didn't occur until it was in an installer. So I wanted to make sure it worked properly before anyone else tried a broken version. I have it working now and the installer is building on github: OrcaSlicer V2.4.0 Beta release with Sl1cer name change and several fixes for many Windows specific network plugin library gates. I wanted it to work like normal Orca if consumers didn't have Bambu Studio 2.7.1 installed (which is what this specific version is built against.) but that's still not strictly true yet. This build (https://github.com/danielwoz/OrcaSlicer/actions/runs/27219530485/job/80370545012) running now should work fine if you have Bambu Studio 2.7.1 installed, on Windows and use the OrcaSlicer installer that comes out of that build and only want to use Bambu printers from this release. I will work on a version that removes a lot of this qualifiers and just reverts to normal Orca behaviour if it can't use the hooks to open full bambu functionality. |
|
Github finished the build: https://github.com/danielwoz/OrcaSlicer/actions/runs/27219530485/artifacts/7515184855 let me know if it works for you. |
|
It took me some time and fiddling, but now it works! The problem was: I have BBL Studio 2.7.1.57 and the matching Network Plugin. Your build searches for .51; if it can't find it, it downloads the latest, which is .57. You get signed in but cannot connect to the printer; .51 is not an option in your build. So I deleted the BBL plugin, downloaded .51 from the API, ran BBL Studio once, then started your build, and it worked and now I can print! I don't know when the plugin gets signed, but this way worked. |
fb61c98 to
d38d421
Compare
|
Thanks for the feedback, helped me figure out a bunch more bugs / non-robustness in the install. Re-opened this pull request with all the updates. I have a proper release binary now that seemingly works regardless of your current state as long as you have the stable BambuStudio installed (either before or after install this release of OrcaSlicer). https://github.com/danielwoz/OrcaSlicer/releases/tag/v2.4.0-beta-bbl2 |
|
I installed the latest version built 5 hours ago and ran into the same issue with the plugin version, on first launch it says the plugin was succesfully installed but the UI never updates to allow sign in. On relaunch it says the network library wasn't found when searching for bambu_networking_02.07.01.51.dll. It allows me to install version 57, but then no connection to the printer can be established. Seemingly still searching for the old dll. Edit: Can confirm workaround still works. Thank you Gabriel, you saved me some time digging around in the logs :), will attempt to fix the root cause in source later tonight. Also thank you daniel for the great work! |
You can find it here: https://public-cdn.bblmw.com/upgrade/studio/plugins/02.07.01.51/02a9ecd52c/win_02.07.01.51.zip |
Single squashed commit: OrcaSlicer v2.4.0-beta with the full native-bridge work (plugin integration pinned to network plugin 02.07.01.51, genuine-host launcher with consent dialog + UAC self-heal + Bambu-installed-later support, install-time staging, vanilla fallback, print-to-cloud PrintParams fix, vcpkg auto-link disabled for self-contained builds). The OrcaSlicer-bambulab fork shares no ancestry with upstream's tag.
d38d421 to
92446fd
Compare
|
My bad, figured this out: The slic3r version is different to the network plugin version, while I was developing this I must have manually copied the version in with the wrong name. It should work out of the box now. |
What this does
Brings OrcaSlicer‑bambulab up to OrcaSlicer 02.07 (current upstream) with the newest Bambu network plugin (02.07.01.57), and adds a native‑Windows backend for the network bridge.
Verified end to end on a Bambu H2S: live camera, filament‑colour change, AMS active drying (with safe per‑filament default temperatures), and storage file listing all work.
You need Bambu Studio v2.7.1.57 (the latest stable) installed but not running.
The Bambu network plugin checks that its host is genuinely Bambu‑signed. On Windows the in‑process backend satisfies this by pointing the plugin's signature verification at the genuine, signed
BambuStudio.dll/bambu-studio.exefrom your Bambu Studio install. Those files are only read for the code‑signing check — Bambu Studio itself is never launched, so it simply needs to be present and closed.Note on the diff size
This is intentionally large: it's a full rebase of the fork onto OrcaSlicer 02.07, and there's no shared git history with the previous squashed base, so GitHub shows it as a whole‑tree change rather than a small delta.
Thanks for the original bridge work — this just carries it forward to the current OrcaSlicer and plugin. 🙏