• Welcome to the AirSource Forums!
  • This space intentionally filled with airspace..
  • FL290-FL410 Track 000 to 179° – odd thousands
  • FL290-FL410 Track 180 to 359° – even thousands
  • Confess, Conserve, Climb, Communicate, and Comply
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Title: Question On The Recording Capabilities of MyAAS
Threaded Mode
#1
So, I’m looking through my logbook and clicking flight details on the crew pass. I notice at the bottom of the report there are some of the flight stats including average speed and landing rate. So I’m just curious, what other FS parameters, specific to MSFS can the program capture?

The way I’m headed with this thought process is recording additional parameters, particularly takeoff and landing data, I.e., takeoff flaps, ias speed, N1, landing ias speed, flaps, stopping distance.

And yes, I read the FAQ and no, I don’t want MyAAS to be the end all be all of ACARS programs. :lol: :lol: :lol:

Just wondering, for now, it’s data recording capabilities. LOL!

Thanks.

 
Reply
#2
Hey Ken,

Yeah, the wording on that could have been better but, it works.

As for what myAAS captures, it really only captures what we need for flight information. There is quite a bit that is caught but not presented as it's used for background tasks. Also, things like landing rate and speed are recorded and sent with the flight report. Where they are used, I couldn't really tell you (Landing Rate can be seen if you click the 'Details' link at the top of the Flight Report in your logbook)

Another thing we need to take into consideration is the variety of aircraft that can be flown here. Some data might not be applicable to some where it is others. I'm not sure it is still a thing but I remember helicopters being in the topic (I could be wrong on that one though).

Memory management concerns also played a part with what we catch. There was a feature that, basically, recorded the flight track and displayed it on a version of Google maps but, when ActiveX controls(?) became taboo, so did that feature.

To answer your question, theoretically, we could catch pretty much anything that we want. If you are really that curious, you can go to https://www.fsuipc.com/. Scroll down to 'Additional Free Software' and download the FSUIPC SDK. Have a look at FSUIPC for Programmers.pdf.

 
Reply
#3
AS201 Joe Wrote:Hey Ken,

Yeah, the wording on that could have been better but, it works.

As for what myAAS captures, it really only captures what we need for flight information. There is quite a bit that is caught but not presented as it's used for background tasks. Also, things like landing rate and speed are recorded and sent with the flight report. Where they are used, I couldn't really tell you (Landing Rate can be seen if you click the 'Details' link at the top of the Flight Report in your logbook)

Another thing we need to take into consideration is the variety of aircraft that can be flown here. Some data might not be applicable to some where it is others. I'm not sure it is still a thing but I remember helicopters being in the topic (I could be wrong on that one though).

Memory management concerns also played a part with what we catch. There was a feature that, basically, recorded the flight track and displayed it on a version of Google maps but, when ActiveX controls(?) became taboo, so did that feature.

To answer your question, theoretically, we could catch pretty much anything that we want. If you are really that curious, you can go to https://www.fsuipc.com/. Scroll down to 'Additional Free Software' and download the FSUIPC SDK. Have a look at FSUIPC for Programmers.pdf.

This is a great resource. Thank you for pointing me to it. Happy reading to me. :mrgreen:

 
Reply
  


Forum Jump:


Browsing: 1 Guest(s)