The problem is we don't have control over a P3D/FSX/MSFS model set. Our loose relationship with FLAi was the closest we have gotten to having some sort of influence over a model set for those platforms, but FLAi ended up going bust.
This is in stark contrast to how we handle X-Plane. Right now, we are fully in control of the X-Plane model set.
If you have any suggestions on how we can get our hands on a model set for P3D/FSX/MSFS, then your wish is my command and we can ensure commonality between the sets.
Until then ?
So, the only difference between our X-Plane library/client and IVAO is the fact you can choose a variant?
If this is the case, then you will be happy to know our API supports it, but we haven't implemented it yet.
Have you guys tried our X-Plane library? Wondering if the technique we used with that library would be better suited for other simulator platforms in the future?
First a point of clarification, because it is to me very confusing. When you refer to "sectors" you should be using the terms "legs" or "flight segments"
Anyway, when you connected to the network, in the connection window where it asks you to specify your ADS-B callsign - did you change this between flights, or leave it the same for both?
While some of the steps to this procedure can still apply to help fixes, it is not entirely important anymore and thus I am going to unpin and unfeature.