Hi Mark

Just a couple of questions before leaving the 1.5:

1. Have you possibly tried to load FSC8 based plans into your own 1.5 FMS with a successful result? or only FSC9 based plans?
I just wonder if perhaps the CS converter is not able to import FSC8 plans?

2. Another strange thing I noticed, is that it seems that the only 5% of the FSC8 based plans that the 1.5 FMS will accept, is all written in "AceXML" format. Along with these plans there are valid waypoints inside the Legs section of the FMS. Whereas plans written in core text format are completely empty in the Legs section, which obviously is the reason why these plans are non-executable!

I have no idea why the plans is sometimes in this "AceXML" format and sometimes only in text format - however both types of plans format has the same .PLN file extension..!!!
Originally all the the FSC8 plans are made in text format on my client XP PC - but when I transfer the plans to my main W7 PC into the C:\Users\Morten\Documents\Flight Simulator X Files some of these plans (automatically or under influence of CS?) are converted into this "AceXML" format!

Here's an example of a FSC8 based plan LFMNLSZH.PLN that my 1.5 FMS successfully will accept:

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
   <Descr>AceXML Document</Descr>
   <FlightPlan.FlightPlan>
       <Title>LFMN to LSZH</Title>
       <FPType>IFR</FPType>
       <RouteType>VOR</RouteType>
       <CruisingAlt>21000</CruisingAlt>
       <DepartureID>LFMN</DepartureID>
       <DepartureLLA>N43° 39' 22.20",E7° 12' 55.80",+000010.00</DepartureLLA>
       <DestinationID>LSZH</DestinationID>
       <DestinationLLA>N47° 27' 29.40",E8° 32' 52.80",+001414.00</DestinationLLA>
       <Descr>LFMN, LSZH</Descr>
       <DeparturePosition>04R</DeparturePosition>
       <DepartureName>Nice/Cote D&apos;Azur</DepartureName>
       <DestinationName>Zurich</DestinationName>
       <AppVersion>
           <AppVersionMajor>10</AppVersionMajor>
           <AppVersionBuild>61472</AppVersionBuild>
       </AppVersion>
       <ATCWaypoint id="LFMN">
           <ATCWaypointType>Airport</ATCWaypointType>
           <WorldPosition>N43° 39' 22.20",E7° 12' 55.80",+000010.00</WorldPosition>
           <ICAO>
               <ICAOIdent>LFMN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="USANO">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N43° 44' 3.00",E7° 42' 49.80",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>USANO</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="BASIP">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N43° 53' 31.80",E7° 57' 42.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>BASIP</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="ABN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 3' 21.60",E8° 13' 15.60",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>ABN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="DORAV">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 19' 34.80",E8° 51' 7.80",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>DORAV</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="GEN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 25' 27.60",E9° 4' 55.20",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>GEN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="VOG">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 57' 52.20",E8° 58' 12.60",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>VOG</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="SRN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N45° 38' 45.60",E9° 1' 18.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>SRN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="CANNE">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N46° 10' 0.00",E8° 52' 52.20",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>CANNE</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="KELIP">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N46° 57' 22.20",E8° 45' 42.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>KELIP</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="LSZH">
           <ATCWaypointType>Airport</ATCWaypointType>
           <WorldPosition>N47° 27' 29.40",E8° 32' 52.80",+001414.00</WorldPosition>
           <ICAO>
               <ICAOIdent>LSZH</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
   </FlightPlan.FlightPlan>
</SimBase.Document>
         

CoolP wrote on Dec 11^th, 2011 at 9:42pm:


I could try that - however I'm not sure if the native FSX format will keep my SIDs and STARs extensions added through FSC8..? if not, I can't go that way.

Hi Morten.

I can try it, but it will be a while before I do. FSX decided to go crazy on me last night and now I have to reinstall it. I hate that!

Mark

Morten wrote on Dec 13^th, 2011 at 12:16am:

That is pretty much all I use FSC9 for too, except the moving map. I rarely connect FSC to FSX and track my flights.

Anyway. I'm glad you found a work-around to help you sort this out. It does seem like Captain Sim changed it enough not to recognize the FSC8 Flight Plan (FS9?) format. I actually think it does not have the capability to load a Flight Plan in the older FS9 format and that has a kick-on affect to FSC8 (as explained in my earlier reply).

Mark

You mean the CG entry and the then computed trim setting? I think it stays like on the releases before 1.5, which means that the CG entry already is a bit off from the rw 767 spectrum. You can estimate it in the FSX payload dialogue and then get a FMC trim value.
As that part of the simulation is simplified pretty much, maybe a default trim setting is the most reasonable solution. That's just my impression though.

Markoz wrote on Dec 17^th, 2011 at 6:20am:


Arhhh!..
OK, many thanks for letting med know anyway, so I don't have to risk a fatal crash after all them time-consuming preflight preparations..!!

I'll just ignore the trim settings then and instead use the trim option on my yoke intuitively during climb as I already was getting use to with the 1.4 version - That is, mostly by pressing her smoothly down a bit until reaching the V/LNAV/AP engagement phase at around 1000 agl.   

Another thing, however less important - The weather conditions data via my weather radar is only viewable through the extra HSI popup window and not directly on the HSI itself.

Anyone else having the same problem?

Yeah okay!
I'm trying to use it 100% of the time, but it will only show up on the actual HSI 25% of the time. In fact this error already started back on the 1.4 version - I guess it must be system related, then - Related to my multimonitor setup or my graphic driver.