docs(a32nx/feature guide): Estimated Takeoff Time#1119
docs(a32nx/feature guide): Estimated Takeoff Time#1119github-actions[bot] merged 6 commits intoprimaryfrom
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Sleinmaster
left a comment
There was a problem hiding this comment.
Also consider replacing "In order to" with "To"
| {loading=lazy} | ||
|
|
||
|
|
||
| If we depart prior to the ETT, it will be automatically deleted and the predictions will be updated automatically based on the current time, as usual. On the other hand, if we don't depart by 12:30Z, the "CLK IS TAKE OFF TIME" scratchpad message appears on the MCDU as a reminder. At this point, time predictions are continuously updated based on the current time. Although the ETT has expired, we can insert a new one if we wish by repeating the whole process. |
There was a problem hiding this comment.
Although the ETT has expired, we can insert a new one if we wish by repeating the whole process.
Not sure if although is the correct word here since it doesn't really matter if the ETT has expired or not to be able to repeat the process.
Maybe something like that?
| If we depart prior to the ETT, it will be automatically deleted and the predictions will be updated automatically based on the current time, as usual. On the other hand, if we don't depart by 12:30Z, the "CLK IS TAKE OFF TIME" scratchpad message appears on the MCDU as a reminder. At this point, time predictions are continuously updated based on the current time. Although the ETT has expired, we can insert a new one if we wish by repeating the whole process. | |
| If we depart prior to the ETT, it will be automatically deleted and the predictions will be updated automatically based on the current time, as usual. On the other hand, if we don't depart by 12:30Z, the "CLK IS TAKE OFF TIME" scratchpad message appears on the MCDU as a reminder. At this point, time predictions are continuously updated based on the current time. We can insert a new one by repeating the whole process. |
There was a problem hiding this comment.
yeah it does not. Maybe it could be an info note at the end or further up rather than next to the sentence? Something amongst the lines of. The only requirement to be able to insert an ETT in the active flightplan, is the preflight phase being active. For the secondary flightplan, no requirement applies unless it was created as a copy of the active. If that is the case, the same restriction as the active flightplan applies.
|
I can modify the images for optimization this week while waiting for changes. Thanks. |
Is there anything I can help from my side? If its just converting to jpg I don't mind doing it. |
JPEGs would scale themselves, if you're using pngs (which is ok) you have to check yourself that the width is as specific on https://docs.flybywiresim.com/dev-corner/documentation-guide/writing-documentation/#image-optimization |
|
Only now coming back to this as I somewhat forgot we didn't finish it. Images are now converted to jpg and i rewrote the last bit as per the suggestion & added some extra information at the start about restrictions. Let me know what you think @Sleinmaster |
|
Thanks lgmt |
Fixes #1116
Summary
Adds a feature guide about the Estimated takeoff time function (flybywiresim/aircraft#10487).
Updates MCDU guide f-pln page to mention the new functionality of the RTA page.
Location
https://flybywiresim-docs-rta-ett.cf-fbw-docs.pages.dev/aircraft/a32nx/feature-guides/estimated-takeoff-time/
https://flybywiresim-docs-rta-ett.cf-fbw-docs.pages.dev/pilots-corner/a32nx/a32nx-briefing/mcdu/f-pln/#rta-page
Discord username (if different from GitHub): bruno_pt99