February 8, 201412 yr Hi, I just purchased and installed RC4 but having trouble to get it run correctly. The problem seems a bit unusual and would need some helps here please. issue 1 There's always run time error 5 after loading my flight plan. The flight plan was created within FSX planner and RC database have been rebuild for a several times. issue 2 Run time error 6 when I press to hear the voice under Customize Voices menu. My OS is Win7 64bit, Traditional Chinese as you notice from the screenshots, not sure if it has anything to do with the problem. Thanks!
February 9, 201412 yr In part your system language setting could be the problem. How is your numerical decimal place parsing setup. Do you use a comma for thousands and a decimal point for separation? Try setting up for US standards and see what happens. Also, paste in a reply here an extract with the origin and destination from your FSX .pln file. Make sure for testing you use default airports within FS when creating your plan. There are some fixed databases in RC that only include default airport airports. These databases are not extracted from your scenery. This a more infrequent cause, however.
February 9, 201412 yr Author Hi, Thanks for the assistance! I've been advise by another member of this fourm to change unicode setting which elimanated the problem in Customize Voices menu however causing error to other program in my computer, so I'm wondering if there's other solution please. Problem to load .pln do not resolve by change the unicode setting. I just rebuild RC data base again and create a plan using default airports but came up with the same error. extract of the .pln as below. Thanks for the help again amd really looking forward to get this great program to run. <?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KSFO to KLAX</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>32000</CruisingAlt> <DepartureID>KSFO</DepartureID> <DepartureLLA>N37* 37' 0.37",W122* 22' 55.52",+000013.00</DepartureLLA> <DestinationID>KLAX</DestinationID> <DestinationLLA>N33* 56' 9.47",W118* 25' 7.69",+000126.00</DestinationLLA> <Descr>KSFO, KLAX</Descr> <DeparturePosition>GATE D 2</DeparturePosition> <DepartureName>San Francisco Intl</DepartureName> <DestinationName>Los Angeles Intl</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61637</AppVersionBuild> </AppVersion> <ATCWaypoint id="KSFO"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N37* 37' 0.37",W122* 22' 55.52",+000013.00</WorldPosition> <ICAO> <ICAOIdent>KSFO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="OAK"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N37* 43' 33.30",W122* 13' 24.92",+000000.00</WorldPosition> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>OAK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="AVE"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N35* 38' 49.11",W119* 58' 42.98",+000000.00</WorldPosition> <ATCAirway>J1</ATCAirway> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>AVE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DERBB"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35* 15' 21.25",W119* 38' 29.21",+000000.00</WorldPosition> <ATCAirway>J1</ATCAirway> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>DERBB</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="REYES"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34* 39' 31.43",W119* 8' 3.56",+000000.00</WorldPosition> <ATCAirway>J7</ATCAirway> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>REYES</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FIM"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N34* 21' 24.11",W118* 52' 52.65",+000000.00</WorldPosition> <ATCAirway>J7</ATCAirway> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>FIM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LAX"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N33* 55' 59.31",W118* 25' 55.22",+000000.00</WorldPosition> <ATCAirway>J7</ATCAirway> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>LAX</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KLAX"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N33* 56' 9.47",W118* 25' 7.69",+000126.00</WorldPosition> <ICAO> <ICAOIdent>KLAX</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan></SimBase.Document>
February 9, 201412 yr 5 Invalid procedure call6 Overflow is the error message definition. Are you still getting these when loading the .pln file? I don't have FSX but I can create a plan with a payware utility FSBuild version 2.4. Try loading this plan file : <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KMSP to KMDW</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>27000</CruisingAlt> <DepartureID>KMSP</DepartureID> <DepartureLLA>N44° 52' 55.00" , W93° 13' 18.00",</DepartureLLA> <DestinationID>KMDW</DestinationID> <DestinationLLA>N41° 47' 09.00" , W87° 45' 08.00",</DestinationLLA> <Descr>KMSP, KMDW</Descr> <DeparturePosition>04</DeparturePosition> <DepartureName>MINNEAPOLIS-ST_PAUL_INTL</DepartureName> <DestinationName>CHICAGO_MIDWAY_INTL</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>60905</AppVersionBuild> </AppVersion> <ATCWaypoint id="KMSP"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N44° 52' 55.00",W93° 13' 18.00",</WorldPosition> <ICAO> <ICAOIdent>KMSP</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="FGT"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N44° 37' 51.00",W93° 10' 55.00",</WorldPosition> <ICAO> <ICAOIdent>FGT</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LOAFR"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N44° 28' 10.00",W92° 58' 47.00",</WorldPosition> <ICAO> <ICAOIdent>LOAFR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SHUZE"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N44° 21' 27.00",W92° 50' 26.00",</WorldPosition> <ICAO> <ICAOIdent>SHUZE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BROTA"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N44° 13' 13.00",W92° 40' 16.00",</WorldPosition> <ICAO> <ICAOIdent>BROTA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="UKN"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N43° 16' 48.00",W91° 32' 14.00",</WorldPosition> <ICAO> <ICAOIdent>UKN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DBQ"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N42° 24' 05.00",W90° 42' 32.00",</WorldPosition> <ICAO> <ICAOIdent>DBQ</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="CVA"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N41° 42' 30.00",W90° 28' 59.00",</WorldPosition> <ICAO> <ICAOIdent>CVA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DIPSY"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N41° 15' 56.00",W89° 45' 30.00",</WorldPosition> <ICAO> <ICAOIdent>DIPSY</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BDF"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N41° 09' 35.00",W89° 35' 16.00",</WorldPosition> <ICAO> <ICAOIdent>BDF</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MOTIF"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N41° 13' 46.00",W88° 30' 03.00",</WorldPosition> <ICAO> <ICAOIdent>MOTIF</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MINOK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N41° 28' 07.00",W88° 21' 47.00",</WorldPosition> <ICAO> <ICAOIdent>MINOK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="JOT"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N41° 32' 47.00",W88° 19' 06.00",</WorldPosition> <ICAO> <ICAOIdent>JOT</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KMDW"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N41° 47' 09.00",W87° 45' 08.00",</WorldPosition> <ICAO> <ICAOIdent>KMDW</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan></SimBase.Document> The difference is in the first line. The other difference I see is the section ICAOregion. I tried both UTF-8 and a standard win XP encoding, no difference. What I do see that has caused errors in the past is a space in the starting position between D and 2. I took it out but I still get an RC crash on loading it. I'll have to dig deeper. You can try starting RC and then setting the debug on before loading your flight plan. I tried that and it bailed out just after reading the OAK VOR waypoint on looking at rcv4.log in wordpad.
February 10, 201412 yr Author Hi ronize, Thanks again! The error I got when loading .pln should be Invalid procedure call. I tried your flight plan and it works, unfortunately I do not own FSBuild, tried to laod exported flight plan from PFPX but came up with the same error. Below debug log from laoding ,pln created by FSX planner,I'm not sure how to read it so would you take a look for me please. Thank you! debug onRC Version 4.3.3845 June 6, 2006C:\Program Files (x86)\rcv4x\rcv4.exe<fs2kplanner> C:\Users\LEE\Documents\Flight Simulator X Files\IFR San Francisco Intl to Los Angeles Intl.PLN=================================================================================================================================================================================嚜??xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KSFO to KLAX</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>32000</CruisingAlt> <DepartureID>KSFO</DepartureID> <DepartureLLA>N37* 37' 0.37",W122* 22' 55.52",+000013.00</DepartureLLA>
February 11, 201412 yr Commercial Member are you running a non english version of windows. rc does not run on DBCS languages, such as chinese, japanese, korean, etc. jd JD Read my blog
February 11, 201412 yr Author Hi JD, Thank you for your reply, I just pm you, please check your message. Thanks!
February 12, 201412 yr jd does not view PMs via the forum. He requests e-mail at jd_at_jdtllc.com (replace the _at_ with @). You can put a link in your e-mail to this thread if you like. Be sure jdtllc.com is allowed through your spam filters. Thanks.
Create an account or sign in to comment