Update the garbage driver device protocol

[okawo80085]

Is your feature request related to a problem? Please describe. The protocol our driver uses to communicate device tracking and inputs is garbage. It feels like two different unfinished protocols thrown together, because it is. It's awful and i hate it.

The main issues with the current protocol is:

• inefficient packet structure
• lack of two way communication in the tracking protocol
• its inconsistent af
• socket code in the driver can be improved, like a lot

Describe the solution you'd like We need to go over all the protocols used in the driver currently, throw them in the garbage, and come up with replacements that are:

• consistent
• efficient, i.e. make packets as small as possible
• doesn't make me want to kms

Additional context This has been an issue for a while, posers can't tell if the driver ignores them unless they try to actually sync their device lists, and a lot of other terribleness. Time to finally fix it!

[okawo80085]

I should've clarified what i meant by this issue xD

So our current tracking protocol requires device list synchronization, our manager protocol has sync commands exactly for that, however this synchronization is not persistent and the driver will reset to the device list from settings AND when our driver connects to the poser it does not communicate it's current device list in any way AND if the device lists don't match the driver will just ignore the poser's tracking, while the poser has no way to tell the device lists are not synced, let alone if its ignored or not.

Thats the current problem, well the biggest one at least...

[okawo80085]

This is mostly fixed in the new driver version, i'll close this as soon as the new driver version is merged into master.