Alpha 1.4

Updated logs to use txt instead of JSON.

Have to admit, it was entirely because I didn't want to deal with the JSONs. I spent 4 hours and still couldnt figure it all out for some reason, so I'm just going to use .txt as it works just as well(albeit a little less organized).

Fortunately, a good part of this is that it shows that the route is updating, however the CS CMU lib is deciding that .clear() is not going to work. I have verified that this function is borked in their web-based IDE as well, so It probably isn't going to work any time soon.

Things to be added to roadmap(see Alpha 1.0 Release notes for roadmap):

• csv? xml? any spreadsheet for data recording? If I can understand JSON I'll start recording and exporting files with info at certain times, essentially acting as a pseudo ADSB/GPS recorder, just for recorded points.

SimConnect Plans

So I found out SimConnect exists(a direct link to MSFS where you can grab in-game data such as altitude, airspeed, etc), and I plan to use it for data logging. There are functions where I could set autopilot settings to flight plan params, but I don't think that would be really practical. So the plan currently is only data logging and visualization of flight params in relation to the flight plan.