Releases · SAHorowitz/MSFS2020-PilotPathRecorder

24 Aug 03:37

SAHorowitz

v1.4.1

f22df22

v1.4.1 Latest

Latest

Fixed issue with waypoints causing an exception if they have a zero altitude. This would cause the SimConnect to disconnect.
Rewrote AddWaypoint algorithm to make it much simpler and easier to understand
Added logger for general exceptions that would cause SimConnect to disconnect. This will make finding future issues easier.

Assets 3

13 Aug 02:08

SAHorowitz

v1.4.0

10472fa

v1.4.0

Added automatic connect, and reconnect, to MSFS.
Added support for multiple flight delete from list (just use shift key to multi-select)
Added support for multiple flight export from list (just use shift key to multi-select)
Fixed issue where MSFS would sometimes return garbage characters for waypoint of a flight plan. These garbage waypoints are now renamed to "Unknown Waypoint"
Fixed issue with some 3rd party planes that had characters that would cause a crash on KML export
Added ability to use an airport within 2 miles from the start of the flight and 2 miles within the end of the flight as waypoints for flights that didn't have a flight plan created.
Added support for a new option for automatic logging to only stop logging if engines were turned off.
Added ability to customize the exported KML filename with key names. These key names must be surrounded by { }. The key names are as follows:
Plane.Name - the name of plane used in flight
Loc.Start.Ident - the ident of the closest airport at the start of the flight
Loc.End.Ident - the ident of the closest airport at the end of the flight
Loc.Start.Name - the name of the closest airport at the start of the flight
Loc.End.Name - the name of the closest airport at the end of the flight
Loc.Start.City - the city of the closest airport at the start of the flight
Loc.End.City - the city of the closest airport at the end of the flight
Loc.Start.State - the state of the closest airport at the start of the flight
Loc.End.State - the state of the closest airport at the end of the flight
Flight.Start.Timestamp:timeformat - the computer date/time at the start of the flight using timeformat as the format of date/time desired
Flight.End.Timestamp:timeformat - the computer date/time at the end of the flight using timeformat as the format of date/time desired
more details about timeformat can be found at Custom date and time format stings
Also, plain text and symbols can be used in the file name as well. Just type them in outside of { }

Assets 3

11 Dec 16:46

SAHorowitz

v1.3.0

a6dda9d

v1.3.0

Added ability to automatically start and stop the recorder based on flight ground speed. This way you will never forget to log your flight.
Some more details: There is a new setting on the main page that allows you to turn on and off this feature (default is on) and also set the ground velocity to a specific value to your liking. Above that value, logging starts and below that value, it stops and the flight log is saved. You can still manually start, pause, continue, and stop logging as you did before.
Some rules about how manual and automatic logging work together. If you manually start logging then you must manually stop it. If you manually stop an automatically started log then once you go below the threshold speed and then above that speed again it will start an automatic log as a new flight. If you pause a log and then go below the threshold speed you must manually stop the log.
Rewrote the logging subsystem for simplicity and to support automatic logging

Assets 3

09 Nov 02:46

SAHorowitz

v1.2.2

b8c5346

v1.2.2

Fixed issue with FlightSampleDetails table create missing sim_on_ground column
Added database exception logging. The errors are now stored in a PilotPathRecorderLog.txt and a message is shown on the user interface if an exception occurs

Assets 3

27 Oct 00:43

SAHorowitz

v1.2.1

e81266e

v1.2.1

Added ability for the application to check for updates

Assets 3

26 Oct 03:28

SAHorowitz

v1.2.0

e729efe

Added Plane On Ground capability

Added the ability to know if your plane is on the ground or in the air. Changed yellow push-pins on Flight Path Data Points to green meaning plane is on the ground or blue meaning plane is the air. This way people can zoom in on when their plane landed or took off and look at detail easier.

Note that previous flights recorded in the database assume plane is in the air the entire flight. Only new flights recorded will distinguish whether the plane is on the ground or in the air.

Assets 3