Skip to content

BamDude Bridge v0.1.0-beta.1 (pre-release)

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Aug 21:12
· 28 commits to main since this release

First build. Windows only — the BambuStudio integration it exists for was never implemented for macOS.

What it does

Registers itself as the receiver for BambuStudio's Send to Bambu Farm Manager Client, and puts the sliced plate straight into your BamDude library. The server side needed no new code: it is the library upload endpoint that was already there.

Downloads

  • …-setup.exe — installer. Start Menu entry, uninstaller, and it fetches the WebView2 runtime if the machine lacks it.
  • …-portable.zip — unpack and run. Does everything the installed build does, because registration is a button in the app rather than installer work.

The unversioned copies of each are stable links for pointing at from elsewhere.

First run

  1. Server address and an API key. The key needs the library-manage scope, and nothing else.
  2. Test connection — it checks the address, the key, and whether that key may actually add files to your library, so a green answer means the first plate will land.
  3. Register Bridge as the receiver — one administrator prompt, for the single registry key BambuStudio looks for. Autostart comes with it.
  4. Restart BambuStudio. It reads that key only at startup, so the menu entry will not appear in an already-open slicer.

Worth knowing

  • Unsigned. SmartScreen warns on first run: More info → Run anyway.
  • Closing the window hides it. The app lives in the tray; Quit there is the only real exit. Staying resident is what lets a plate reach the running instance instead of paying a cold start each time.
  • A handover stays quiet unless it fails — the slicer is in front of you, and the confirmation you want is the file appearing in your library. Failures take the window. Everything is logged to %LOCALAPPDATA%\top.bamdude.bridge\logs\bridge.log.
  • If you move a portable copy, press Register again. Registration stores the path of the executable that performed it; after a move the app stops claiming it is registered, but nothing warns you until you look.
  • ⚠️ It takes over a URL scheme that belongs to Bambu Lab's own farm client. A system has one handler per scheme. If you have that client installed, the app says so and will not displace it without an explicit tick.