Skip to content

Releases: MordantArc/vatsimFPL

Alpha 2.1

29 Oct 02:58
b4e1919
Compare
Choose a tag to compare
Alpha 2.1 Pre-release
Pre-release

Minor Update

  • Improved logs for debugging
  • Added weight category to the GUI(also adds "Super" A380s, however not "Heavy" to others[yet])
  • Mainly improving the shell for future processes such as SimConnect, etc

Full Changelog: v0.0.2-Alpha2.0...v0.0.2.1-Alpha2.1

Alpha 2.0

28 Oct 03:22
a58841f
Compare
Choose a tag to compare
Alpha 2.0 Pre-release
Pre-release

Super excited as this is the first release with what I would consider to be vaguely usable code. I will test it with my own Vatsim flights to see what I should change, and what's broken and such. Feedback is appreciated!

Here is the full list of supported functions:

  • Continuously updating FP(flight plan) info for the following fields(Note: due to the refresh time of the API itself, these values update every 20s. Not "real time" data, but fairly accurate):
    • Altitude
    • Airspeed
    • Callsign
    • Assigned Squawk Code
    • Departure Airport Code
    • Arrival Airport Code
    • Alternate Airport Code
  • Logging updates and changes to FP
  • Base for .csv data recording(SimConnect data from MSFS)
    • Auto create .csv
    • Thats about it, however implementation of data will now be really easy with Simconnect. Means it gets to you sooner!

Future Roadmap:

Soon-ish(within a month or so):

  • Image representation of major aircraft types, such as:
    • C172/182
    • 737
    • A320/A321/A319
    • 747
    • C414
    • B58
    • SR22
    • CRJ7
  • Real time Route updating

Future(within 1-2 months):

  • Update the look, spruce up the look of the gui - see lower for GUI plans

Far far future(unknown time into the future):

  • Weather API for departure and arrival airports, possibly a midpoint for enroute weather

Much ado about the GUI...

The current GUI looks unbelievably bad and already has inop commands such as .clear() that hinder it's abilities. However, it is still easier to use(in my eyes, at least) than an alternative(probably TKinter). And that's not to say TKinter is bad, but it doesn't look too spectacular either and doesn't have as many graphical abilities outside of buttons and labels.

With that in mind, here's the plan:
There will be two branches, a main branch with TKinter or another GUI and one that is the same with CS CMU. This will allow a functional product to be available sooner(next month or two) in the CS CMU branch and then that will be translated to another GUI for the main branch at that time. If you want a simpler and easier to use GUI, sorry but you'll have to wait. All in due time :)

Future Updates

With the GUI in mind, the plan is a handful of minor Alpha pushes(ie: A3.1, A3.2) with (possibly) only one more major Alpha push(A4) and then hit the Beta 1. B1 should be sometime in the next 2 months.

Thank you!

Thank you so much for checking this out!

Full Changelog: v0.0.1.4-Alpha1.4...v0.0.2-Alpha2.0

Alpha 1.4

26 Oct 04:49
6b5d30f
Compare
Choose a tag to compare
Alpha 1.4 Pre-release
Pre-release

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.

Alpha 1.3

26 Oct 01:28
f2628bc
Compare
Choose a tag to compare
Alpha 1.3 Pre-release
Pre-release

Added logs.

  • Date, time, and details
  • Note: Only marks app start at the moment. Will add more soon.

Same roadmap as last time.

Alpha 1.2 - Minor Update

25 Oct 17:38
6994ca0
Compare
Choose a tag to compare
Pre-release

Minor fixes to comments and labeling in the gui

Alpha 1.1

22 Oct 07:16
dc9bb61
Compare
Choose a tag to compare
Alpha 1.1 Pre-release
Pre-release

Added Routing.

Note: There is no functionality for updating the route. This will be changed soon. It will remain static o the route loaded on startup.

Alpha 1.0

22 Oct 05:47
307ed36
Compare
Choose a tag to compare
Alpha 1.0 Pre-release
Pre-release

Hello!

This is the first iteration of the vatsimFPL!

It is very barebones, and I will certainly be updating this. Here is the current mini-roadmap for this program:

Very soon(within the week):

  • Add routing to the main section

Soon(within 2 weeks):

  • Add icons for popular aircraft
  • Add label for aircraft with their weight restrictions

Future(within 1-2 months):

  • Update the look, spruce up the look of the gui(up to and including redoing the gui)

Far far future(unknown time into the future):

  • Weather API for departure and arrival airports, possibly a midpoint for enroute weather