|
Post by Michael on May 5, 2014 16:20:13 GMT -5
Hi, First I would like to congratulate the developers. I recently bought the addon and it's now adding an extra challenge providing a better sim experience. Now may I suggest 2 things to be added (if possibe of course!): -via the request menu, would it be posible to get information on the runway(s) in use at the destination airport. It woud be very nice to prepare the approach. -in the log file maybe display more information (if possible) such as the landing vertical speed (ft/min), the landing speed (kts), the average cruise speed... Again thanks for your work and I hope you will consider my ideas . Regards, Michael
|
|
|
Post by peter on May 5, 2014 16:58:49 GMT -5
Hi Michael,
with respect to the runways, FSCaptain is not really designed to give you reliable information about the runway. It would need detailed information about individual airport procedures, which it simply doesn't have. In my experience, not even dedicated ATC programs get this right all the time, the only way to get reliable information seems to be Vatsim or IVAO.
Having said that, a rule of thumb that works 95% of the time is to pick a runway that is close to the wind direction. For instance, if FSCaptain tells you the wind is 215@7 and your destination has runways 24 and 06, then pick 24.
As for the log file, much of the information you suggest is displayed when you select a flight in the log and then click on "view details". FSCaptain stores all the information you mention, but some of it seems only to be displayed when you export it (others: correct me if I'm wrong here).
Cheers, Peter
|
|
|
Post by Michael on May 7, 2014 14:56:50 GMT -5
Ok Peter thanks for your answer. In fact I wars suggesting that FSCaptain would use the data from the sim concerning the active runway at the destination airport, just like when the default atc cleares you for the approach. Anyway very nice app.
Bye,
Michael
|
|
|
Post by Travis on Jul 16, 2014 16:29:54 GMT -5
Several years ago (for AivlaSoft EFB) I stumbled on an algorithm that is highly successful in determining which runway(s) should be active for an FSX ATC airport. (There are three factors... one of which is wind direction/speed.) However, the internal ATC is the actual "boss" for these matters - and it's only possible to derive the actual active runway(s) when one is near to the airport and when there's active internal AI there. (So it would require the simulator to be running, and at Dispatch, you'd only know the active runway for the departure airport, etc....) I've had some thoughts in mind to enhance the "crosswind" enforcement of FSCaptain, and those thoughts would need to have the necessary "available runways" in play, so when Dutch returns from his sojourn I'll pass them along to him to see what can be used. As for the extra logging... I've already put a bug in Dutch's ear to possibly export a post-flight log that would mimic the pre-flight Dispatch along with the values at each waypoint, as well as the landing stats you've mentioned. It's all a matter of time.
|
|