November 3, 200322 yr 1. just to check, can anyone here go to KPHX and try to access the runways for wither departure or arrival? I receive a 'fmc error' every time, this is a repeatable situation for me.2. does anyone know of a way to 'reverse' the mouse wheel operation with the 'climb/descend' wheel on the MCP panel? Currently I get the ipression that it is not quite right, IMO. CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
November 3, 200322 yr # 2 is already done Mike...........................................Cheers,[h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg Randy J Smith
November 3, 200322 yr >1. just to check, can anyone here go to KPHX and try to>access the runways for wither departure or arrival? I receive>a 'fmc error' every time, this is a repeatable situation for>me.Sounds like the procedure has a problem in the syntax. Try updating to the most recent AIRAC cycle, and the most recent procedure cycle.
November 3, 200322 yr Author thanks guys, as I just purchased this within the last two weeks I assume that I have the latest data. I know that AIRAC has been updated but I am sure that this would not effect my problem (I have not downloaded it yet). I reviewd the procedure file and it appears to be the latest (DAFIF Cycle 0309) that I can find. the KPHX.txt file is located in my PMDGSIDSTARS directory. I have not had this problem in any other instance. Can I assume that you folks have KPHX runways working? If so I will assume that it is on my setup only and will try to work it out myself. Thanks for your replys (also on the MCP wheel - good job) CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
November 3, 200322 yr Hi Mike,>I know that AIRAC has been updated but I am sure that this would not effect my problem.:). Airac 0310 was missing a VOR (FMG, I think), which is part of some arrival/departure procedures for KPHX. Thus, the SIDSTAR file for KPHX is calling up a navaid that's non-existent in the navdata, hence the FMC error.Update to 0311, and the problem will most likely disappear.Cheers,Gosta.http://hifi.avsim.net/activesky/images/wxrebeta.jpg
November 3, 200322 yr Hi Mike,Maybe you should have made a simple search in this forum with the word "farmington" (without the quotes). You would have seen several posts dedicated to the very issue you are mentioning. I will not repeat here what has been beaten to death in those posts but as Grove said it looks like the farmington - rattlesnake VORs issue is now solved in the Airinc 1103. DAFIF 0309 is not only outdated but cannot be used in its original form. It must be converted to FMC readable formats. I suggest you go to http://www.navdata.at/ and download the latest cycle.Michael
November 3, 200322 yr Author thanks GOSTA, will do that. However, you guys may be interested in knowing that this issue with me is directly related to my use of FSBuild, AdvDisp and RCv3.Tonight I flew from KPHX to KDEN. I knew that when I went to select KPHX as the departure airport, that the error would show up. OK, I did select and sure enough the error. I cleared it and went on (without selecting a departure runway). Off to Denver, 30 out, RC's instruction to contact arrival, did that, got the runway in use and went to place it in the arrival on the FMC. BINGO, no runways available!I knew this was not true because of prior flights. I also knew at this point that FSBuild and PMDG are not at fault. RCv3 and its associated AdvDisp.dll were the only changes I have installed with no issues prior. So, I landed anyway, ended RC via the ADV display and then 'goto' KPHX, again no runways listed in the FMC (after the posit keyins and departure setup)... hmmmmmmm.So I exit all and restart with no RC, yep, I get the runway info now, no problem. I can repeat this error at will just by utilizing RCv3. Somthing is very funny here on my system and I will let you know how it turns out. It may be somthing with pre selecting runways via RCv3. I know this sounds weird only because of the standalone nature of RC - but I can do this on command.Let me experiment over the next few nights and get the exact sequence and eliminations down pat, that way I can relate to you what I found out and how I got around it just for future reference. Now... off the get the update AIRAC... CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
November 4, 200322 yr I have a similar problem with KPHX. I get the error shown in the attachment. I was using airac 309. After reading your post, I updated to 311, but the problem remained. (This is in FS9). I have a FS2002 installation as well, but it is using 304 airac and I do not get the problem there. I have tried installing from 309 thru 311, but the error continues. I have not tried an updated airac in my fs2002 installation. I am unable to get any runways, sids or stars for kphx. Let me know if you solve this as phoenix is one of my favorite departure airports. Thanks,Mike MKDFW
November 4, 200322 yr Hi Mike,I just checked with the latest Airinc (0311). It works perfectly. My suspiscion is that the problem is not with the Airinc but with the sids and stars file for KPHX. Suggest you delete the KPHX files which is in your PMDGSIDSTARS folder and try again. If it works then try to download the latest sids and stars database from the PMDG site.Michael
November 4, 200322 yr Michael, your suspicions were right on. I deleted the kphx sidstar file and the error disappeared. I reinstalled the latest file from PMDG and all sids, stars and runways available. Thanks for your assistance.Mike M.KDFW
Create an account or sign in to comment