Timeline
03/07/15:
- 19:28 Ticket #253 (New reverser usage logic) created by
- According to most ACFT FCOM, the usage of reverser is not prohibited …
- 15:55 Changeset [613:215a5d286518] by
- Updated to the latest version
- 06:45 Changeset [612:e0785d69da78] by
- Modified the minimum landing fuel to 7000 kgs (re #251)
- 06:45 Changeset [611:6e8540c1970b] by
- Added checks for tailstrike during takeoff and touchdown (re #250)
- 05:19 Ticket #252 (Boeing 767 min. remaining fuel) closed by
- duplicate: Duplicate of #251.
03/06/15:
- 20:14 Ticket #252 (Boeing 767 min. remaining fuel) created by
- Please reset the 767 family's min. rem. fuel value to 7.000Kgs. Thanks
- 20:12 Ticket #251 (Boeing 767 min. remaining fuel) created by
- Pls. reset the min. rem. fuel value for 767 family to 7.000Kgs. Thanks
- 17:04 Ticket #250 (New NO GO) created by
- Implementation a new NO GO feature: Tail Strike Goal: Automated NO GO …
03/05/15:
- 18:19 Changeset [610:66c6e9ccf72c] by
- Stepped the version
- 18:14 Changeset [609:4eac92648123] by
- Disconnection from the simulator is logged (re #249)
03/01/15:
- 18:42 Changeset [608:74ab0fb49fbe] by
- Fixed the documentation
- 18:40 Changeset [607:d0dccf044560] by
- The help text on the Finish page is updated dynamically based on the …
- 18:25 Changeset [606:acd6bab9eda5] by
- The fault updating operations are put into the main queue (re #248)
- 18:22 Changeset [605:f508c2cac441] by
- The finish page also checks for the presence of all explanations (re #248)
- 16:53 Changeset [604:0ec6a6f58f08] by
- Added a new widget to list the faults and provide space for the user …
02/28/15:
- 11:10 Ticket #249 (Logging sim. crash in log) created by
- Couple of people are having issues with FS, and even myself had 2 …
- 11:08 Ticket #248 (PIREP proc. in case of irregularities) created by
- - Removal of text box "hibajelenségek" - Implementation of a feature, …
02/22/15:
- 09:51 Changeset [603:6cf5eff2a6d7] by
- Updated to the new version
- 09:39 Changeset [602:130e4cf75677] by
- Altitude is logged with flaps changes during all flight stages (re #247)
- 09:38 Changeset [601:16ff9fcc527c] by
- The initial climb speed is logged (re #246)
- 09:37 Changeset [600:c788380d2fea] by
- The manual speedbrake operation is logged (re #245)
- 09:35 Changeset [599:2f719a01af01] by
- The textual version of the delay codes is also sent to the website (re …
- 09:33 Changeset [598:85f4667214b4] by
- The reverser use is logged and is checked against IAS with a lower …
- 09:29 Changeset [597:79a1c9f14bc5] by
- It is no longer a NOGO if the amount of landing fuel is too low (re #239)
02/21/15:
- 13:25 Changeset [596:875cd3520493] by
- Stepped the version
- 01:14 Ticket #247 (Take-off flaps retraction schedule altitude logging) created by
- To improve logging details considering flaps retraction schedule durin …
02/20/15:
- 15:36 Ticket #246 (New log entry: Initial climb speed) created by
- Implementation of a new line to log: Title: Initial climb speed Time: …
- 14:11 Ticket #245 (Speedbrake deployment and closure logging) created by
- To make it possible to see speedbrake operation in log, not only at …
02/19/15:
- 06:10 Ticket #241 (The usage of the reverser should be logged) closed by
- duplicate: This is a duplicate of #242.
- 06:09 Ticket #240 (Send the meaning of time codes as well) closed by
- duplicate: TThis is a duplicate of #243.
- 00:03 Ticket #244 (Company NOTAM) created by
- Implementation of a new logger page: Phase: Before connecting to …
02/18/15:
- 22:28 Ticket #243 (Delay code modification) created by
- Add text format delay code to reported code to be shown on supervisors …
- 22:26 Ticket #242 (Reverser use and log entry) created by
- Implemantation of "Reverser up" entry to the log with logged IAS and …
- 18:23 Ticket #241 (The usage of the reverser should be logged) created by
- 18:22 Ticket #240 (Send the meaning of time codes as well) created by
- Currently the delay codes are sent with the code only, but it would be …
- 18:21 Ticket #239 (Landing with too low fuel should not be NOGO automatically) created by
- Such a situation should be considered a fault with a score of 0, and …
Note:
See TracTimeline
for information about the timeline view.
