No NatNetClient in MinGW...got it...depacket then...few questions?

[lehthanis]

I'm looking at the PacketClient.cpp example, and I'm wondering if the whole sPacket structure is required for just sending commands to Motive? I don't need to extract any data from the stream, I just need to be able to send a few commands to manage it's state. What's the absolute bare minimum I'd need to accomplish just basic commands using UDP without the NatNetLib?

[lehthanis]

It took quite a bit of effort from my team, but we've finally managed to reverse engineer the PacketClient method of sending commands without using the NatNetLib. We're actually sending the packets via Qt's QudpSocket->WriteDatagram function. This is cross-platform capable.

[failurecounter]

I'm looking at the PacketClient.cpp example, and I'm wondering if the whole sPacket structure is required for just sending commands to Motive? I don't need to extract any data from the stream, I just need to be able to send a few commands to manage it's state. What's the absolute bare minimum I'd need to accomplish just basic commands using UDP without the NatNetLib?

No, the full sPacket structure isn't required if you're only sending commands. For basic control (like ping, connect, start/stop), you just need to send a properly formatted command packet via UDP to Motive's command port (default 1510). Just create a simple buffer with the correct message ID (e.g. NAT_PING, NAT_START, etc.) and send it—no need for full NatNetLib or data parsing.