Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

1.3.22 bug report -- position not updated before 1st flight plan sent


Robert Shearman Jr
 Share

Recommended Posts

Robert Shearman Jr
Posted
Posted

Hi Justin --

Mike Cinnante and a group of us from the Virtual USA Flying Club found a bug in 1.3.22 which is very, very specific, but also very, very reproducable, and results in the user's position not being sent across the network.

Step #1: have a fresh, clean install of xPilot 1.3.22.  You can configure CSLs, Server settings, and Audio settings, and reload X-Plane and xPilot accordingly.  DO NOT SEND A FLIGHTPLAN TO VATSIM.

Step #2: spawn at a US airport that is NOT one with a common, four-letter ICAO.  We used MT86 (Bar E Airport, Montana) and W42 (Fallston, Maryland) for several rounds of testing.

Step #3: have a friend spawn at that same airport.

Step #4: begin taxiing around.  Your friend will observe that you are NOT moving.

Step #5: file a flightplan.

Step #6: disconnect from VATSIM and immediately reconnect to VATSIM.  Your friend will observe that you have re-spawned in your updated position.

Step #7: begin taxiing around again.  Your friend will observe that you are now moving.

In one test, the two users moved to LAX and taxid around, and observed movement, before filing a flightplan, and this ALSO solved the issue.  This led them to believe that it only affected smaller airports whose positions might not be in the VATSIM database.  I think this may be a red herring because it was also purported to have happened at Molokai (PHMK).  Our guess is that it has to do with one of the .json files not having a variable initialized properly until a flightplan is sent.  Note also that we WERE NOT able to reproduce this using someone who HAD successfully sent a flightplan, even when they deleted AppData/Local/xPilot/AppConfig.json -- but we WERE able to reproduce it if that person deleted that ENTIRE folder as well as X-Plane/Resources/plugins/xPIlot and did another fresh reinstall of 1.3.22.

I know that's a convoluted one, but, given its reproducability we figured it would be something you should be able to track down.  Hope it helps!

Cheers,
-R.

fvJfs7z.png

Link to comment
Share on other sites

 Share