Closed prolix-oc closed 1 year ago
The websocket listens on 0.0.0.0 which should bind to all interfaces, but apparently windows doesn't do that. Try this build and set the ip in the settings dialog, then restart obs https://github.com/univrsal/input-overlay/actions/runs/6431140462
That seems to have done the trick. I was initially worried nothing would happen when I saw that it still showed the link-local address under the settings, but I just tested the connection from my main PC to the encoding PC and it works.
Thanks for the super quick fix, have a great morning!
Describe the bug On a desktop PC with multiple ethernet interfaces, this program will bind to the first NIC even if it is unused. For example, on my X99 Taichi there is both an Intel I211 and Intel I218-V NIC present, but input-overlay will attempt to bind its websocket server to the I218-V interface since it is technically NIC 0.
To Reproduce Steps to reproduce the behavior:
Expected behavior input-overlay should bind to the interface that OBS binds to.
Screenshots
I believe it's self-explanatory enough.
Additional information:
Additional context None needed, slightly frustrating that I'd now have to disable an interface that belongs to NewTek NDI Receiver in order to use this program, since the bindings are all wrong.