Jump to content
The simFlight Network Forums

JetJerry

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JetJerry

  • Rank
    Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    Atlanta
  • Interests
    aviation/fly fishing
  1. Yes it is Jesse, Good product, good people and good forum. Thanks again! Jerry
  2. OK, all you guys not any smarter than me. Volker found my problem, and I am very appreciative! "I was selecting FIND ROUTE after loading the FP into FSX." DO THE PROCESS OUTLINED BELOW: Select Flight Planner Click on Load select the plan you have created and saved with FSCommander (in my case KDFWKSTL). Now DO NOT CLICK ON FIND ROUTE - CLICK on NAvlog or EDIT but NEVER on FIND ROUTE. While you CLICK on FIND ROUTE FSX ignores your loaded plan and creates a new plan. Therefor, as you can see, this is NOT a FSCommander problem. It is a user problem. I am very happy to have FSC back again and running as it should...THANKS! I wish to thank everyone who posted and tried to help. I apologize for the trouble I've caused. Jerry
  3. Volker: I will send the 2 FP's, but I don't think it will help. I did that before and they both showed the correct route. However, for whatever reason, when the saved FP is LOADED into FSX it runs it incorrectly (not as saved). Again, if I change the "KDFWKSTL to a number and open it in a certain airplane that requires numbers, it runs it correctly. Good luck! Jerry
  4. OK, I removed ALL FP's from the FSX folder. I used FSC9 to build a new FP: KDFW BYP FSM HRO MAP KSTL (This time I used the WPT box)...instead of RT click. I saved it: "SAVE AS"...to FSC and FSX. I ran FSX and "LOADED" the FP (KDFWKSTL)...the only FP in the file. When I opened the route in FSX it displayed this: KDFW CVE BYP FSM HRO DGD TBN VIH FTZ STL CSX KSTL Thanks, Jerry
  5. I know you can not verify my problem Volker. I only wish you could. I have about given up on trying to figure out why this happens. I will run the above FP again today just to satisfy myself. I've been using "right click", I will try other method to add wpts this time. Thanks for responding, Jerry
  6. Volker: If you will recall I, Jerry Allen, (in a different post) sent you my two FP's and they were identical, and thus you said it was not a FSC9 problem. Well, it is still doing exactly what is described above...even though the two FP's are the same. Again let me say that if I change the FP to a number for use in one particular airplane it works, but in all other cases if I leave it as transferred by FSC to FSX using only the FSC interface then FSX runs whatever route it wants rather than actually using the one FSC sends...JUST AS THE ABOVE ILLUSTRATION...even with default airplanes. Thank you for your attention on this matter, Jerry FSX FSUIPC 4.6 FSC 9.0 Build: 23-11-2010 Aerosoft & Wn7/64 PREVIOUS POST: Posted 19 December 2010 - 05:26 PM I built a FSX FP using FSC9 and saved it: "SAVE AS". FSC9 Showed this route (correct): KDFW.BYP.FSM.HRO.MAP.KSTL When I opened the FP in FSX it showed (incorrectly): KDFW.CVE.BYP.FSM.HRO.DGD.TBN.VIH.FTZ.STL.CSX.KSTL This happens with every FP, not just the one above. I built the FP using the Right Mouse Click function over the waypoints and selecting. Any ideas what is wrong? Thank you, Jerry Allen
  7. I am still having the same problem and I'm using FSX. A funny thing about this is: I have one airplane where I need to change the FP to a number rather than leaving it "KSEAKSFO etc, and those changed to numbers work fine and do not arbitrarily change the route from FSC9 to FSX. Jerry Wn7/64
  8. I would like to use FSC9 for ATC during multi-palyer sessions. Is there a way to set the distance I can see AI traffic to 40nm or more? Thank you, Jerry Allen FSX / FSUIPC 4.6 / AS FSC9.build 01-01-2011 / Wn 7/64
  9. Volker: It seems my problem has nothing to do with FSC. I just made a FP using only the FSX planner: KSEA.OLM.SCAPO.KPDX. Yet when I loaded it, it ran: KSEA.KPDX. There was not a previous KSEA-KPDX FP in FSX, so this had to have been the one I just made, yet it too is incorrect. I apologize for assuming I had a FSC problem. Do you by chance have any idea what may be causing my FSX problem? Sorry to have bothered you. Have a great day. Jerry
  10. When the FSC flightplan is opened thru FSC and displayed using FSC the route is as stated above. However, when the same flightplan is opened thru FSX and diplayed in the FSX plan/route it is displayed differently...again, as above. I don't understand how this can be happening. Every time I use a flihtplan with FSX rather than FSC then I must delete and add the waypoints within the FSX flight planner in order to make it the same routing as it is in FSC. However...they were both "saved as" after building the FP with FSC, with "FSC" and "FSX" checked in the save box. If there is no answer for why this may be happening, then I will un-install FSC9 and re-install it and see what happens. I am waiting to hear from you again. Thanks, Jerry
  11. Well then I don't understand how they can read out as two different routes in FSC and FSX. FSC = KLNK PWE STJ LMN MCM HLV FTZ KSTL FSX = KLNK STJ MCM STL CSX KSTL Jerry
  12. Volker: Thank you for responding to this. I have no idea what is happening. I did find something that looked incorrect to me...don't know if it is: I have FSC9 > D:\Program Files(x86)\Aerosoft\FSC9\FlightPlan\ *then I have another FSC folder under that that shows only FlightPlans. Here is a FP I just made from KLNK - KSTL. The FSC plan is correct. <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KLNK to KSTL</Title> <FPType>IFR</FPType> <RouteType>VOR</RouteType> <CruisingAlt>5000</CruisingAlt> <DepartureID>KLNK</DepartureID> <DepartureLLA>N40° 51' 27.00",W96° 45' 38.00",+001217.00</DepartureLLA> <DestinationID>KSTL</DestinationID> <DestinationLLA>N38° 44' 51.00",W90° 21' 35.00",+000604.00</DestinationLLA> <Descr>KLNK, KSTL</Descr> <DeparturePosition>14</DeparturePosition> <DepartureName>Lincoln</DepartureName> <DestinationName>Lambert-St Louis Intl</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="KLNK"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N40° 51' 27.00",W96° 45' 38.00",+001217.00</WorldPosition> <ICAO> <ICAOIdent>KLNK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="PWE"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N40° 12' 1.00",W96° 12' 22.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>PWE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="STJ"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N39° 57' 38.00",W94° 55' 30.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>STJ</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LMN"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N40° 35' 48.00",W93° 58' 3.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>LMN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MCM"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N39° 39' 14.00",W92° 28' 55.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>MCM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HLV"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N39° 6' 48.00",W92° 7' 41.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>HLV</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FTZ"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N38° 41' 39.00",W90° 58' 16.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>FTZ</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KSTL"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N38° 44' 51.00",W90° 21' 35.00",+000604.00</WorldPosition> <ICAO> <ICAOIdent>KSTL</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> ========================================================================================== [FSCFP] DepartAPCode=KLNK DepartNum=0 DepartID=14 DepartType=Rwy DestAPCode=KSTL RouteType=1 SID= STAR= Transition= WP=1,VOR,PWE,PAWNEE CITY,40.20035,-96.20628,112.40,146.9565,3.823,1,0,0,,0,0,3186 WP=2,VOR,STJ,ST JOSEPH,39.96058,-94.92522,115.50,103.3329,2.401,1,0,0,,0,0,3657 WP=3,VOR,LMN,LAMONI,40.59674,-93.96760,116.70,48.6426,1.544,1,0,0,,0,0,2200 WP=4,VOR,MCM,MACON,39.65406,-92.48215,112.90,129.2107,0.868,1,0,0,,0,0,2353 WP=5,VOR,HLV,HALLSVILLE,39.11354,-92.12823,114.20,153.0443,0.868,1,0,0,,0,0,1564 WP=6,VOR,FTZ,FORISTELL,38.69433,-90.97116,110.80,114.6008,-0.566,1,0,0,,0,0,1288
  13. I built a FSX FP using FSC9 and saved it: "SAVE AS". FSC9 Showed this route (correct): KDFW.BYP.FSM.HRO.MAP.KSTL When I opened the FP in FSX it showed (incorrectly): KDFW.CVE.BYP.FSM.HRO.DGD.TBN.VIH.FTZ.STL.CSX.KSTL This happens with every FP, not just the one above. I built the FP using the Right Mouse Click function over the waypoints and selecting. Any ideas what is wrong? Thank you, Jerry Allen FSX FSUIPC 4.6 FSC 9.0 Build: 23-11-2010 Aerosoft & Wn7/64
  14. Volker: Thank you Sir. I , as you know, was mis-reading the line for saving the path to "Add-Ons". All is working as it should now...THANKS! I like FSC9. Much more intuitive than 8. The SID; STAR & TRANSITION saves on printed paper too. Jerry
  15. I have FSC 9 and like most of it, but i can not save a PMDG flight plan. I have: FSX FSUIPC 4.6 registered FSC 9.0; Database 9.0; Build 291010/091010; Aerosoft; Windows 7/64. I have the PATH correct for both FSX plans and PMDG and the PMDG box is checked. However, when I select "SAVE AS" I get a message that: "Flight plan for Add-On aircraft can not be saved because the FSX folder is unknown. I have FSX, and thus the PMDG folder on Drive E:, and FSX flight plans are on C: in "My Documents" as normal. If anyone can help me please make it simple. I am an airplane guy, not a computer person. Thanks, Jerry
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.