tdammers wrote in Mon Jun 04, 2018 4:47 pm:Well, the new v2 protocol will actually chop up a property tree update into multiple packets if it doesn't fit
The 2017.2 protocol doesn't do that. If the properties don't fit into a packet a message is output onto the console and properties aren't sent. This can happen when the packet is nearly full and text chat is used (as text is variably sized). There is a property /sim/multiplay/last-xmit-packet-len that tells you the size of the last packet transmitted. This is useful information for developers, but also for the pilot whose model isn't appearing correctly.
There may be other problems with the V2 protocol that are lingering in there - it was a hard thing to develop and I spent a lot of time validating that it was right; however it is complicated and things could be missed.
All I need is a bug report saying what the two versions of FG are; the affected model, and where to get the model from if it isn't from FGAddon.
Any version of FG should be able to receive packets from any other equal or earlier version, regardless of what is sent. The reverse isn't true and earlier FG will only be able to send packets to newer FG, so any incoming data will be reduced to basic position information. Models should always be visible and in the right place. This part of the protocol is unchanged.
Also worth remembering that we had MP problems long before I changed the protocol; so there could be other factors at play.