Add kill command, fix Ctrl-C teardown, speed up 2nd instance startup

[bl2-split] / README.md

diff --git a/README.md b/README.md
index 2ce0f741e99973db8626c1348bce0c570f178a38..bf009c772380cfb79981d9897b11b1429baae718 100644 (file)
--- a/README.md
+++ b/README.md
@@ -61,7 +61,8 @@ their own controller, save, and screen. Tested on **Arch + KDE Plasma 6 (Wayland
 | `./bl2-splitscreen.sh setup` | fetch Goldberg + build `p1/`, `p2/` |
 | `./bl2-splitscreen.sh run`   | launch both instances + place windows |
 | `./bl2-splitscreen.sh tile`  | re-place the two windows |
-| `./bl2-splitscreen.sh clean` | remove `p1/`, `p2/` (copies + saves + prefixes) |
+| `./bl2-splitscreen.sh kill`  | terminate all running Borderlands 2 instances |
+| `./bl2-splitscreen.sh clean` | kill instances, then remove `p1/`, `p2/` (copies + saves + prefixes) |
 
 Useful env overrides: `MODE=native|proton`, `DISPLAY_MODE=dual|split`,
 `ISOLATION=bwrap|sdl`, `SPLASH_WAIT=<secs>`, `STAGGER=<secs>`.
@@ -117,6 +118,12 @@ So another person clones the repo, forces Proton on their own BL2 in Steam, runs
   `rm p{1,2}/game/Binaries/Win32/steam_settings/configs.main.ini`
 - **They don't see each other on LAN:** Player 1 hosts first (the script staggers
   launches). Discovery uses `custom_broadcasts.txt` (localhost).
+- **The 2nd instance takes ages to reach the menu:** the two share a DXVK shader
+  cache (`dxvk-cache/`) so the 2nd reuses the 1st's shaders; the first-ever run
+  still compiles them. If it's still slow, raise the gap between launches so the 1st
+  is fully loaded before the 2nd starts: `STAGGER=45 ./bl2-splitscreen.sh run`.
+- **Ctrl-C / kill left something running:** `./bl2-splitscreen.sh kill` tears down
+  the whole game + Proton/Wine tree.
 - **A window won't sit on its monitor:** re-run `./bl2-splitscreen.sh tile`; raise
   `SPLASH_WAIT` if it fires before the game settles.
 - **Reset everything:** `./bl2-splitscreen.sh clean` (removes copies + saves; the