HelloI have been using 737NG for a couple of weeks now and only recently have noticed quite strange thing ( at least to me ):When uploading FSBuild - made flightplans sometimes it looks like a part of FMC own database is lost, as it no longer recognizes some of airport runways and SID/STAR's and all this results in 'Program Eroor' message on the FMC.One example ( there are more avaialable ):Everything works fine if I load flightplan for EDDF rwy 25R - LFPG rwy 26L, but if I load another one for rwy 7L and 8L respectively, there aren't any runways ( "not in database" message when trying to enter them manualy ) & DEP/ARR procedures recognized by the FMC - and than this 'Program Error' msg pops up. All this happened only today, after some 5 weeks of seamless FMC performance. The only thing that has changed in FS2004 - related software on my PC in the meantime is the last week's upgrade of Ultimate Traffic by Flight1 + new official Flight1 AFCAD2 files for major airports ( EDDF and LFPG included ).Needles to say, Navaid & SID/STAR databases are up-to-date, have reinstalled them when the problem occured but with no change whatsoever. I do also believe I am able to handle correct FMC programming to perform standard flight procedures ( well, at least I was able up to now... ).PMDG: any ideas/help please ?Thanks in [email protected]

Chris,I too am experiencing the same problem as you when loading up a FBuild2 generated flight plan. I also have Ultimate Traffic with the latest AFCADs installed,but I cannot confirm that this is causing the problem because I've only just purchased FSBuild and had not uploaded any of it's plans before installing UT.CheersPaddy(Satchmo)Howard

This issue has already been reported, and should be fixed in SU2.Aaron

Well, have spent some time investigating the problem myself and here are the results:1. Cause of problem: The issue is most probably related to FSBuild-made RTE plans. The runway numbers that start with '0', e.g. '08L' are put by FSbuild into those RTE files with additional '0' at the beginning - so plan entry looks like '008L' and this causes PMDG FMC to crash - at least in my case.2. Temporary fix: If you correct manually those runway entries in RTE files to the right ones, everything works OK3. Permanent ( ? ) fix: I have reinstalled my FSBuild ( v 2.1.1 ) and now it works ( for 2nd day ) with no problem, runway entries in FSBuild-made RTE files are correct again - will see for how long...Anyway, perhaps I am not catching the big picture ( and it is indeed quite possible ) but if the issue is about FSBuild import format, than what can be done about it by PMDG in SU2 ? I am just curious...Have funChris_K

>1. Cause of problem: The issue is most probably related to FSBuild->made RTE plans. The runway numbers that start with '0', e.g. '08L' >are put by FSbuild into those RTE files with additional '0' at the >beginning - so plan entry looks like '008L' and this causes PMDG >FMC to crash - at least in my case.>>2. Temporary fix: If you correct manually those runway entries in >RTE files to the right ones, everything works OK>>3. Permanent ( ? ) fix: I have reinstalled my FSBuild ( v 2.1.1 ) >and now it works ( for 2nd day ) with no problem, runway entries in >FSBuild-made RTE files are correct again - will see for how long...>Anyway, perhaps I am not catching the big picture ( and it is >>indeed quite possible ) but if the issue is about FSBuild import >format, than what can be done about it by PMDG in SU2 ? I am just >curious...This poblem was fixed in Build 153. I believe the ver 2.1.1 release was Build 154.I took responsibility for this fix, so there should be nothing in SU2 to address it.Most Fsbuild2 users should have Build 154, if you do not and have this problem, send me an email and I will send you Build 154 in he reply.Regards.Ernie.BTW: this bug would only occur for Airports outside the U.S. as the program as adding the leading zero for the runway identifier when a leading zero was already there for most non U.S. airports.

Ah..That's what my problem is! my version of FSBuild is 151 ..which is strange 'cos I only purchased it last week(?)Anyway, thanks for the 'heads-up' Ernie, sending you an email now!CheersPaddy (Satchmo) Howard

Glad you guys found a fix for your problem, but there is _another_ problem with the FMC and loaded files that _is_ a PMDG issue, and is reported to be fixed in SU2. Some of these problems may also be related to NAVDATA errors.I was able to reproduce it easily (with the 0310 NAVDATA, haven't tested with the new update) by creating a flight plan from SEA to anywhere. The FMC would through a PROGRAM ERROR every time after you'd loaded the plan and tried to pull up the departure screen.In any case, I always check to make sure the problem isn't with the FMC itself by creating the plan manually and then saving and reloading it. If the problem doesn't happen, then there is something wrong with the RTE file.Happy flying, and hopefully SU2 will really close the last of these issues!Aaron