falconno

Hi there,Yeah, this certainly is weird. If you have installed PMDG_Procedures_0412 from Terry the files you mention for LSGG from 2001 and LSZH from 2003 should not have been there at all. Terry' files contains newer ones for both LSGG and LSZH with his header. Also if you have installed the All-in-one from Navdata on top you should have had completely different ones in your SIDSTARS folder. So one or more installations must be corrupted in some way here if you have followed the correct procedures when installing both AIRAC and the Sid/Star files. It's mentioned before here, but I again recommend you to recheck and verify what Michael described in the #3 post here. Also check Buck Buldoc's tip about duplicate folders. If nothing of this helps I suggest a complete reinstall from scratch, Use PMDG's "Removal Tool" and after that manually scan the Fs9 root folder/your drives for any leftover files/folders and delete them. Restart and run the PMDG installer(s) again, then install the latest AIRAC and the latest PMDG_Procedures. Eventually you can install the "All-in-one" from Navdata on top.

Steele, you are giving us too little info about your FMC setup, dep/dest airports, procedure file origin, etc. First, have you looked at the pinned post here: "SID/STAR/IAPs updates explained. New 737NG owners shou..."? This may give you some further help on installation routines regarding SID/STAR/IAP files and problems that may come up. Have you followed this procedures? If this error message persists, it's most likely an error in the actual SID/STAR/IAP file for your dest airport, at line 75.

I guess he's refering to the "ARINC 424 PROCEDURE TYPE CODES". I think this in real life are defined standards/rules for FMS procedure coding. (Look at this pdf doc, at the bottom: http://www.rockwellcollins.com/fms/viewdoc.asp?doc=280).I also saw this in the FMS format of the new ATR baby from Flight1.How this is implemented in our FMS, I know nothing about. What I know is that the coder (Anthony Merton) has implemented a very easy and straightforward language for us end users to utilize in procedure file writing. No need to worry about this codes when writing.

Yes, it is. A little bit OT. but.. I have been a long time reader on the Pprune forum, and to some extent, they are discussing the very same issues as here on our forum, and with the same solutions! Sometimes I have to look in the header to see which forum I am in...:-) You may also pick up some good tips from the "testosterone jockeys" over there, but mostly the topics that concern us are already well covered in our forum.This also tells me that the PMDG NG is extremely well modelled!

Hi Jason.As Randy described you must engage A/T in order to hold speed. From the pics above I can see the A/T is not engaged. Are you sure you have switched on the engine driven generators on the overhead panel? The GEN1 and GEN2 buses must be connected or the A/T will not engage. (See the manual about "Cockpit and systems" from page 28)

In addition to what Marcus said, the only option you have is to define this in the procedure file, if needed, as an ex: NAVAID OVERFLY XXX. The airplane will then start the turn after passing the XXX navaid.

Hi RogerYes, you can write soft constraints in the procedure file. In this case this will be: NAVAID TOSUS AT OR ABOVE 7800. I suggest that you download Terry Yingling's latest tutorial from the library for further reading on procedure file writing.Remember that if you don't have the -800/900 upgrade installed, soft constraints will be ignored. You can still use the procedures as normal, but any altitude restrictions have to be entered(IF needed) manually in the FMC as a hard conctraint. It's not always a good solution to write a "soft constraint" as a "hard constraint". If you still are within the criteria for the soft constr.(ex. AT OR ABOVE.. ), let the FMC calculate the path instead of writing a hard constraint, and leave out the "hard". Too many hard constraint close to each other may also lead to a VNAV DISCONNECT.

Also make sure you have switched on the generators on the overhead panel, the Gen1 and Gen2 switches.

Hi there.I would agree with Word Not Allowed, HDG SEL seems to be a good option. But if you insist on using LNAV you have some options. To visualize Word Not Allowed's suggestion, here how it's look lik when using existing waypoints:http://forums.avsim.net/user_files/96506.jpgYou can also make your custom waypoints using the BKY VOR as reference:http://forums.avsim.net/user_files/96508.jpgHere I have inserted as follows:BKY160/9.5BKY180/4.5BKY063/12BKY085/15BKY102/11EGSS.As shown below you can use the FIX page as an aid for entering your own wp's.http://forums.avsim.net/user_files/96509.jpg

