You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending DCSBIOS_ADD_EXPORT_TARGET <IP> <PORT> to the import stream, DCS-BIOS should start sending a copy of the export stream to the given IP address and port.
DCSBIOS_REMOVE_EXPORT_TARGET <IP> <PORT> should remove it.
This feature would enable software running on another device on the network to connect to DCS-BIOS without requiring the user to configure anything on the DCS computer. It would also work if the other device has a dynamic IP address (as opposed to the current mechanism of editing BIOSConfig.lua).
The text was updated successfully, but these errors were encountered:
…T commands"
This reverts commit ae772c9.
While trying to implement this on the client side it became
apparent that this changeset was not fully thought through.
There is no way to reliably stop exporting to the additional
target IP/Port once that client has been closed. Doing so
would require implementing a keep-alive mechanism.
We have TCP support now, which mostly solves the same problem
in a simpler way (with the disadvantage of a very small
performance penalty).
Additional UDP targets can still be used by statically configuring
them in BIOSConfig.lua.
Closes#6.
When sending
DCSBIOS_ADD_EXPORT_TARGET <IP> <PORT>
to the import stream, DCS-BIOS should start sending a copy of the export stream to the given IP address and port.DCSBIOS_REMOVE_EXPORT_TARGET <IP> <PORT>
should remove it.This feature would enable software running on another device on the network to connect to DCS-BIOS without requiring the user to configure anything on the DCS computer. It would also work if the other device has a dynamic IP address (as opposed to the current mechanism of editing
BIOSConfig.lua
).The text was updated successfully, but these errors were encountered: