falconno

Hi Steve.1. To get these new approaches available in ATC you have to decompile, edit and recompile an internal FS bgl file, for EGPE this would be AP946110.BGL located in FS9SceneryEURWscenery. This is a lot more complicated work, but it's possible. Please refer to the BGLCOMP SDK for further info on how to code this.You have to do this also to get the new approaches available in the ordinary FS GPS and for any AI traffic in the area.2. I believe this is due to the differene in magnetic variation in FS and real world

John,The FMC in this NG reads it's data from the airac files(and thus updated), and the NAV radios read data from the old bgl/scenery files in FS9, unless you have any updated add-on scenery or Afcad with the ILS transmitters included.However there is an easy and quick solution. In AFCAD you can insert the missing ILS transmitters at the correct positions and save. Then you will have full ILS and correct DME readout.I played around with this and if you want you can try the new Afcad file attached. I have inserted ILS at both rwy 05 and 23, edited the rwy designators and start locations, inserted the IVR NDB and done some other small adjustment. Both the I-DX (23) and I-LN (05) DME's should read zero at rwy thresholds as per charts.At glideslope capture rwy 23:http://forums.avsim.net/user_files/148932.jpgThese new navaids are also available in other aircrafts. If you have FSNavigator, remember to run the FSNAVDBC to update the database.

>how do I tie in the rwy to a STAR and does this not>conflict with the approach RWY selection or do you end up with>a mess on the legs page to sort out later?>Steve, If you write in the rwy at the end of the STAR syntax, that rwy will be tied to the STAR and you will get the warning message as described above. It's that conflict that will trigger this message. Here's an example: The syntax:"STAR AND.4L NAVAID AND NAVAID D220S AT OR ABOVE 5500 NAVAID D034X NAVAID D204Q NAVAID D190O NAVAID CI01 AT OR ABOVE 5000 RNW 01"If I now select the "ILS.19" approach first and then the AND.4L I'll be presented with this message:http://forums.avsim.net/user_files/147910.jpgAnother workaround "trick" to sort the STAR's is to write the star procedure as STAR transitions. Start the coding with something like: STAR RWY.07... and then write the actual stars for that rwy as transitions. Not rw realistic, but it may help in sorting out the correct procedure for a given rwy.http://forums.avsim.net/user_files/147911.jpgThe code for this:"STAR RNAV.07 NAVAID GOKSI AT OR ABOVE 3200 TRANSITION SOVIG1G NAVAID SOVIG NAVAID AL801 AT OR ABOVE 6000 NAVAID NERLO AT OR ABOVE 4000 NAVAID RUNAD TRANSITION TUVUG1G NAVAID TUVIG NAVAID VETIG AT OR ABOVE 12000 NAVAID AL803 AT OR ABOVE 7000 NAVAID AL802 AT OR ABOVE 6000 NAVAID PILEM AT OR ABOVE 4500 NAVAID RUNAD AT OR ABOVE 3200RNW 07"When you select the "RNAV.07" you will be presented with the star names as transitions. The end result on the FMC legs page will be the same as if your wrote it as a straight forward star syntax. Also here you'll get the "ARR N/A FOR RUNWAY" warning if the rwy is listed at the end.

Steve,You are correct about the listing if runway specific STAR's. However if you code the runway into the procedure, you'll get a "ARR N/A FOR RUNWAY" warning message if you select a STAR not specific to the selected approach. (That is if you select the rwy before the STAR).Besides that I guess we have to wait for the -NGX version for any updates or modifications to the FMC.

You can find current SID/STAR/IAP procedures for LEBL at Navdata. Also be sure to have the latest available AIRAC installed, also from Navdata.

Adrian,The above mentioned document will supply you with all needed info to get started with procedure creation. I also recommend that you take look over at Navdata to check which airports that already have been written in the UK. I know Simon Butler has done a lot of high quality procedures for the UK among others which he also updates on a regular basis. For further background and info also take a look at the forum at Navdata and Terry Yingling's "Terminal Procedures Forum" here at Avsim.Good luck with the writing:-)

Adam,You may head over to fmcguide.com here: http://www.fmcguide.com/support.htmlAs a starter download the pdf document called "737 profiles". Take a look from page 6. Maybe this will get you on track for some nifty approaches. The other content is also very useful.

You'll find answers for both in your (FS9)../FMCWP/NAVDATA folder. This folder should contain 6 txt files.

Giorgio,do as Damian wrote in the first post here.1. Run the unwrapper you downloaded WITH ASV installed. I verified OK, the unwrapper installs a normal setup file. This is the ASv6 full installer.2. Now you can go ahead and uninstall ASV as described earlier3. Then run the setup file (the ASv6 full install) that the unwrapper made for you4. Set up ASv6 according the manual, and then, ENJOY. Fantastic software!

Andrew,You'll find current SID/STAR/IAP for EGLL at Navdata.at. Look under SID/STAR--Download, change to PMDG 737NG. Both the PMDG 737NG and the 747 use the same files.

Edmundo,FYI, all sorts of decimals functions ok at least for me.Have you tried to remove/uninstall the RXP gauges, then delete the FS9.cfg and restart both FS9 and the machine?

