ske087/Bambu_lab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: upgrade StudioBridge v2.1.2 -> v2.1.3, add persistent-folder creation, update runbook

Browse Source 
- Rebuild StudioBridge-2.1.3.jar from latest upstream (v2.1.3) and deploy to portable-dist
- Add ensurePersistentDirectories() so the app creates ~/.studio-bridge and Profiles at startup (GUI + --sendonly)
- Bundle full StudioBridge source under StudioBridge-src/ (with rebuild-jar.bat)
- Update launchers (Launch-StudioBridge.bat, portable-dist/StudioBridge.bat) to v2.1.3
- Add check-update.ps1 and UPDATE.md for the step-by-step update runbook
- Update README (v2.1.3, persistent data + updating sections)
- Ignore StudioBridge-src/target/ build output
This commit is contained in:
ske087
2026-08-06 20:05:21 +03:00
parent 42293e0d5a
commit a50dd3b34b
52 changed files with 5875 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+28 -4
View File
@@ -1,6 +1,6 @@
# StudioBridge
> **This portable distribution bundles StudioBridge v2.1.2** — the latest release from [Rdiger-36/StudioBridge](https://github.com/Rdiger-36/StudioBridge).
> **This portable distribution bundles StudioBridge v2.1.3** — the latest release from [Rdiger-36/StudioBridge](https://github.com/Rdiger-36/StudioBridge).
With StudioBridge it is possible to make Bambu Lab 3D Printers visible in Bambu Studio or Orca Slicer, that cannot be automatically added by them.
It is also possible to connect printers from other subnets or from accessible external networks (e.g. via VPN) or in your normal home network.
@@ -18,12 +18,36 @@ You have the option to send the package via broadcast or directly to Bambu Studi
You can check if the printer would connect correctly in Bambu Studio with the function **"Check Printer"**.
# Persistent data
On its very first start the app creates its own persistent data folder, so that everything you
save is remembered the next time you run it:
- **Data directory:** `~/.studio-bridge/` — created automatically at startup.
- **Settings:** `~/.studio-bridge/settings` — remembers your theme, profile directory,
"remember last used profile" and direct-mode options.
- **Profiles:** `~/.studio-bridge/Profiles/*.sbp` — one file per printer profile
(printer name, IP address, serial number, model). Once you have saved a printer there,
it is loaded again on the next start, both in the GUI and with `--sendonly`.
> **Note:** On Windows this is usually `C:\Users\<YourName>\.studio-bridge\`. If you used a
> version older than 2.1.x, the app migrates your old `~/StudioBridge` data directory into the
> new one automatically on startup.
# Updating StudioBridge
To check whether a newer release exists and to update/rebuild the complete bundle, see
**[UPDATE.md](UPDATE.md)** — a step-by-step runbook for an AI agent or a manual update.
Quick check for updates:
```powershell
.\check-update.ps1
```
Successfully tested on:
- Windows 10/11 ARM and x86
- Linux Ubuntu 25.10 ARM and x86
- MacOS Intel and M-Series
# Supported Printers (v2.1.2)
# Supported Printers (v2.1.3)
| Display Name | Model Code |
|---|---|
| A1 | N2S |
@@ -90,8 +114,8 @@ StudioBridge.jar is built in Java, so a Java Runtime Environment (JRE) is requir
2. Verify with `java -version`.
**Running the GUI:**
2. Download `StudioBridge-2.1.2.jar` from the [GitHub releases page](https://github.com/Rdiger-36/StudioBridge/releases/tag/v.2.1.2).
2. Double-click the `.jar` to launch, or run: `java -jar StudioBridge-2.1.2.jar`
2. Download `StudioBridge-2.1.3.jar` from the [GitHub releases page](https://github.com/Rdiger-36/StudioBridge/releases/tag/v.2.1.3).
2. Double-click the `.jar` to launch, or run: `java -jar StudioBridge-2.1.3.jar`
# FAQ