A packet is sent between FlightGear and the multiplayer server.
V1 packet is "Visible to All"
V2 packet is "Visible to only 2017+"
jomo wrote in Wed Jul 17, 2019 11:35 am:* and why in the MPsettings there is the option "Visible to only 2017+" or "Visible to all"
For backwards compatibility with pre 2017.1 FlightGear.
To be clear it is to allow someone running 2016.4 (or before) to see all of *the animations* (gear, elevators, etc.) from someone running 2017.1 or later.
jomo wrote in Wed Jul 17, 2019 11:35 am:* and why I (the filming ATC) never yet had a problem with guests coming with whatever model and or setting: If they switch to "Visble to All" everything works fine without changing anything on OR and/or ORCAM.
Because OpenRadar doesn't correctly support V2 packets; so when your pilots switch to V1 (Visible to all) packets OpenRadar will forward these packets correctly.
The way that ORCAM works (according to the documentation) is to use the OpenRadar MP relay to send packets from OpenRadar to ORCAM.
jomo wrote in Wed Jul 17, 2019 11:35 am:* Could it be that this MPsetting has something to do with that V1/V2? Maybe that V1/V2 is supposed to try reducing the traffic via the MP-servers?
V2 is to reduce the network traffic and to allow many more properties to be sent (in a smaller amount of space). That's the reason for V2.
jomo wrote in Wed Jul 17, 2019 11:35 am:Based on the f-14 incident I checked my local Model-Library and found an older version of the f-14b (June 8 2017) than the one now in the FGFS-Library (Oct 2018) and maybe there are even newer
The problem you saw with the F-14 model is 100% not caused by incompatible models. I can be sure because it is my model and I understand it completely.
It is possible that a new model will not show - but unlikely as generally the model names don't change. More likely is that animations will not work correctly between model versions. Most aircraft developers should be aware that changing MP property usage can break older versions - but sometimes it is impossible to avoid.
jomo wrote in Wed Jul 17, 2019 11:35 am:Can anybody help me by explaining:
* What is V1/V2, where is it and what is it for ? (Reduce MP-traffic?)
V1 packet is "Visible to All"
V2 packet is "Visible to only 2017+"
V2 is to reduce the network traffic and to allow many more properties to be sent (in a smaller amount of space). That's the reason for V2.
jomo wrote in Wed Jul 17, 2019 11:35 am:* Are we still allowed to fly OLD models from many years ago ? (I see them weekly at EDDF!)
Yes; models are not affected by this change if you are using FlightGear 2017.1 or later then it will handle both V1 and V2 automatically.
jomo wrote in Wed Jul 17, 2019 11:35 am:* Can we tell everybody participating in any event that he should set MP to "Visible to All"! (As I do it now as ATC)
That is what you will have to do until OpenRadar is fixed; or you use the alternative way to connect ORCAM to the normal flightgear multiplayer server instead of the OpenRadar MP relay.
jomo wrote in Wed Jul 17, 2019 11:35 am:* I am sure OR-designers cannot help us there - because as stated above in the first lines: "ORCAM is only an aircraft running a normal FG session .." --> i.e. you always have the VIEW functions as from any other FGFS-model! You do not need OR for that!
I am 100% totally sure that it is only the OpenRadar developers who can fix this problem - because OpenRadar is acting as a MP relay.
What this means is that OpenRadar receives the multiplayer packets from the main FlightGear multiplayer servers (e.g. mpserver01.flightgear.org) and then it sends these packets out on port 5010 to the ORCAM FlightGeear instances. The ORCAM FlightGear instance is not connected to the normal multiplayer servers but instead ORCAM is connected to OpenRadar.
jomo wrote in Wed Jul 17, 2019 11:35 am:* Would it matter if events (without OpenRadar) will continue to have that problem between all participants themselves?
Providing that those participating in events are running 2017.1 or later there will not be a problem; only pilots running old FlightGear (before 2017.1) will be unable to see animations.