Hi Mark,

  I´ve done everything you said but didn´t solve the problems with LNAV/VNAV. The MCP doesn´t work at all. No AP. Have deleted files reinstaled the base pack several times and even the FSX,  but no solution.

Hugs

Dirceu

The problem is: After setting the inercial correctly and all the FMC stuff, perf init included, when you turn the FD on the TO mode don´t engage and so you don´t have neither the FD when flying nor the LNAV/VNAV modes if you try to engage them. All the MCP doesn´t work either.

cheers

Sometimes when I start a flight in FSX from Free Flight using the Captain Sim 767, after it loads, I get a situation like this:


The IAS/MACH Indicator displays 000 and the Altitude Indicator displays 00000.

Is this what is happening to any of you?

When this happens, a lot of the switches and buttons are not working either so I can't fly the 767. To fix this, I reload the 767. I have assigned the keyboard command CTRL+R to Aircraft (reload), so all I do is press CTRL+R and everything works fine after the reload.

Mark

Morten wrote on Dec 3^rd, 2011 at 4:46pm:
I've never had that happen with v1.5.

Morten wrote on Dec 3^rd, 2011 at 4:46pm:

FSC8 creates an FS Flight plan that is saved in FS9 format AND its own FSC format. So next time you create a plan with FSC8 and save it in Documents\Flight Simulator X files folder, open it with Notepad and delete [FSC] and everything below it. Then see if v1.5 can read it.


Part of the FS9 section of the saved FSC8 plan:
[Flightplan]
AppVersion=9.1.40901
title=YMML to KLAX      
description=YMML, KLAX      
type=VFR
routetype=1
cruising_altitude=29000
departure_id=YMML, S37* 40.16', E144* 50.27', +000433.00
departure_position=16
destination_id=KLAX, N33* 56.55', W118* 24.48', +000125.00
departure_name=Melbourne Intl
destination_name=Los Angeles Intl
alternate_name=
waypoint.0=, YMML, , YMML, A, S37* 40.16', E144* 50.27', +000433.00,
waypoint.1=KK, DOSEL, , DOSEL,  I, S37* 09.90', E145* 23.71', +000000.00,
waypoint.2=KK, EBONY, , EBONY,  I, S36* 10.94', E147* 04.23', +000000.00,
waypoint.3=KK, ARRAN, , ARRAN,  I, S35* 50.30', E147* 38.40', +000000.00,
waypoint.4=KK, NONUP, , NONUP,  I, S35* 25.80', E148* 17.90', +000000.00,


Part of the FSC section of the FSC8 plan:
[FSC]
DepartAPCode=YMML      
DepartNum=0
DepartID=16
DepartType=Rwy
DestAPCode=KLAX      
RouteType=1
SID=
STAR=
WP=1,Int,DOSEL,DOSEL,-37.1650,145.3953,0.00,40.9404,12.140,1,33758,H129
WP=2,Int,EBONY,EBONY,-36.1825,147.0706,0.00,54.3278,12.602,1,33767,Y59
WP=3,Int,ARRAN,ARRAN,-35.8383,147.6400,0.00,53.4020,12.239,1,33647,Y59
WP=4,Int,NONUP,NONUP,-35.4300,148.2983,0.00,52.8432,12.618,1,33974,Y59

If it doesn't read the FS9 FP format, open it in FSX > Flights > Flight Planner and then save it. FSX should save it in FSX Flight Plan format which v1.5 should be able to read. Mine did.


Part of the same plan that was made by FSC8, opened using FSX Flight Planner and then saved:
<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
   <Descr>AceXML Document</Descr>
   <FlightPlan.FlightPlan>
       <Title>YMML to KLAX</Title>
       <FPType>VFR</FPType>
       <RouteType>VOR</RouteType>
       <CruisingAlt>29000</CruisingAlt>
       <DepartureID>YMML</DepartureID>
       <DepartureLLA>S37° 40' 9.60",E144° 50' 16.20",+000433.00</DepartureLLA>
       <DestinationID>KLAX</DestinationID>
       <DestinationLLA>N33° 56' 33.00",W118° 24' 28.80",+000125.00</DestinationLLA>
       <Descr>YMML, KLAX</Descr>
       <DeparturePosition>16</DeparturePosition>
       <DepartureName>Melbourne Intl</DepartureName>
       <DestinationName>Los Angeles Intl</DestinationName>
       <AppVersion>
           <AppVersionMajor>10</AppVersionMajor>
           <AppVersionBuild>61637</AppVersionBuild>
       </AppVersion>
       <ATCWaypoint id="YMML">
           <ATCWaypointType>Airport</ATCWaypointType>
           <WorldPosition>S37° 40' 9.60",E144° 50' 16.20",+000433.00</WorldPosition>
           <ICAO>
               <ICAOIdent>YMML</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="DOSEL">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>S37° 9' 54.00",E145° 23' 42.60",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>DOSEL</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="EBONY">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>S36° 10' 56.40",E147° 4' 13.80",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>EBONY</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="ARRAN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>S35° 50' 18.00",E147° 38' 24.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>ARRAN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="NONUP">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>S35° 25' 48.00",E148° 17' 54.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>NONUP</ICAOIdent>
           </ICAO>
       </ATCWaypoint>



The error I mention above with the zero's displaying is the main "bug" I get in the 767 v1.5.

Mark

I have also a problem with the spoilers.

they won't arm on the ground before TO

When I use keyboard shortcuts / Joystick assigned button to arm the spoilers on the ground, they open  

While flying they arm correctly

Edit: just saw that there's no need to arm the speedbrakes during TO (normal procedure) bt that does not explain why they open when I want them armed on the ground...

Thx for your answers Markoz, you're very right, the spoiler system is exactly the same than stock airplanes one 

I did an aborted takeoff test today. I had the the autobrakes set to RTO and the autospoilers set (SHIFT+/). Both were triggered as soon as I pulled the throttles back to idle during the takeoff run. So I know it works very well for me.

Hi Morten.

I'm sorry to hear that doing all that doesn't fix it. You certainly appear to have a very strange problem with the FMS and your old plans.

Mark