Está disponível o SP3 para o B767 da Level D

Está disponível o Service Pack 3 para o Boeing 767 da Level D. Uma das mais aclamadas aeronaves para o Flight Simulator sofre assim mais uma actualização que desta vez corrige alguns bugs reportados ao nível do RMI, IRS e FMC, para além de outras pequenas correcções. Apesar de ser um excelente produto a Level D tem tido o cuidado de corrigir as situações que vão sendo indicadas pelos utilizadores, o que torna este um dos maiores casos de sucesso em termos de add-ons para o simulador da Microsoft. Todos os detalhes acerca deste service pack em ‘leia mais’ sendo que o download está disponível no site da Level D.

******************************************* Service Pack 3 *******************************************
This service pack was released on Feb 25, 2006
AFDS —– HDG SEL MODE automatically switches to HDG HOLD if HDG REF(NORM/TRUE) changes.- HDG SEL now follows correctly true heading in HDG TRUE mode.- LAND2 mode now correctly arms FLARE amp; ROLL mode.
MAIN PANEL———– RMI compass card shows true heading when in true north ref mode.- RMI had a bug that caused VOR2 needle to sometimes flag when it shouldn’t amp; vice versa- EHSI points correctly when in true north ref mode.- Orange Captain/FO Altitude bugs now saved with panel data
SYSTEMS——– The IRS position display on the overhead now displays righly “S” instead of “N” for latitudes between south zero degrees and south one degrees.- While navigation on IRS only, crossing either the prime meridian or dateline or equator resulted wrongly in doubling the IRS drift.
SDK—- numerous new commands and data have been added.Replace the old LVLDSDK.dll file with the new one provided in FS9Level-D SimulationsLevel-D SDK
FMC—- LNAV stays armed until within capture distance in Intercept Course.- Intercept Course was broken- Fixed intermittent bug in Direct-To function
FMC Procedures————–The procedures database has been redesigned to use individual airport files rather than a single procedures.XML file.This solves two problems that users were encountering with the large single proceduresl.xml file:- 1. An error in a single procedure would cause the entire file to fail to load, thus a single malformed procedure would result in NO procedures being loaded. With the format change this effect will be limited to one airport.
– 2. The procedures.xml file is searched sequentially, thus it could take a long time for a procedure to load. This was inconvenient and made the FMC appear as if it was locked up. All procedures will now load without delay.
The FMC will now save procedures to individual airport files, which are named ICAO_Airport_Name.XML. For example the procedures file for Heathrow is named EGLL.XML. If the file does not exist it will be created. If it exists it will be appended to. If that particular pocedure exists within the file it will be overwritten with the new one. The FMC will not write procedures to the old procedures.xml file.
The FMC will now load procedures from individual airport files. If the individual airport file does not exist the FMC will attempt to load the procedure from the old procedures.XML file.This is done to ease the changeover to the new single airport file format. The procedures.xml file is no longer supported.Users can now delete individual procedures from within the FMC. Procedure files in the new format will be made available from

Comments are closed.