falconno

Yes, you have ;). The PMDG NGX FMC doesn't have this option. I only made a suggestion for future developement of the FMC. That said, some real NG aircraft has this function(company specific) or more precicely, a REQUEST button for winds uplink (page 1047 in FCOMv2). For FS purposes, it would be nice to have this function/option coded to retreive winds info for your route waypoints from a weather generator such as Active Sky etc. Per

Some further info on issue. 1. I tried trisager's route again and the same happened this time too:This picture shows cruise wind info 294/13 for waypoint MONTO entered in the scrathpad: (So far so good) When I hit LSK 3R this happens...The info disappears. Also all entries on the other pages are lost. I then hit the EXEC button (it didn't light up though): The PERF INIT page also misses some info.. When this happens and you try to enter something in the scratchpad, it will not show up at all. If you then select another page, the entered numbers in the scrathpad reappears. 2. I also tried the route a third time, but this time just entered cruise wind info just for 1 waypoint on RTE DATA page 6. Then cruise wind info for 1 waypoint on page 8 and then the FMC locked up again. Average crz wind was entered first on the PERF INIT page. 3. If needed, I have the route in .rte format and the navlog with crz wind info I used. 4. Just want to add that I have flown the NGX on several shorter routes with less waypoints(2 - 6 pages with complete cruise wind info) without any issues at all. So this only seems to happen when crz wind info are entered on longer routes with a lot of waypoints(8+ pages). 5. I know PMDG said that nothing need to be fixed, changed etc..and also garbage in=garbage out. I can agree with that, but can someone confirm that this is per functionality? If so, what are we doing wrong here? Per.

George, as I tried to explain in my post #8 and #12, everything worked as expected for me in these examples. Then I tried trisager's route. Take a look at post #7 by 'trisager' and my post #14 in this thread. The same issue happened to me when I tried to input cruise wind data. The first 5 pages went ok. Then on page 6 the FMC locked up as mentioned. The FMC refused to accept any more wind entries. And as 'trisager' said: 'At this point existing cruise winds are also lost, and there is also information missing in the right CDU column if I go back to the LEGS page' So my re-phrased question is: Is this per functionality of the FMC? Is there any limit here on number of cruise winds entries? Per

Personally I know that :) as I stated. And I also tried to explain the procedure in my other posts here.But if I may ask, does this also mean that the FMC have some limit on the number of waypoints it will accept cruise wind data as we found in the example above? I know the man said garbage in = garbage out, but I can't figure out the garbage here. Per

I'm sorry for the misunderstanding, my fault.. Thanks emvaos for the explanation of some of the modelling here, very interesting indeed! As for the lock up of the ACT RTE DATA pages as 'trisager' and I found, maybe someone could test this further? Per

Hmm, about the descent phase, what makes you think this is something that PMDG needs to fix? Isn't this modelled as in real life? Personally I think this is correct.For my route:I made a route with FSBuild from ENVA to LHBP and fetched weather data from Active Sky for the particular route and waypoints. Winds data was entered on the ground and EXEC'uted after each entry(I think)..For the remaining pages, some individual entries if needed and the rest 'propagated'. This worked for me.BUT, I tried your route, EKCH BISTA T503 GIMRU UT503 MIC UZ707 FAMEN UZ707 BSN UZ707 RESMI UN857 TERTO GCLP, generated it with FSBuild and imported to Active Sky. Entered average route wind on the PERF INIT first, then entered correct wind info for each waypoint needed as per the navlog.When I was on the 6th page, the FMC locked up and all info of winds and RTE data was lost, no chance to make new entries. Strange, probably the same issue as for you. Per

I'm not sure if this is a problem, as far as I know (2) is as the 'real thing'. Descent winds should be entered in the DES FORECASTS page. As for (1), I just tried to rebuild a route with 6 pages of cruise waypoints. I could easily enter cruise winds into every waypoint, se pic below. (This reminds to suggest an UPLINK function with winds data from a flight plan/navlog such as in Active Sky, as in RL, hint,hint:)) Per

Take a look at page 1046 in FCOMv2 "Route and Waypoint Data". The RTE DATA page displays forecast wind data for cruise waypoints. The cruise wind data entered in the PERF INIT page (page 942 in the manual), will be propagated here. If you have exact data for each waypoint, this can also be entered here on the RTE DATA page, but only for cruise waypoints!Take a look at page 1084 in FCOMv2 for the DES FORECASTS page entries. Vital for correct descent path calculation. Personally I use Active Sky and FSBuild together for collecting waypoints wind data for both cruise waypoints and to enter forecast data for pre-descent planning. Per

Jonathan, you're correct, this is how the FMC in the sim works. If you enter wind info into one waypoint, this info will propagate into remaining enroute wp's. Of course, you can finetune every single waypoint afterwards to suit your needs if you like. What I usually do for shorter trips, is to enter average winds info from Active Sky into 'CRZ WIND' at the 'PERF INIT' page, and eventually insert greater changes for specific waypoints if needed. On longer trips, I tend enter as much info as possible from AS into RTE DATA, as winds changes can be quite significant on longer trips. It take some time, but I like to get as real as possible, that's my way to do it. Lazy real world drivers have ACARS to do the dirty work for them :)

Search for 'ttcomp20.zip' and the update 'ttcomp21.zip' in the library.

As the FMC do not allow an entry of the overfly command, you may also try to cheat a little to get the desired effect while you are in flight. You do this by entering an ATW (Along Track Waypoint) in the FMC very close to the waypoint in question.Downselect HOLLY to the scratchpad, then enter HOLLY/0.1, then click on HOLLY again. This will create a waypoint 0.1NM after HOLLY and will force the aircraft to wait with the turn. You can also try HOLLY/-0.1, then the new wp will be created just before HOLLY.Bear in mind that I'm not familiar with this exact procedure at Gatwick, so you may try with other settings to get the desired effect.

