• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

FSTramp for V2.2 Question

falcon409

Moderator
Staff member
I have found a problem that seems to have come out of nowhere. I have not flown 2.2 for quite awhile as I added 1.4 and it affords me the chance to still fly many of the airplanes I enjoyed in FSX. . . .ones that no longer are functional in 2.2. Anyway, after finding that Orbx has a triple Installer available I installed my limited Orbx stock into V2.2 and went flying. When I opened FSTramp to follow the flight I discovered that if I held the cursor over a second airport to get a heading and ETA it would give me erroneous information. I can draw a line to the airport and as a for instance. . .it would then tell me the airport was 20nm away at a heading of 026, which is correct. . . .however if I just hover the cursor over that same airport it would tell me it was 6628nm away at a heading of 334 degrees. This is something it has never done before and even after uninstalling the original installation (along with all the hidden files scattered about the drive) then reinstalling the latest version, registering it and then loading it back into V2.2, the problem remains and I have no idea why, or what caused it to start happening.
 
Back
Top