wkitty42 wrote in Thu May 31, 2018 3:31 pm:the MP protocol was modified back in 2017... then a few updates were made to it to fix a couple of problems...
speaking of those problems, it almost sounds like the one where the one craft with multiple noses was being displayed with no nose... this was because they were not defaulting that property to false... since the property was not being sent to the remote, it was defaulting to false over there and they were not seeing the nose at all... once the craft was fixed, the nose reappeared and things have been fine ever since... so where's this going? it is possible that the logic in your craft is backwards for your landing gear and livery selection stuff... i dunno...
The aircraft in question is the DHC-6; defaulting the nose to "false" doesn't fix the underlying problem, the property is still not being sent, the model now just deals with it in a less disruptive way. Instead of "oh dear, there's no nose property, so let's not select any nose at all", it now goes "oh dear, there's no nose property, so let's select the long nose, wild guess".
And because of this, the same approach won't work for landing gear, because if the "gear down" property isn't transmitted, then you can only default to "gear always down" or "gear always up"; neither will be helpful.
wkitty42 wrote in Thu May 31, 2018 3:31 pm:the MP protocol was modified back in 2017... then a few updates were made to it to fix a couple of problems...
remember, the MP protocol has fixed sized packets it sends... if a craft tries to send to much, the packets will be truncated... that could easily lead to problems like this...
Well, the new v2 protocol will actually chop up a property tree update into multiple packets if it doesn't fit into one; and older (v1-only) clients will still receive and process the first of those, just not the subsequent ones. And unfortunately, authors have very limited control (bordering on useless) over the order in which they are packed, so you can't even say "OK, these 16 properties here are essential and must go into the first packet, everything after that is eye candy and may be ignore by v1 clients", and then stuff things like surface positions, cockpit / cabin lights, doors, etc., into those "less important" props, and landing gear and such into the "important ones".