Hi Roger.1. Your FMC warning most likely says "APPROACH VREF NOT SELECTED". Dave pointed out the correct procedure.2. The second one for your descend is more complicated. I tried the flight many.many times with different settings. I also wrote new procedures with diff alt settings, deleted hard constraints, inserted soft constraints, no constraints at all, deleted the missed approach etc, but every time I get the same behaviour as you. I ran my tests without any speed restrictions.However I tried the procedure from another airport, this time KPSC, and then it works OK. Here the T/D point will be before YDC. Also the YKA transition works OK. I also tried to delete YDC and go direct to TOSUS, and then everything is OK. From your picture it seems that you use the -600/700 base pack and don't have -800/900 installed. I have the -800/900, but my test was done with a -600 VC, 167 NM trip, tried both FL 270 and FL 300. Fuel: 4800 lbs in wing tanks, 1000 lbs in center. Start weight 107824 lbs. Take-off from 07 at CYXX, also tried a flight with intsc YARRO - CILLI before entering the procedure at YDC. No weather add-on, but downloaded fs9 weather for yesterday.Here's my procedure setup: (Note that if you don't have the -800/900 installed, soft constraints will be ignored)add to FIXES section:FIX D14.9 LATLON N 50 12.72 W 119 24.51FIX D8.7 LATLON N 50 06.54 W 119 23.76FIX D5.2 LATLON N 50 03.05 W 119 23.34FIX B141 LATLON N 50 14.58 W 119 30.08add to APPROACHES section:APPROACH ILS.DME.16 FIX D14.9 AT OR ABOVE 5600 FIX D8.7 4400 FIX D5.2 3400 RNW 16 NAVAID EX KEEP TRK INTERCEPT RADIAL 218 TO FIX YWB FIX YWB TRK 211 UNTIL 9000 NAVAID YDC 9000 TRANSITION YDC NAVAID YDC AT OR ABOVE 9000 FIX TOSUS AT OR ABOVE 9000 FIX B141 AT OR ABOVE 7200 FIX WTMAN AT OR ABOVE 6300 The strange behaviour remain with this procedure too.This seems to be triggered by the T/D point just after a turn as here at YDC. There is an issue reported that the FMC under certain criterias may stop commanding pitch correctly, take look at this thread:http://forums.avsim.net/dcboard.phpaz=show_topic&forum=136&topic_id=64686&mode=full. This may apply to your scenario. Maybe Anthony Merton could run this scenario in the debugger for a test and see if this is the same.

Hi again.The SID/STAR's from Navdata are not outdated in common, but some may be. It's up to the author to update them as these are user uploaded files. In my experience the majority of them are ok and are updated from time to time. As a sidenote these procedures may be more complete and may also cover airport not present in the PMDG_Procedures.I have personally uploaded almost 40 airports to Navdata and I check available resources at least once in month to catch up with changes. (I already now know that some will need an update in the next cycle due to changes effective later this month:-)).The files from Terry covers 1740 airports. Although the may lack some procedures some places, they are always up to date, every month, thanks to him for great service! FYI you may take a look in his ReadMe file how this procedures are generated.

Hi again,No, it's not the Airac 0410 that cause this. I suggest you recheck your installation once again.1. When you install the Airac, make shure you direct the installer to your FS9 root folder. Look in your FS9/FMCWP/NavData folder, it should contain 6 files dated 21.09.2004. Also make shure that you don't have any double folders of this or elsewhere.2. Download the PMDG_Procedures from Terry's site, http://home.sw.rr.com/filesherenow/index.html, or from the PMDG site. Install these files direct into your FS9/PMDG/SidStars folder. 3. To verify go into your FS9/PMDG/SidStars folder, here you should have about 1800 files. Open one file and check the file header, should say "Derived from DAFIF cycle 0410" and be dated 29.9.2004.4. Then you may download the All-in-one file from Navdata with useruploaded procedures, install into FS9/PMDG/SidStars and overwrite.

Hi,In which airport do you get the error message? It is most likely due to an old procedure file that don't match any recent changes in the latest Airac cycle. The SID/STAR's at Navdata are all user uploaded files, and some of them are not updated when there are changes in the airac data. You may also try to download the PMDG_Procedures_0410 from Terry's site and see if this solves your problem.

Hi Vincent.I did some search on this and found that either CYQQ or CYLW are a part of the precent sid/star download from Terry. However CYQQ was earlier until april, I have a file in my folder dated 3/18/2004. As he mentioned there has probably been a renumbering of rwy's, but for some reason CYQQ is no longer present in the download.To summarize, the file you have don't match the data from the latest airac cycle including the renumbering.As for CYLW, this one is not a part of the PMDG_Procedures either. The file you use is most likely from the AIO from Navdata. This is a user upload and as far as I can see it was written back in january, and may not contain any recent changes, and that will cause the error message. You will have to contact the author of this file or rewrite your own.

