Capture Card Flow
Latest
Hardware
Eclipse now supports a capture-card flow through OBS Projector with Pico W input forwarding. Two-PC setup: PC2 runs the game, PC1 runs OBS + Eclipse — input is shipped over Wi-Fi to the Pico W, which injects it into PC2.
Topology
PC2
Runs the game. Pico W plugged in. 1920×1080 desktop.
PC1
Runs OBS + Eclipse. Reads the OBS projector window as the visual reference.
Capture
OBS captures the HDMI feed from PC2.
Input Path
Keyboard & mouse sent over Wi-Fi to the Pico W → injected into PC2.
Why this matters
No Local Input on PC1
Eclipse no longer needs to send local input on PC1 — keep using PC1 normally while the bot runs.
Zero Software Trace on PC2
Eclipse itself leaves 0 software traces on the gaming machine.
Setup requirements
Pico W
Plugged into PC2 · provisioned on a 2.4 GHz Wi-Fi network
Network
PC1 must reach the Pico W on the same local network
How to use it — OBS + Eclipse
- Add your capture-card source in OBS on PC1.
- Right-click the source → Open Source Projector.
- Choose Windowed Projector.
- In Eclipse, select OBS Projector.
Result
Eclipse auto-resizes the projector window to 1920×1080, uses it as the visual reference, and automatically switches to the Pico W input path.
First-time Pico W setup
- Connect to the Pico setup Wi-Fi.
- Open http://192.168.4.1/.
- Enter your 2.4 GHz Wi-Fi name and password.
- On success, the Pico reboots and the setup Wi-Fi disappears.
Known Tradeoff
The current Pico W input path runs over 2.4 GHz + TCP. Packet size is trivial, but Wi-Fi latency and jitter still exist — movement can be slightly less stable than a fully custom hardware path.
Security Note
The biggest remaining visible hardware signature on PC2 is the capture card. The Pico W USB presentation is already obfuscated.
Future Hardening
Custom hardware can replace the Pico W · OBS reliance can be removed · direct HDMI passthrough can replace the projector path.