I'm using my own UDP solution to connect an external control system to my game and it all works really well. (it's very simple, the control system sends a constant stream of values and I translate them back into usable signals to move or rotate transforms via System.Net.Sockets.UdpClient)
Now I'm using TNet to make this multiplayer. The idea is that it's a normal networking situation, all handled via TNet, only one specific player will get the UDP signals from the control system and will then delegate the actual scene-changes to the rest of the players - again via TNet. (let's say the control system connects to 192.168.0.235:8000 and TNet connects to 192.168.0.235:5127)
But for some reason the two don't work at the same time?
If I disable the TNet part the control system works, if I enable TNet all the TNet-stuff works, but the control system doesn't receive any signals.
How can I fix this? Is TNet catching all signals?
Okay. User error. Got it to work! *doh*
But now I'm wondering: Would it be possible to rewrite my solution using TNet?
Is there a way to use TNet to simply listen to a specific UDP port and look-at/use all incoming messages? (A typical message would look something like this: "pos|0|1|2#rot|0|180|0")
Thank you very much for your help!