Hi LucaWell, you are almost there, I try to explain.Start the SID with the name and common part, must be at leats one waypoint. Then follows the rwy transitions, but don't write TRANSITION here, just nail down RNW XX and the waypoints, headings or whatever needed to get from that rwy to the wp in the common part. Do so for each rwy. Then at last comes the enroute transitions, if needed.Here is a fictive example:SID TEST.1A NAVAID ABC FIX DETA (This is the common part, must be at leat one wp) RNW 25R KEEP TRK UNTIL 1500 NAVAID DEF NAVAID GHI (This is the rwy transition) RNW 25L KEEP TRK INTERCEPT RADIAL 150 FROM NAVAID DEF NAVAID DEF (This is the rwy transition) TRANSITION ALPHA NAVAID JKL NAVAID MNO ( This is the enroute transition after the common part, if needed)In these SID's you always start with the common part, and then followed by the rwy transitions. Test this in you sid's and let us know how it works.

Hi Shaheedan.No sorry, that is not possible. FsNav can only exports(for PMDG) in the flight plan format, RTE. The closest you can get is to create your flight plan WITH sid and star included in FsNav and export the flightplan for later use.But don't give up on the procedure writing in Notepad, the syntax is actually straightforward and easy to write as soon as you get into it, thanks to the programmer. As a reference tool when writing procedure files, FsNav is very handy. Good luck.

Well, there is.. When you have entered the origin an dest and at least one waypoint, you will get the save prompt on page one in ACT RTE.

Terry, as Mats pointed out, there has been changes-renaming for a lot of wps for EGPF, especially in the SID's. so I think some of the procedures must be rewritten. You may also check out the latest charts.It looks like the author is going to release a bunch of updates for the latest airac over the weekend, have a look at his website here: http://homepage.ntlworld.com/simon.butler2...usefulfiles.htm.FYI, the PMDG_PROCEDURES_0409 are working for EGPF, although they are not complete.Garry, you can find the tut's in the library, "making_737ng_procedures_v4.zip" and "making_737ng_procedures_v4_correction.zip".

Yes it is, 07_System_Operations.. page 60

You can find the latest here: http://home.sw.rr.com/filesherenow/html/pmdg.html. I recommend using the same cycle for both the Airac navdata and the procedures. Then you will get no errors, at least with these files. These procedures files may not be complete for every airport around, but the procedures they contain are always up to date.

Hi,Download the latest Airac cycle 0409. Also download the latest procedures, PMDG_Procedures_0409. This will most likely cure the problem.

Seems to me that you have 2 entries of DCS, and then you will not be able to close the disco. Try first to delete the second entry of DCS and then close the disco.

Well, this isn't related to PMDG, but is rather due to MS design. If you can get hold of an add-on scenery that would probably exclude it. Or you can eventually make your own....I suggest a jump over to the scenery design forum and search for some solutions there, and also make a post there. There are also a few freeware scenery design program available for download.BTW, I didn't see this at VRMM..

In addition to what have been mentioned, if you search the library in "Original aircrafts" for FSPainter, there will also pop up some basepacks. Also try a search for "fsp_mdl_update_010418-zip". I don't know really if there are any differencies in them. I also think it's the same models you can get at fsrepaints.de.You may also take a look at the new verion2 of T Urakawa's 737NG series 600/700/800/900, you can get them here: http://www.cam.hi-ho.ne.jp/urakawa-t/index2.htm.Here's how I fill up my AI hangar (in preferable order):1: Aardvark2: T Urakawa's models.3: FSPainter.4: ARNZ5: CDAI5: PAIThey all have pro's and con's in regards to quality, framerate, install routine and so on, but that's how I do it. And not to forget the superb MRAI installer for both airlines and textures.

Hi there.Jeff, I just tried KATL and KMIA and they are present for me with airac 0409 and pmdg_procedures_0409 installed. James,The procedures from Terry(0409) for LEPA works without errors here. But I also tried the procedure file available at Navdata(from Simon Butler), and then I get the same error message. When error appears, no procedures are loaded.The most likely reason is that the VOR station SSJ is renamed to JOA in the latest airac due to real world changes sept -04. The author of the file will have to update it, and I am sure he will as soon as possible.For reference, you may take a look at the latest charts at ais.aena.es