Jump to content

Sign in to follow this  
Nigge

Strange waypoints when getting closer to an airport

Recommended Posts

HiI have a quite annoying problem with RC4, I have browsed throught the posted messages in this forum and cant seem to find the answer anywhere so ill try.When im getting closer to my destination airport radar contact says that my next point is in a different direction and lika 8500 nm away...It


Niklas Eriksson

Share this post


Link to post
Share on other sites

Hi Niklas,It sounds like FSBuild may be selecting the wrong waypoint as RC4 only uses the lat/lon for each waypoint in the plan to determine the distance and heading.Some time ago there were two CONGA waypoints - one in Cheshire, England and the other somewhere in the US so if the wrong one was selected it would result in the kind of problem you're experiencing.Can you paste your plan here?


Ray (Cheshire, England).
System: P3D v5.2 & v3.4, Intel i7-8086K o/c to 5.2Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Hi, thanks for your reply, this happens almost everytime i fly...no matter what the route is,but the route that it happened last with is thisNZAA OT H436 WI H277 AA N774 SHARK YSSY(I excluded the NZAA and YSSY in FSBUILD of course)


Niklas Eriksson

Share this post


Link to post
Share on other sites

Something is very wrong if it's happening with every flight. Can you paste the actual plan here so we can see the lat/lon for each waypoint? I need to see what info you gave to RC. Open it with Notepad and do a copy/paste please.


Ray (Cheshire, England).
System: P3D v5.2 & v3.4, Intel i7-8086K o/c to 5.2Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Of course, here is the contect of the file that got exported from FSBUILD2And before i paste it, many huge thanks for you taking your time to help!!; ----------------------------------------------------------------------; Generated by Fsbuild 2.X for Radar Contact 2; ----------------------------------------------------------------------ARRIVAL_ID = "YSSY"HOLD_ID = "SHARK"DEPARTURE_ID = "NZAA"; ----------------------------------------------------------------------; Begin Nav Generated variables; ----------------------------------------------------------------------GET_FLIGHT_PLAN: Title "!RC NZAA to YSSY (filename: NZAA-YSSY.apl)" Description "AUCKLAND_INTL to SYDNEY_INTERNATIONAL" Description "Generated by Fsbuild 2.X" flight_planner = 13 filed_altitude = 3900 departure_elevation = 23 arrival_elevation = 21 number_of_checkpoints = 12 departure_latitude = -37.007900 departure_longitude = 174.791800 arrival_latitude = -33.940900 arrival_longitude = 151.170900 checkpoint_1_latitude = -37.060400 checkpoint_1_longitude = 174.609500 checkpoint_1_altitude = 200 checkpoint_1_heading = 125 checkpoint_1_freq = 0398.0 checkpoint_2_latitude = -37.267600 checkpoint_2_longitude = 174.814000 checkpoint_2_altitude = 500 checkpoint_2_heading = 341 checkpoint_2_freq = 0254.0 checkpoint_3_latitude = -37.004500 checkpoint_3_longitude = 174.813700 checkpoint_3_altitude = 800 checkpoint_3_heading = 260 checkpoint_3_freq = 114.80 checkpoint_4_latitude = -36.384500 checkpoint_4_longitude = 170.740700 checkpoint_4_altitude = 3900 checkpoint_4_heading = 257 checkpoint_5_latitude = -35.914800 checkpoint_5_longitude = 165.229500 checkpoint_5_altitude = 3900 checkpoint_5_heading = 260 checkpoint_6_latitude = -35.650700 checkpoint_6_longitude = 163.000100 checkpoint_6_altitude = 3900 checkpoint_6_heading = 263 checkpoint_7_latitude = -35.558400 checkpoint_7_longitude = 162.297600 checkpoint_7_altitude = 3900 checkpoint_7_heading = 263 checkpoint_8_latitude = -34.375100 checkpoint_8_longitude = 155.164000 checkpoint_8_altitude = 3900 checkpoint_8_heading = 263 checkpoint_9_latitude = -34.269300 checkpoint_9_longitude = 154.165700 checkpoint_9_altitude = 3900 checkpoint_9_heading = 264 checkpoint_10_latitude = -34.082000 checkpoint_10_longitude = 152.565700 checkpoint_10_altitude = 1800 checkpoint_10_heading = 263 d_runway_1_id = 50 d_runway_1_heading = 051 d_runway_1_latitude = -37.016800 d_runway_1_longitude = 174.777300 d_runway_1_altitude = 21 d_runway_2_id = 230 d_runway_2_heading = 231 d_runway_2_latitude = -37.000100 d_runway_2_longitude = 174.809800 d_runway_2_altitude = 21 a_runway_1_id = 70 a_runway_1_heading = 061 a_runway_1_latitude = -33.933400 a_runway_1_longitude = 151.170100 a_runway_1_altitude = 21 a_runway_2_id = 161 a_runway_2_heading = 154 a_runway_2_latitude = -33.950100 a_runway_2_longitude = 151.190100 a_runway_2_altitude = 21 a_runway_3_id = 163 a_runway_3_heading = 155 a_runway_3_latitude = -33.916800 a_runway_3_longitude = 151.172300 a_runway_3_altitude = 21 a_runway_4_id = 250 a_runway_4_heading = 241 a_runway_4_latitude = -33.933400 a_runway_4_longitude = 151.191500 a_runway_4_altitude = 21 a_runway_5_id = 341 a_runway_5_heading = 335 a_runway_5_latitude = -33.950100 a_runway_5_longitude = 151.187300 a_runway_5_altitude = 21 a_runway_6_id = 343 a_runway_6_heading = 334 a_runway_6_latitude = -33.966800 a_runway_6_longitude = 151.199800 a_runway_6_altitude = 21RETURN


