Kyle Kahn
-
Posts
17 -
Joined
-
Last visited
Posts posted by Kyle Kahn
-
-
10 minutes ago, aivlasoft said:
What means "etc"?
I just did a quick test and created a flight plan on SimBrief.com. The only field which is set to 00:00 is FOB. This is because the FOB time is not provided in the section 'ICAO Flight plan' of the OFP which is parsed by EFB. If you plan with PFPX for example, the FOB field is properly filled.
Yes FOB time is 0:00. I guess I need to manually add these numbers then.
I have set STD at 16:00z in simbrief however it parses as 15:37z in efb. Sometimes WTC is not recognized as well. Other than that it's good. Could you please add those information to the “after-flight” flight log that is generated by EFB after touchdown? And make the flight log editable so we can take some notes?
-
1 hour ago, aivlasoft said:
Is "yes" related to the first or the second question? 🙄
Some data provided by OFP is inconsistent with the data on the second page of flight plan creation such as FOB time STD etc. I will have to re-enter these numbers in the blanks sometimes.
Also it would be nice if we can add some notes on the final flight log or make after-flight flight log editable.
-
7 hours ago, aivlasoft said:
Hi Kyle,
Are you talking about the data on the second screen of the flight plan creation dialog, or about the data which is provided by a flight (OFP) from SimBrief?
Yes, but that information is not available in final flight log.
-
Hi Aivlasoft,
Could you please record more information on the flight log? Such as scheduled time of departure/arrival (Runway Time), scheduled enroute time, block fuel time, Airline name and a flight number? I use simbrief to retrieve the flight plan and I was asked to fill the STD/STA and these blanks. They just didn't appear on the flight log unfortunately.
Thank you for the assistace,
Kahn
-
2 hours ago, lonewulf47 said:
Hi Kyle,
Please check the Manual "5 EN Client" page 94, the Remark about X-Plane. This is common behaviour if the respective ICAO-Code is not contained in the Profile in question. I don't have the Ultimate B737-700. Maybe you could retrieve the Code from the *.acf file and publish here? So we could add it to the present set of profiles.
Hi, I just found the ICAO code is B737 in the planemaker. I'm not sure if I can share the .acf with you due to copyright concerns.
-
5 hours ago, aivlasoft said:
In the meantime we have figured out that the 767 seems to be the only one which does not work properly. But in the meantime I have also found another trigger which seems to be more reliable than what I have used before. It works now with the 767 too and will be available with next update. Thanks for reporting.
Thanks! I will report back the test result after the fix is released.
I would like to report another issue. When I was flying with Ultimate 737-700 for X-Plane. The EFB won't recognize the profile and it's using the default profile instead. Could you please take a look at this? Thank you!
-
ok i tried default aircraft at the same spot its working.
-
Inside the cockpit
-
okay it''s happening again this time at SLC I arrived in
-
On 4/25/2019 at 11:36 AM, aivlasoft said:
No, because it is not needed (if all works properly). So we should investigate why this flight did not detect touchdown and therefore it did not automatically close the flight plan. Usually the flight plan is then available in the EFB library, and therefore in the EFB 'Library' folder as a pdf-file (it's also possible to have it as a CSV-file).
Hi Urs, I think I found the issue now. I'm now starting a new flight in Paris. The status bar at the beginning says "Enroute" but I'm still on the ground.
Could you please tell me how do you evaluate if the plane is staying on the ground or flying? Do you take AGL data as a reference?
Please reply to me if you see this message.
K
-
Quote
Could be. I don't have had a look at this. Of course I would have to ask the people at FSRealtime first.
That's great! If you have their permission to use the file, do you consider adding this as a feature? We really need local time format as an annotation to the UTC because it's being used in airport charts, information and flight logs.
QuoteUsually all works automatically. But here it obviously went something wrong which I have never seen before. I can see on the sidebar that most probably the sequencing of the waypoints did not properly work or something else happened (e.g. Active WPT is empty, Dist=2.0km, Time 23:54) These values are completely wrong. Did you use time compression? Was it a regular flight with a duration of 10h:29m without any interruption. Did you experience any other 'anomalies' while in flight?
I don't think something went wrong in this case, I wasn't monitoring the flight because I was sleeping during the long haul flight. However, the flight duration at 10:20 is normally the flight time from Seattle to Paris in the real world so I don't think it triggered time compression.
When I woke up everything was perfectly fine, I have noticed this issue at the time of on blocks. It indeed recorded the time of touch down (15:03z) but there is no way to complete the flight or export the log. Do you have a manual switch or short-cut method to complete a flight? I have read the manual but it doesn't cover the instructions.
-
-
On 4/19/2019 at 3:58 AM, aivlasoft said:
Hi Kyle
This would require a database with local time offsets because it's not just one hour every 15° ... I unfortunately don't know such a database. Do you?
Currently we do not have plans to introduce this functionality in the near future, but we will keep it on our radar and probably reconsider our decision if we get more requests regarding this functionality.
The current version of EFB does automatically log the takeoff and the touchdown time but not the engine ON/OFF. EFB v1 had an internal trigger for engine ON/OFF, but unfortunately we had to learn that it does not work for all aircraft, so we decided to take a trigger for v2 which is always available. Maybe we could add a possibility to manual start/stop the time.
What kind of database are you looking for? FSRealtime has a corrected timezone file, I assume you are talking about this?
In EFB V2 I have encountered a new issue, the status of a flight stays at ARRIVAL even when the plane has arrived at the airport and on the ground. Normally when EFB detects a touch down it will automatically save the flight log as a document.
However, this doesn't appear to be the case for my flight today to Paris. The status says "Arrival" even when the flight actually on blocks. And there is no way to export the flight log as pdf for this reason. I didn't find a switch to complete this flight manually.
Am I doing things wrong or you didn't add a button to complete a flight manually?
-
Hi Aivlasoft,
Could you please inform us if the local time indication (as a sidenote to UTC) is implemented? The time refers to airport charts or info is all local time, I will have to google the local time at the destination for this reason. As far as I know, there is no alternative has implemented this feature, it would be best if you have considered it.
Also, I really want to see there will be a "Diversion" option in the flight log, sometimes you may not able to reach the destination but have to land at an airport for emergency reasons. So you would have every flight (normal or abnormal) recorded.
Is there still a chance that OFF/OUT/IN/ON times to be recorded in the flight log? Many airlines flight log have these entries to be filled by ACARS. I hope it will be available in EFB v2. (EFB v1 has this implemented)
AFAIK, VA software can record the engine start/shutdown time as OFF/ON time, at least for X-Plane it works. However, this option is not available to non-VA users. It can still be used for flight log purposes.
Thank you very much for the answers.
Cheers,
K
-
9 hours ago, aivlasoft said:
Due to the fact that some developers of add-on aircraft program the engines outside of the simulator, it is not always possible to recognize the time when the engine starts and when the engine stops. Engine start and stop was the trigger to save the Block-On and Block-Off-Time in EFB v1. We decided to no longer rely on this.
In EFB v2 only the liftoff and the touchdown time is logged. The flight log is still opened/closed/saved automatically, saved as PDF and/or CSV file.
1I remembered you can log the Block OUT time and Block IN time manually in EFB v1, do you plan to keep this feature?
-
Hello Aivlasoft,
Congrats on the release, you made it on time!
I just have few questions to ask about EFB v2
1. There is a neat tool in ETA v1 to log all times during the flight phase. (The ATA to reach a specific waypoint, OUT TIME, OFF TIME-ATD, ON TIME-ATA, IN TIM etc. Does ETA v2 have this toll as well?
2. I know on-ground times are logged in UTC format but are they going to be logged in local time formats as well, more like adding an additional time indication for local time? See there is local time formats used on the AOC charts, for airport operation, runway preference usage, noise abatement procedure etc, so that might be helpful and necessary.
3. Are you going to support X-Plane in the next sub-version of v2, when?
Thank you very much for the answers
Cheers,
Kahn
FS2020 EFB version?
in EFB v2 - Support forum
Posted
According to fsdt, simconnect is still supported in the new sim.