Richard wrote in Tue Jan 08, 2019 4:01 pm:tdammers wrote in Tue Jan 08, 2019 3:48 pm:Someone who is more intricately familiar with the MP protocol should probably jump in and elaborate though.
Partial UDP packets can't happen however packets that don't contain the full property set are possibly, and if the aircraft is transmitting variable length strings long strings can cause a packet that is nearly full to become full and cause properties at the end to not be transmitted. There are warning messages given on the console of the transmitting aircraft that indicate this. I've not checked the packet size on the B777 - that can be viewed when flying by looking in /sim/multiplay/last-xmit-packet-len - ideally this should be no more than 900 (bytes) to allow for text chat strings.
The non tilting landing gear on the 777 doesn't seem to me from what I've read to fit the profile of a transmission problem - it is more likely a model/animation problem than an MP protocol problem.
Hmm, I'm looking at the 777 as we speak. The RH gear tilt animation is based on sim/multiplay/generic/float[2] in Models/777-200.xml, and 777-set-common.xml maps that to /gear/gear[2]/compression-m. So that looks alright to me.
I'm also looking at two 777's (running on two of my computers) as we speak, going through mpserver01. This is what I see:

The Air France one in the foreground is running locally on the machine where the screenshot was taken, the BA one in the background runs on the other machine, callsign NL255. As you can see, the gear looks fine on both, no tilting.
**HOWEVER**
These are both the model taken directly from https://gitlab.com/fg777_seattle/fg777_seattle.git. There are other 777's making rounds, including the one in the default hangar, which I believe is an older version of this model. The model ID they send may very well be the same, but it's possible that those don't send that particular property yet. If that is the case, then the proper solution would be to use the gitlab version, or, even better, merge that into the default hangar. It's either that, or a protocol issue after all (but then again, it works fine between these two machines...)
(On a side note, parking 777's at EDLN is hilariously ridiculous... just imagine trying to taxi past one another on those taxiways...)
**EDIT:**
I just checked the 777 from fgaddon; it has the same MP property assignments, as you can see here: https://sourceforge.net/p/flightgear/fgaddon/721/tree/trunk/Aircraft/777/777-set-common.xml#l515, and the animation here: https://sourceforge.net/p/flightgear/fgaddon/721/tree/trunk/Aircraft/777/Models/777-200.xml#l1872. So that's not it.