Hi EdmundoI guess you're asking me? If so, no I don't have any RXP gauges installed. And I have done quite some testing on this furthermore, but for me all VOR needles and DME show up when supposed to, I cannot replicate this issue on my system. I have also checked several times now in and around the EGLL area, with and without SB3, and it worked ok for me. The only thing I noticed was that one VOR disappeared for a very short moment when I connected to Vatsim, but that was 1 sec max befor it reappeared. Just as a note about SB3, I don't have the sb3gaugebridge.dll on my system, maybe that's because I haven't installed the latest version 3.0.4, I have 3.0.3.Lefteris, if you see this post, I have one question in regards to navradio's and FMC:I know that in the NG the FMC gets its navdata from the airac files, while the nav radios (including dme's, course deviation indicator) reads from the FS bgl's. I've saw one post from Matts J where he commented that this logic may have changed in the 747, Can you enlighten us on this? May be worth to know how bgl's/afcad affect these things in the 747 too.

Chris,I tested this yesterday, and I get the VOR needles and DME reading on the stations in question here in the 747 without loading the 737 first. The left picture is taken at the gate at LGAV:http://forums.avsim.net/user_files/134865.jpg

Vincent,I don't know how you loaded up the plane, but have you properly executed the whole IRS align prosess according to the manual? Also remember to execute the SET IRS POSITION in the FMC during the process. The align process will take some time to finish based on the setting in the PMDG options menu, and when finished, you must turn the IRS switches back to NAV position(all 3 of them). And of course, all this must be done on ground when not moving.

Hi all,The thread starter didn't mention which aircraft he's flying, and there may be some differencies. But for the 737NG:LNAV criteria on ground: - origin runway in flight plan - active route entered in FMC - track of first leg within 5 deg of runway heading - LNAV selected prior to TO/GA. Once TO/GA is engaged, the LNAV switch light is extinguished until 400ft AGL; * LNAV guidance becomes active at 50ft AGL * bank angle is limited to 8 deg below 200 ft and 30 deg above 200 ft AGLLNAV criteria in flight: - active route entered in FMC - within 3 NM of active route, LNAV engagement occurs with any airplane hdg - outside 3 NM the airplane must: *be on intercept course of 90 deg or less *intercept route segment before active waypoint

MRAI installer files needs to have a comment attached in the zip in order to work correctly. If a MRAI format file is uploaded to Avsim "as is" without beeing zipped to a 2nd level as mentioned above, this comment will be erased, and an Avsim comment will automatically be inserted.What you can do is to open the MRAI zip, go into Actions, Comment, and insert the following:MRAI Release FileThen save and close. If not any other errors, the installer should work ok.

Hi.FYI, there are already quite a number of addon sceneries(both freeware and payware) that have this feature with frequency controlled lighting for runway lights, approach lights, strobes etc.

>Despite updating my FS9/PMDG/SidStars folder per instuctions>with the latest Airac 0511 data my display on the FMC is>showing Airac 0506.>>GSNo, that's not correct install procedure. Airac should not install into the FS9/PMDG/SidStars folder. Here's a quicky routine:1. Download latest AIRAC 0511 for PMDG from Navdata. As this is an installer exe, just select your FS9 root folder and run the installer. The files will then automatically be installed into your (FS9)/FMCWP/Navdata folder. (6 files dated 11/1/2005 for the current Airac)2. Download PMDG_Procedures_0511 from Terry Yingling's site here: http://planepath.com/html/pmdg.html. This is a zip file with the SID/STAR/IAP files. Extract the zip into your FS9/PMDG/SidStars folder.(ABout 1640 files)This is the base setup to get you up and running with the current Airac and procedures.3. Eventually you may download user-made SID/STAR/IAP from Navdata, preferably the "All-in-one" file for PMDG. Unzip these files into your FS9/PMDG/SidStars folder and overwrite. (About 530 files files)This install procedure is the same for both the 737NG and the 747, they use the same files.And GS, please sign your posts with your real name!!

Chris,as mentioned above, at Navdata, under SID/STARS for PMDG. Download the single file for EGLL, OR the "All-in-one" with all files available there (about 530 airports)May I also bring up this thread again by Terry Yingling in regards to this issue: http://forums.avsim.net/dcboard.php?az=sho..._id=7&mode=full

Thanks for the update and for your hard work and contribution. This is an excellent module!!

Christopher,take a look at the Navdata site, under charts, there are plenty of links to different sources. Most Vatsim ot IVAO country divisions will also have a chart section.

Jonathan,There may be other reasons, but there is an issue with the AFDS under certain circumstances stops commanding correct pitch. Recycling of VNAV will help in these situations.Take a look at this thread and see if this applies to your scenario:http://forums.avsim.net/dcboard.php?az=sho...64686&mode=full

>And, can you please check your FMC DB for Rwy22ILS freq at>EHBK? On my pc it doesn't match FS9 freq (108.50) :-(Luigi,The reason for the difference between the FMC db and FS9 freq is probably due to real world AIP changes. The FMC retrieve it's data from the AIRAC cycle (in this case the wpNavAPT file), and the NAV radios(and the DME readout, VOR needle and course deviation indicator)are reading from FS9 bgl files which contain old data. And as you know the AIRAC cycle are up to date.Unless you have an add-on scenery that holds the new ILS frequency, there is another workaround; Open up EHBK in Afcad and change the ILS frequency to 111.55 and save(you can't change the identifier though). Then the FMC and the NAV radios should be "in sync".

I guess you mean the All-in-one file with the SID/STAR/IAP procedures. Unzip the content to your (FS9)/PMDG/SIDSTARS folder, and let them eventually overwrite what's already in there. You may also refer to the following thread for recommended installation routines and background: http://forums.avsim.net/dcboard.php?az=sho...id=66852&page=2

Clayton and Glen,The intsc FIKUL , CHOOK and SAILA you get in the FMC are in the US. The ones that you need for ROONY3 arrival procedure at YBCG are not present in the database, for an unknown reason, that's why you get those extreme distances. According to the chart for ROONY3 arrival at YBCG these intsc have the same names as those in the US (not uncommon that this happen).Over at Navdata you can download a sid/star file for YBCG (either as single or as apart of the AIO). This file has these necessary intsc specified as fixes with the correct lat/long, and thus will override the ones in the database. Seems that all procedures for YBCG are present and working.