Closed NikolaiVChr closed 4 years ago
First thing: this is because I was doing some testing with the MP protocol, the issue should not occur for anyone else. The properties should not be nil of course, I am using a recent git version indeed, is there some known issue with that?
Well RAF1 has same issue and he also uses next.
I think there is bug in next, MP protocol 2.
Just to check, you mean that the problem exists between two persons who are not me?
When I look at RAF1's properties over MP his properties are mostly nil also.
That might be a core issue indeed, I will search if I can find something in flightgear source code.
Nevermind he uses 2019.1.1, hmm maybe I am wrong, I will do some tests of next.
I did some tests. This is an incompatibility between 2019.2 and 2019.1 in the MP protocol (precisely generic bool properties from 2019.2 are not received by 2019.1, everything else seems to work), nothing Viggen specific.
oh, maybe alert Richard to the issue then, he is the one who did all the bools.
I don't think the problem is with the Viggen. It might be due to people flying with FG git next. Look at these properties, almost all were nil (recorded from 2019.1.2):