Since landing spot has became key attribute for T&W mission, I would like to share the behavior of deviation between Simfly and Volanta (because both uses Mapbox so it should be the same).
Currently, the touchdown point between Simfly and Volanta is different, so that means, if we land on one spot, it will appear as different spot on Simfly, resulting in T&W imprecision.
I point Volanta as reference because if you look at the link of landing clip, you will see that the spot of touchdown is almost the same (Sim + Volanta), while it is pretty much different in Simfly. In other missions, this is very ok, but I think T&W may result in unpleasant situation.
I really cannot make a landing before the aiming in order to appear nicely on Simfly. I land as what I’ve seen on screen. The sample flight is on XPlane 12, but I notice the same on MS2020 as well.
What version of Mapbox is Simfly currently on? Wonder is it from the version different or something.
How to get rid of the deviation between the SIM and Simfly’s map?
(As I mention, I have no issue with other missions at all, but the mission like T&W that requires some precision, it will be even more difficult.)
Best Regards.
1 Like
I suppose we would need a “third” acars in order to have a 2 out of 3 results.. I am signed to FSHub, but there’s also a landing monitor on MSFS called toucdownFX, or Landing Monitor and Flare Analysis XP12.
1 Like
Hi Metrocat,
thanks again for reporting this. First, if you can, please send us the data/files from this same flight from both SimFly and Volanta. For SimFly, the Flight ID is enough.
With these data, we’ll check both the visual position of the touchdown marker on the map and, most importantly, the actual touchdown coordinates recorded by the two systems.
As Antonio suggested, for a truly reliable and complete comparison, we need three independent systems. With only SimFly and Volanta we can confirm that there is a difference, but a third ACARS would give us an additional reference and help us understand much better where that difference comes from.
So, when you can, it would be important to make another flight while recording it simultaneously with:
-
SimFly
-
Volanta
-
A third ACARS
Then we’ll compare the coordinates, marker positions, satellite imagery, georeferencing, and any possible differences in Mapbox versions/configuration or the mapping services being used.
For now, please send us the SimFly + Volanta data from this flight so we can already start checking it.
Thanks
Hi. Below please find Simfly’s flight ID and Volanta:
Simfly: 01a096f1-6d6c-75c8-a2dc-566bd9203279
Volanta: Volanta
I would like to clarify first, that I do concentrate on Simfly’s ACARS more on this case. It isn’t the FPM/GForce, it is the mismatch between Simfly map vs. the simulator itself. I gave Volanta in context because both Simfly & Volanta uses map box, which I understand that it should be very same on map.
Please kindly look at the log above, may you find something. In my opinion, we should test on the very same airport for XP, MS20 and MS24 and see the result again. I have only XP & 2020, I can also send some with MS20 if you need it in the future.
