Jump to content

Archived

This topic is now archived and is closed to further replies.

meccadom

Runtime error 62

Recommended Posts

After upgraded my PC and performing a clean re-install of FSX and and RCv4 I find that I receive this message referring to "get departure information" when attempting to open a flight plan.

 

All databases have been updated and makerwys has been run with the latest version 4.6.1.4. I created a flight plan in FSC v 9.21 with file path for RCv4 pointed to my Users\Documents\Flight Simulator X Files\ location. The .PLN file is there but not the .RC4 file.

 

The entries in r4 and r5 csv appear to be valid, although I do notice that the makerwys text file referred to in an older post in this forum dated November 2010 is not there.

 

Can you offer a solution?

 

Thanks

 

Dom

Share this post


Link to post
Share on other sites

Disregard the .rc4 file. Only the .pln file is used. The .rc4 file contains I believe some modifications made in a controller tab preflight.

 

The runways.txt file, the log of makerws.exe, resides in your FS folder. The r5.csv in your FS folder is copied during the scenery build to the rcv4\data folder as r4.csv and the a4.csv, the airport coordinates file, is built from that r4.csv.

 

The have been cases where FSC and FSX users have had problems with RC. If FSC offers the FSX XML format choose that. In the FS9 format I believe FSC uses extra fields that RC can have problems with as indicated by error-62 (line format problem).

 

In the non-XML format RC wants to see:

 

[flightplan]

title=KMSP to KDLH

description=KMSP, KDLH

type=IFR

routetype=3

cruising_altitude=15000

departure_id=KMSP, N44* 52.55', W093* 13.18',+000841.00

departure_position=4

destination_id=KDLH, N46* 50.31', W092* 11.37',+001428.00

departure_name=MINNEAPOLIS-ST_PAUL_INTL

destination_name=DULUTH_INTL

waypoint.0=KMSP, A, N44* 52.55', W093* 13.18', +000000.00,

waypoint.1=GEP, V, N45* 08.44', W093* 22.23', +09000.00,

waypoint.2=RZN, V, N45* 49.13', W092* 22.28', +15000.00,

waypoint.3=KDLH, A, N46* 50.31', W092* 11.37', +01428.00,

 

as a simple option. Altitudes are not used. After "waypoint.n=" should be one ICAO code followed by the waypoint type, then coordinates and the optional altitude. Check you .pln in notepad or wordpad.

 

The FS9 format above will work in FSX as well. An FSX XML format .pln looks like this:

 

<?xml version="1.0" encoding="Windows-1252"?>

 

<SimBase.Document Type="AceXML" version="1,0">

<Descr>AceXML Document</Descr>

<FlightPlan.FlightPlan>

<Title>EKCH to ESGP</Title>

<FPType>IFR</FPType>

<RouteType>HighAlt</RouteType>

<CruisingAlt>34000</CruisingAlt>

<DepartureID>EKCH</DepartureID>

<DepartureLLA>N55° 37' 04.00" , E12° 39' 21.00",</DepartureLLA>

<DestinationID>ESGP</DestinationID>

<DestinationLLA>N57° 46' 32.00" , E11° 52' 14.00",</DestinationLLA>

<Descr>EKCH, ESGP</Descr>

<DeparturePosition>04R</DeparturePosition>

<DepartureName>KASTRUP</DepartureName>

<DestinationName>SAVE_AB</DestinationName>

<AppVersion>

<AppVersionMajor>10</AppVersionMajor>

<AppVersionBuild>60905</AppVersionBuild>

</AppVersion>

<ATCWaypoint id="EKCH">

<ATCWaypointType>Airport</ATCWaypointType>

<WorldPosition>N55° 37' 04.00",E12° 39' 21.00",</WorldPosition>

<ICAO>

<ICAOIdent>EKCH</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="D039C">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N55° 37' 41.00",E12° 40' 17.00",</WorldPosition>

<ICAO>

<ICAOIdent>D039C</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="CH370">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N55° 52' 47.00",E12° 45' 02.00",</WorldPosition>

<ICAO>

<ICAOIdent>CH370</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="NOA">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N56° 06' 20.00",E12° 14' 29.00",</WorldPosition>

<ICAO>

<ICAOIdent>NOA</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="ROKAM">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N56° 19' 00.00",E12° 10' 59.00",</WorldPosition>

<ICAO>

<ICAOIdent>ROKAM</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="VEDAR">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N56° 31' 54.00",E12° 07' 24.00",</WorldPosition>

<ICAO>

<ICAOIdent>VEDAR</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="LASLI">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N56° 55' 42.00",E12° 00' 42.00",</WorldPosition>

<ICAO>

<ICAOIdent>LASLI</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="RISMA">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N57° 02' 30.00",E11° 58' 45.00",</WorldPosition>

<ICAO>

<ICAOIdent>RISMA</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="BAK">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N57° 33' 18.00",E11° 58' 36.00",</WorldPosition>

<ICAO>

<ICAOIdent>BAK</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="ESGP">

<ATCWaypointType>Airport</ATCWaypointType>

<WorldPosition>N57° 46' 32.00",E11° 52' 14.00",</WorldPosition>

<ICAO>

<ICAOIdent>ESGP</ICAOIdent>

</ICAO>

</ATCWaypoint>

</FlightPlan.FlightPlan>

</SimBase.Document>

 

Either works with RC.

 

The sample pln files were created with FSBuild 2.3 or 2.4.

Share this post


Link to post
Share on other sites

make sure you have the latest makerwys.exe installed, and run rcv43, and click the rebuild rc scenery database button

Share this post


Link to post
Share on other sites

Thanks Ronzie and JD. A re-install of RCv4 solved my issues. I had a corrupted previous install in my old FSX folder that I did not removed when I upgraded my PC hardware and drives..

 

So thanks again.

 

Dom

Share this post


Link to post
Share on other sites

×
×
  • Create New...