Hi RichardI have tested CIV4H at EBBR. and it must be something wrong in the source data here. When heading 277 (after reaching 1700ft) there's no way you can intercept the BUB 224 radial, that's a complete different direction. So I assume it must be intercepting radial 224 from CIV. Then the string will be something like this according to the chart:SID CIV4H RNW 07L TRK 066 UNTIL 1700 TRK 277 INTERCEPT RADIAL 044 FROM NAVAID CIV NAVAID CIVorSID CIV4H RNW 07L TRK 066 UNTIL 1700 TRK 277 INTERCEPT RADIAL 244 TO NAVAID CIV NAVAID CIVEDIT: I see that many others came to the same conclusion below, didn't update the browser after testing/posting

I can also highly recommend kaitak98 scenery by Jim Vile available in the library as kaitak98.zip. It's without any framerate hogging eye-candy's, easy on framerate. User aircrafts will have all approach options through ATC and GPS under both VMC and IMC conditions too.Jim has even coded and compiled the scenery so that AI aircrafts will follow the full IGS/LDA Precision Approach and operate under both VMC and IMC airport conditions for AI Planes.The zip also include charts, AI flight plans, simple mesh files and an option to remove VHHH. Remember to read the documentation carefully.Together with Steve's SID/STAR data in this thread, fire up your PMDG 747 and be ready for some challenging approaches!

>The only way you can fly EHAM is to buy and use the addon scenery>by Cloud 9. I just avoid the airport.>>AnthonyOf course not. There are enough freeware alternatives available if you don't want to go payware. But you definetively need a good Afcad file. The easiest and cheapest way is to download a decent Afcad or freeware scenery at Avsim. Do a search in the library for Jim Vile or Peter Bos. They have compiled quality Afcad sceneries for EHAM. I just did an succesfull approach into 18R at EHAM with the 737 with one of these.

Hi Qas.As Mats says, you need to have charts for departure to determine which SID to choose. There are several SIDs for each runway depending on the direction for your flight. The BPK sids (in this case BPK6G as you are at 27L) are used more for east/northbound flight (as via airways M185 and L620). BPK6G is definetively not good for southbound to LEBL as you tried. Try instead MID3G or SAM2G for southbound flights from 27L to an appropriate airway from the procedure end at Midhurst (MID) or Southampton (SAM). And for the record, the procedure for EGLL made by Simon Butler is of top quality and always up to date (and for that matter all of his proedure files).I will also recommend Eurocontrol for all European charts. For UK you also have an option at http://www.ais.org.uk/

Hmm, strange, I remeber there was something with the decimals in the NDB frequencies in 0610, but I can't say I have seen this. Sorry I can't help you more but here's is how this page is for me with 0612 anyway:http://forums.avsim.net/user_files/162711.jpgEDIT: FYI, I did a quick check with the 0611 files installed, and I didn't get those strange text strings.

Pedro,to get the FMC to draw a green line you have to insert a radial on the FIX page. The FMC will also then calculate the distance to your route. You can also insert this point into your flightplan if needed. In the picture below you can see what I mean. On LSK2R and 3R I have inserted two differnt radials and also auto-generated the abeam point by clicking on LSK5R. I think the FMC will generate the closest point when clicking on ABEAM both radial and dist, at least it does here in the sim. http://forums.avsim.net/user_files/162270.jpgHere's just the ABEAM point in the flightplan:http://forums.avsim.net/user_files/162271.jpgThis works exactly the same in the 747 (sim, that is:))

Guys, remember that VTBS must be present in the AIRAC files (the data file present in ...(FS9)/FMCPWP/Navdata/wpNavAPT.txt) in order to show up regardless of which prosedure file you have. Jackson (or whatever your name is), if you have the current procedure file, this may look like you don't have an AIRAC with VTBS in it. As suggested, check the IDENT page for which airac cycle you have.

I would recommend you to use the procedure file for EGSS from Navdata written by Simon Butler. This file is also up-to-date and working with current AIRAC cycle. All Simon's files are of high quality and always checked and updated.

You can find charts for VTBS here: http://www.aerothai.co.th/thai/orat/2_operation.php

Tord, do you mean this one, pmdg747_advancedtutorial.zip by Holger Seilz in the library? A good one anyway..

AIRAC 0605 version is obviously missing quite an amount of waypoints around. As Richard Stefan has stated we may consider this as a test version until everything is up and running again. Now for UUEE you may go back to AIRAC 0513 as this was the last stable version, OR you could d/l the earlier version 1 of the UUEE procedures(my own) at Navdata, as it still works with 0605(I havent't updated it after the other guy overwrote it). I guess these issues will be present in 0606 also as it is already done, and Richard is on holiday. But I'm sure he will sort these things out sooner or later, he's making a wonderful service for us simmers.

Owen, there is an export module available for PMDG at the FSNav site. This will export your flightplans directly to rte format from FSNavigator(the doc says).

Hi MartinI guess you have the KMCO file by Dan Downs. If you open the file in Notepad, you'll find instructions on how to get this to work. You have to edit and add some info into the wpNavAID.txt. Then KMCO will be fine in the FMC. I guess this info will be included when a new AIRAC arrives.You probably know this, but in order to actually use the new runways and get the NAV radios to work, you must have an add-on scenery or Afcad file reflecting the current rwy's and navaid info.

Glad it worked for you John:-) Steve, that's easy, open the stock Afcad for the airport and right-click in the window, the Properties tab will tell you.. If you want to go further into this, do a search for "XML Approaches" at the Project AI forums. There is a wealth of useful info there, especially by Jim Vile who has done a extensive research on the subject.