Hi Michael.

Have you ever looked at the Navigraph AIRAC data? It is a list of names of fixes/intersections/airports etc. followed by the Longitude and Latitude coordinates.

This is a small snippet from the fixes.db in FSX\Captain_Sim\navigation folder:

HORSH;-37.726667;144.848334;2
HORSI;64.734603;-154.320900;2
HORST;39.402492;-108.014297;2
HORSY;35.319681;-101.653511;3
HORTA;21.799167;-101.568611;1
HORTA;40.660472;-3.286333;3
HORTE;44.217425;-123.398761;2

So I would say that you are correct in saying that it is the coordinates that the FMC is looking at and not the actual waypoint name.

Mark

I completed a flight from KRSW to KTPA with an autoland using only GPS coordinates rather than named fixes. The standard routing from Ft Meyers to Tampa including origin and destination would be KRSW ERRIN V35 CARIR KTPA. I obtained the coordinates from this site http://skyvector.com/ by using FAA IFR Enroute Low Altitude - U.S. charts. If you put the mouse pointer on top of the waypoint and right click the GPS coordinates will appear on the screen. I have attached two images. The first one is of the CDU when entering the waypoints. The second one is of the HSI about 50 mile south of Tampa. I don't think the second image was attached.

Michael Cubine

Hi,

I just noticed that the FMS ignores the turn direction specified in VI (heading to intercept) type of legs. I have checked the Navigraph-supplied navdata and it is correct.

I'll give you an example based on departure PORTE3 from KSFO runway 01L.

Excerpt from the chart:



After takeoff, the aircraft is instructed to climb to an altitude of 411 ft on heading 012, then it should fly 4 NM on 350 (Navigraph has coded this DME fix as waypoint SEPDY) and at 4 NM, a left turn to heading 200 should be made and flown until PYE radial 135, whichafter another left turn is made towards PORTE.

Here's how 757's FMS displays the procedure:



Corresponding entries in sids.db are as follows:
Quote:


As you can see, the VI leg allows left turns only.

Hi fuzzy11

I suggest you do the 757 FMC Tutorial (by aussie) HERE so you can get a feel for what is required when using the FMC. Going by this and you other post, you might have missed something.

So, I thought I'd try a climb 2.   I set the usual EPR/LNAV/VNAV.  It only climbed at 1500 FPM and around 160 knots.
I mostly use a Cost Index of between 20 and 100. The higher the number the faster the flight and the more fuel it will use. I never touch those buttons as the FMC controls the engines. I'm not good at Flex takeoffs, so most of my flights are done using TO/GA, CLB and, CRZ always controlled by the FMC and never by me.

Practice...practice...Practice...practice...
Yep! That is certainly how you learn.

Mark

I tried this flight just now and I think you might have left out something. Probably the TRANS listed under the RWY you selected to land on.

I chose KJFK 04L MERIT3 - DIRECT ORW - ORW3.ORW - ILS04R WINNI for the flight and it went fine.

Mark

Today, I flew this FP

[flightplan]
title=KJFK to EGLL
description=KJFK, EGLL
type = IFR
routetype = 3
cruising_altitude=0
departure_id=KJFK, N40* 38.39', W73* 46.74', +000013.00
destination_id=EGLL, N51* 28.65', W0* 27.68', +000080.00
departure_name=New_York_John_F_Kennedy_Intl
destination_name=Heathrow
waypoint.0=KJFK, A, N40* 38.39', W073* 46.74', +000000.00,
waypoint.1=BETTE, I, N40* 33.55', W073* 00.70', +000000.00, BETTE3
waypoint.2=ACK, V, N41* 16.91', W070* 01.60', +000000.00, BETTE3
waypoint.3=BETTE, I, N40* 33.55', W073* 00.70', +000000.00,
waypoint.4=ACK, V, N41* 16.91', W070* 01.60', +000000.00,
waypoint.5=KANNI, I, N42* 38.00', W067* 00.00', +000000.00,
waypoint.6=NANSO, I, N44* 29.33', W056* 04.27', +000000.00, N31E
waypoint.7=RAFIN, I, N44* 53.00', W051* 48.28', +000000.00, N31E
waypoint.8=VODOR, I, N44* 56.20', W051* 00.00', +000000.00,
waypoint.9=4500N 05000W, I, N45* 00.00', W050* 00.00', +000000.00,
waypoint.10=4600N 04000W, I, N46* 00.00', W040* 00.00', +000000.00,
waypoint.11=4800N 03000W, I, N48* 00.00', W030* 00.00', +000000.00,
waypoint.12=5000N 02000W, I, N50* 00.00', W020* 00.00', +000000.00,
waypoint.13=DINIM, I, N51* 00.00', W015* 00.00', +000000.00,
waypoint.14=ELSOX, I, N51* 00.00', W014* 00.00', +000000.00,
waypoint.15=EVRIN, I, N51* 46.93', W006* 33.80', +000000.00,
waypoint.16=NEKAP, I, N51* 43.58', W005* 17.43', +000000.00, UL607
waypoint.17=ABDUK, I, N51* 38.57', W003* 48.02', +000000.00, UL607
waypoint.18=NUMPO, I, N51* 36.60', W003* 17.02', +000000.00, UL607
waypoint.19=OKESI, I, N51* 26.60', W002* 03.70', +000000.00, UL607
waypoint.20=BEDEK, I, N51* 22.25', W001* 33.52', +000000.00, UL607
waypoint.21=EGLL, A, N51* 28.65', W000* 27.68', +000000.00,


As I got to about 1,500 miles, I hit dep/arr and  I selected BIG1E (if I recall) and 27L.  I also selected BIG as transition.  I fussed for quite some time as the route had all sorts of U-Turns that did not look right. 

As I got close enough to start down it, all of a sudden it stopped following the route and just kept going straight.  I double checked VNAV and a/p were connected, next waypoint was BIG/303, if I recall.  Of course, I was somehow heading 279 (a full turn).  I forgot to mention that I had stepped away west of the field, so maybe there was something that happened...  Before BIG/303, I tried deleting a waypoiint, and going to BIG/303, but it would not go anywhere, other than straight ahead.  I then disconnected ap and proceeded to do visual approach to finish the flight.

I do believe that CS Support is right on this one. Although I can't see the image, I suspect that you activation has failed!

Did you install the 757-200 Base Pack using the "Run as administrator" option? This is done by right clicking on the installer (csp751_4600.exe) and select Run as administrator from the list (2nd from the top).


It might also be worth using the Manual Offline Activation. This can often fix these activation problems.

Note: We probably can't see the image because we are not on your friend list on Facebook. Try adding the [ img ] [ /img ] (without the spaces) markers to the image link, so it might show up in the post.

I have Windows 7 Professional 64bit (C:\Windows) and FSX on a separate HDD (J:\Flight Simulator X). The installers should know where FSX is installed, unless you moved it to another HDD/partition without changing the registry.

There is no support email address. All official support is done using the Ticket System.

Are all the other gauges in the VC visible (no blacked out)? Does the 752 have landing gear (landing gear is not missing)?

Is you FSX FSX with SP2 or FSX with Acceleration? Depending on that answer, maybe you should do a repair of FSX and reinstall SP1 and SP2. OR. Do a repair of FSX and a repair of Acceleration. It might be that FSX is the problem and not the Captain Sim 757-200 Base Pack installation. This would especially be the case if the landing gear IS visible and the other gauges are NOT blacked out.

As far as I can remember, FSUIPC is no longer a requirement for the 757 Captain.