Niklas Eriksson

Share this post


Link to post
Share on other sites

Thanks for the file. It looks like a old file format because it mentions RC v2. I believe FSBuild generates plans for FS9/FSX. I suggest you generate one of those and use that instead. I think you'll find your problems disappear.All those runway entries are probably responsible for the problem.


Ray (Cheshire, England).
System: P3D v5.2 & v3.4, Intel i7-8086K o/c to 5.2Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Ah thanks for the help,the problem is that i have got any neat formats to export from fsbuild the choices i have are:767PICACS-GPSFLY! IIFS2000/FS2002(If i choose this one it just says that file cant be created:(FSNAVIGATORGPS98PMDG 777/757PS1PSSA320PSS.ROUTEPSS 747PSS 777SQUAWKBOXX-PLANE FMSRADAR CONTACT 2NAVDATA/REAL CRTAny idea what might be wrong, or if there is another choice that might work?my FSBUILD version is 2.0.0


Niklas Eriksson

Share this post


Link to post
Share on other sites

Looking at the spec for FSBuild the latest version is 2.3 which includes support for FSX. v2.1 supports 2004 so a simple update should solve your problem.I got the info from here http://secure.simmarket.com/product_info.php?products_id=486Hope that helps.


Ray (Cheshire, England).
System: P3D v5.2 & v3.4, Intel i7-8086K o/c to 5.2Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Oki, i baught the new FSbuild, and when i choose FS2004 to export to,it just says "Unable to create Fs2000 file /pilots nzaa-yssy.plnWhat can be wro'ng?:(


Niklas Eriksson

Share this post


Link to post
Share on other sites

I don't have it so I'll ask those in our beta group who use it. I'm sure someone will come back to you soon.


Ray (Cheshire, England).
System: P3D v5.2 & v3.4, Intel i7-8086K o/c to 5.2Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Fortunately, as well as being on the RC beta team, I was also on the FSBuild beta team so I'm sure we can solve your problem.First, as Ray has pointed out, RC4 uses the standard MS FS2000/02/04 .pln format - the Radar Contact format is simply for backward compatibility with RC version 2.The most likely reason you're getting the error message is that you've not correctly set and saved your FS path in FSbuild. Start Fsbuild and in the "Folder Items" window on the left hand side, select "Options". When the options window opens, click on the "Export Directories" tab and set your path to the FS root directory. Then, click on the "Settings" tab and click the "SAVE CONFIG OPTIONS" button. Finally, and this is important, close down and re-open FSBuild for the new options to take effect.Select FS2000/02/04 in the "Export to..." menu then build your plan. Load the resulting file to RC and all should be well.Pete http://www.jdtllc.com/images/rcv4bannerbeta.jpg

Share this post


Link to post
Share on other sites

Did you point to your FS2004 directory on the "Export_Directories" tab under the "Options" item in the tree view? In my screen, the FS2004/FSX option is the first item in the list.Make sure to close and restart FSBuild after changing these options to make sure they are recognized.

Share this post


Link to post
Share on other sites

Thank you very much Pete, that did the tricknow my flightplan looks like this[flightplan]title=NZAA to YSSYdescription=NZAA, YSSYtype=IFRroutetype=3cruising_altitude=24000departure_id=NZAA, S37* 00.28', E174* 47.30',+000023.00departure_position=05destination_id=YSSY, S33* 56.27', E151* 10.15',+000021.00departure_name=AUCKLAND_INTLdestination_name=SYDNEY_INTERNATIONALwaypoint.0=NZAA, A, S37* 00.28', E174* 47.30', +000000.00, waypoint.1=OT, N, S37* 03.37', E174* 36.34', +000000.00, waypoint.2=WI, N, S37* 16.03', E174* 48.50', +000000.00, H277waypoint.3=AA, V, S37* 00.16', E174* 48.49', +000000.00, N774waypoint.4=MADEP, I, S36* 23.04', E170* 44.26', +000000.00, N774waypoint.5=PUGAB, I, S35* 54.53', E165* 13.46', +000000.00, N774waypoint.6=OLREL, I, S35* 39.02', E163* 00.00', +000000.00, N774waypoint.7=WOOLY, I, S35* 33.30', E162* 17.51', +000000.00, N774waypoint.8=MAGDA, I, S34* 22.30', E155* 09.50', +000000.00, N774waypoint.9=MAYOP, I, S34* 16.09', E154* 09.56', +000000.00, N774waypoint.10=SHARK, I, S34* 04.55', E152* 33.56', +000000.00, waypoint.11=YSSY, A, S33* 56.27', E151* 10.15', +000000.00, Looks better than the old one right?


Niklas Eriksson

Share this post


Link to post
Share on other sites

Hi,You do not appear to be running the up to date version of FS Build.The up to date version does not show Radar Contact in its export listing which has been updated.I use FS Build for all of my flight planning needs and I have never encounted your problemsNorman Bowman


Norman Bowman

Share this post


Link to post
Share on other sites

Here is how to set up your export paths. Go into your options tab and in line 1 browse to your FS9 or FSX route folder. Then go to the Settings tab in the same option screen and click on Save Configuration. When you drop down your Export Options FS2002/FS2004 should appear or if using FSX then that should appear. Click on your choice to check it. Do not export to Radar Contact.Screen shots are attached.Regarding routing, there can be errors introduced by AIRAC changes, duplicate IDs, etc. If you wish you can try loading an updated AIRAC from www.fsbuild.com at no charge.After using autoroute and build, look at the route in the map section of the route window and/or look for any strange distances and headings in the route grid table. If there are, highlight the problem line (the waypoint in the map will turn red). Hit the delete key and your chosen line will be gone. After making any changes in the grid, drop down Build Options and click on Build from Route Table so it is checked. (This option must be selected each time you run FSB if you need it). Then click on build again to build and export your route. If you save in FSB format your plan the next time you load it you will have to save perform the same procedure. If the errant waypoint is not part of a SID or STAR which is expanded in the grid table, you might consider eliminating it from the route path window and doing a normal build. If it looks OK then you can save the revised path in FSB and not go through this whole grid editing procedure.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    53%
    $13,405.00 of $25,000.00 Donate Now
×
×
  • Create New...