Until OpenRadar and ATC-Pie are updated to use the new multiplayer protocol, Flightgear pilots running 2017.2.+ need to ensure they set the "visible to all" option in the multiplayer settings dialog. ATC-Pie is in progress, I don't know about OpenRadar.
The online map seems to work OK with the new protocol.
Where should I find old vertion of OpenRadar?
Something is obviously going on on the servers' side tonight. Same symptom for ATC-pie, none of its history commits see anybody either, and by tracing received UDP packets I figured I was not getting any traffic from the servers at all (I tried 01 and 13).
Looks like servers got updated to version 0.13.0. I have a FGMS server still running 0.12.0 (used for OPRF events, 750nm range) - if the maintainers of atcpie or openradar need access, PM me and I'll shoot you the IP address.
edit: looks like mpserver51.flightgear.org is still on version 0.12.0 as well.
I just tried OpenRadar and I don't see contacts.
2017-06-14 10:10:53,699 [AWT-EventQueue-0] [[ INFO] MetarReader [AWT-EventQueue-0]] - Metar for EGNM processed.
2017-06-14 10:10:53,970 [AWT-EventQueue-0] [[ INFO] SoundManager [AWT-EventQueue-0]] - SoundManager initialized!
I was seeing contacts on Monday with this version of OpenRadar.
Last edited by sanhozay on Wed Jun 14, 2017 9:15 am, edited 1 time in total.
Last edited by PavlinS on Wed Jun 14, 2017 8:20 pm, edited 1 time in total.
This seems to be server, not client related. Tested with ATC-Pie.
I was though it is. Eny proposition for a fix?
sanhozay wrote in Tue Jun 13, 2017 8:54 pm: Make sure your aircraft is using the old multiplayer protocol. It's on the Multiplayer menu in Flightgear. You want the "visible to all" option.
If you don't see that option, that's not the problem.
The multiplayer packet is in two parts; the first part contains all of the position information - this isn't affected by the 2017.2 changes. This is why MP map still works.
The compatibility affects the second part of the packet that contains the rest of the properties - some are important (such as transponder); but the rest are often used only for animations.
Ideally all clients would be updated to be able to process the new packet format.
I only tested OpenRadar very briefly on Monday and I made the suggestion thinking that during my tests contacts were disappearing. Now I think about it, I was mistaken. The contact wasn't disappearing but it was losing some values when I switched the aircraft to the v2 protocol. Unfortunately I can't see any contacts today to confirm the values it was losing. I think it was squawk code and altitude, but I could be wrong. All I can say with any certainty is that it was not working correctly and it merits some testing.
All multiplayer does not work, not just the OpenRadar. I asume that from now's my flight. I was meet 4 people during flying the distance I do now, but no one is showed up on the pilot list. I roll back my Flightgear to the 2016 4.4 vertion .The problem persists.
It is a bad idea to post your IP address in a public forum.