daniel.burke01

For some reason all of my screens in this livery are loading black (not blue like they are off, but black like they don't exist) and there is zero power to the aircraft. I'm set up to load NGXSHORT as my default. I tried to re-load the panel state. Everything loads up, but I get fire alarms. When I try to deactivate them through failures page, they just keep coming back. I loaded another livery and I don't have any issues. The plane loads as normal and everything is fine. It only happens when I load this specific livery. I've tried loading a default aircraft first, I've tried loading this from the top, I've tried loading another ngx and then this...but nothing seems to be working. Any ideas folks? thanks, -Dan Burke

Mike, 10R re-opened (for commercial jet traffic) on September 18th, 2014. Ray Smith's KFLL wasn't released until 10/3/14. My previous update and flight from KFLL was on cycle 1412 with a 777 from KFLL to ENGM. Everything worked like a dream. Something happened in the updated to 1413 and in the revisions to the file specifically for 1413 v3 that navigraph released. Again, I believe I might have updated the revision of 1413 v2 to 1413 v3 while FSX was opened, and possibly had a 777 loaded. This may have caused the issue. -Dan Burke-

This is interesting Mike. My Airport_Rwy file was showing as dated 12/17/14 as well. However, I did update to V3 of 1413 after this date I believe. It looks like maybe when I updated to v3 of the 1413 AIRAC, something must have gone amiss. Its REALLY strange for me that the incident was only focused on the 777 though. My NGX didn't show ANY signs of the same problem. The only thing I can think that might have happened is if I inadvertantly updated the AIRAC while my PMDG 777 was loaded in FSX. Maybe this caused something with-in the 777 to not regenerate a file to match the new NAV files since the 777 was loaded in the game during the update. I am ALWAYS cautious to make sure I have FSX closed when I update anything, but maybe I had a flight at a gate on pause in the back ground and didn't pay attention. Anyways, issue is fixed! Thank you all again!! -Dan Burke-

Thank you Kyle for your reply, but I didn't really apprecaite your tone. I am the one with the issue here and I will be the judge of whether or not I am wasting my time. Every option is still an option until the option is exhausted through some sort of trial and error. While I appreciate your knowledge, it certainly wasn't in vain for me to pull the add-on. It takes 2 seconds to pull 2 Bgl files out of the add-on folder. To reply to your post from earlier...I did have a route in my 777 route from KFLL, but the runway was not specificed in the plan. It was actually though this route I discovered the issue several days ago. I will try deleting the above mentioned file and report back... thank you, -Dan Burke- The issue is resolved! Thank you Mike777 for the information about deleting the ARPT_RWY.dat file and thank you Kyle for confirming this! Much Appreciated for everyone's assistance! -Dan Burke-

I have never heard of Makerwys before....I have never used that before. This is the first time i have had this issue and it seems to ONLY have an issue with the 777. I just took out the files from my add-on scenery folder to return to the FSX default KFLL and I am still having the issue. Again, nothing shows up in the arrivals or departures page. This is with AIRAC 1413 v. 3. It didn't seem to be an issue with the prior AIRAC cycle for PMDG products. Tomorrow a new cycle should be released, so I guess I'll just wait until then. What is the Makerwys you speak of? -dan burke-

All, As I stated earlier, it works fine with my PMDG 737. So I then closed FSX, reopened and loaded my 777 at the gate. Same issue. The same error occurs every time. I open the route page to input my departure and destination. As soon as I input the departure as KFLL, I get the error in the scratch pad. Then, if I go to the Departure/Arrival page, there is not any departure information for KFLL. None of the runways or SIDS are showing. Downscc: Are you also using the 1413 v3 of navigraph and Ray Smiths updated KFLL scenery? if you aren't using the same material, then the results might differ. I would expect nothing to be wrong with the navigraph information or Ray Smiths scenery file as I said, my PMDG 737 works just fine at the same airport with the same add-ons and AIRAC Cycle. -Dan Burke-

Hi All, I have updated my FMS data with navigraph to the latest 1413 v3 revision. I use the Navigraph Update Data manager to install the files via "All PMDG Products". I also have a KFLL airport add-on (Freeware from Ray Smith via avsim.com) installed which includes the new 10R/28L runway. With my PMDG 737 the FMC has no problem with loading departure/arrival information for KFLL. However with my PMDG 777, if I choose KFLL as the departure airport, I get a message in the scratch pad telling me: "KFLL ERR: 10R RWY N/A". Now, I know that the nav data must be ok as it loads fine with my PMDG 737. Is there some disconnect between my add-on airport Nav Data and PMDG 777 that can be fixed here? I am kind of at a loss for what to do.... Thanks, -Dan Burke-

Thanks all, My 1st plan of attack was to try to repair the file with the installations. However, does it matter which PMDG product I run the installer on? 737, 777, 747? I really have no information as to which product this .ddl is specific too as the error message doesn't really state specifics. And, the file is located in the general PMDG sound folder in the main FSX folder. Also, if I run the original installer of a product and click repair, do I then need to go back and update the service packages as well? Or will it just repair missing/damaged files and leave my version alone? Thanks, -Dan Burke-

Hey All, A couple days ago I noticed an error message related to a .ddl file with PMDG on startup. The message I get says: Flight Simulator has detected a problem with a third-party software program (add-on) Name: PMDGSounds Dynamic Link Library Version: 10,0,61355,40 Company: PMDG File: PMDG\DDLs\PMDGSounds.ddl Do you want to Run this Software (not recommended) If I click yes I Flight Sim shuts down with a fatal error. If I click no, it starts and everything seems to run as normal. I didn't change any settings or do anything different, this just happened one day while opening FSX. I am not sure if I need to re-install something or where to begin to do that. I have the 737, 777, 747...All are up to date and include all add ons. Any tips on how to fix this error without re-installing everything? Thanks. -Dan Burke-

Hi all, On December 3rd, REX released an update to their REX Essentials Plus. Updating to 3.8.14 etc.... Now, let me start off by saying I know that last year in August 2013, REX announced they would support the uploads feature of the 777, but I never heard when or if this actually happened. Since first having the 777, I have always had this feature and it worked with REX. I was able to request, upload and load weather in the legs page and the descent forecast page. Both if I filed a flight plan through REX or just used the weather engine alone. Since updating to the most recent update, this feature now does not work. I get invalid message in my scratch pad. Clearly this is either from the update or maybe it was never supposed to work and I was just somehow lucky? :wub: :rolleyes: I have no idea. If anyone else has noticed this or has any input, let me know. I will go ahead and copy this message over to the forum at REX as well, but since it's directly related to the PMDG 777, I wanted input from this forum as well. Thanks all! Kind Regards, -Dan Burke- After reviewing the REX website, it looks like others are having the same concern. REX did respond to one post asking for more information. I will attempt to keep this post updated with any resolve to this situation since I assume it will affect more than just me! Thanks All, -Dan Burke-

Well, the only reason I believe it may is that it works fine with the NGX, and I am able to have hydraulic power and engine start with no strange side effects... Thank you! I will take a look! -Dan Burke-

Hello All, I've noticed that when using GSX with the 777 for pushback, I cannot have ANY of the hydraulic units switched on or to auto. If I do, this causes the rudder and nose gear to have crazy movements, as I would expect because they are hydraulicly powered, and trying to be turned by an outside source whose bypass pin seems to take no effect. So my question being, does GSX just not work properly with the 777 to "bypass the hydraulics" with it's "bypass pin" or does the 777 in RL actually have to be pushed back with no hydraulic power and engines must remain off until pushback is complete? (something I can't imagine happening)....I am ASSUMING that the GSX bypass pin and PMDG 777 just don't work together, or am I really missing something here? Thanks for your comments in advance! -Dan Burke-

Hey all, Don't normally ask these things, but was curious is anyone is interested in doing the new AA livery on the PMDG 747-8? Thanks, -Dan-

Hello all, I don't normally ask about these things, but curious whether there is an AA new livery for the 747-8 out there or if anyone is interested in creating one? Thanks, -DAN-

There are programs on the web called FSX registry repair....sometimes files get lost or moved by accident. Run this repair and see if this fixes your problem. I know there is one on the Flight1/coolsky website in the downloads section. Hope this helps, -Dan Burke-

I have the same issue, but only since switching to windows 7. It sucks, but I just have to make sure hit ALT+ENTER before opening any menu to load fuel etc....Haven't found a fix yet... -Dan Burke-

I also noticed that when you set the sensitivity for the key combos under "controls" section of FSX...if the "repeat" slider is fully to the right, you will get a HARD brake, if the "repeat" slider is to the left...its less intense. Dan Burke

The default key combo to turn this off I think is shift + 3. I did this my self while using shift + E to open the door and mistakenly hit the 3. If this isn't it, it could be Ctrl + 3 too, but I am almost 99% sure its Shift + 3 Dan Burke

ETOPS isn't "equipment" per say that extends the physical limits of the aircraft. A 737-800 and a 737-800ETOPS are the same aircraft and bulit of the same components, its just that ETOPS craft has been certified for single engine operation to a diversion airport up to 180 minutes away. These certifications range in minutes from 120 to 330 and require the flight crew and aircraft to be certified under special rules such as routing/planning or additional checklists that must be performed during the flight. For example, the 787 is currently certified to 330 minutes as well as boeing's complete line of 777's. The selection of ETOPS on the NGX menu simply places the "certification" sticker in the flight deck. But as far as gaining extra distance or carrying extra fuel...this option doesn't change that. You can read more about ETOPS on wikipedia. It has some good information on ratings and procedures! Dan Burke

Doesn't this happen when you use a pirated version of PMDG 737ngx? ~Dan Burke~

I even believe now that with the 777 they are or are in the process of extending the ETOPS to 330 minutes...thats a good 5 hours from any point! -Dan Burke-

Well, if you have an engine bleed fail, you won't be flying anyways, so no need to start the engines...in theory you could use the air cart to start one engine externally, but to start the other engine you would still need to cross bleed the air from 1 to 2 and with no duct pressure that's not going to happen. The process for the external start is close to the same as a normal APU start. Open the pack of the engine you wish to start. This will provide air flow to that engine for spoiling. Start lever to idle at 25% n2. In your case this would be as far as you could go in your situation. You would then normally disconnect the air started unit. Push back. then rev up the started engine to about 30% N1. Cross bleed your engine packs to supply air to the second engine to supply sufficient air to start. But since you have no engine bleed this won't happen for you. You wouldn't want to be doing any flying though with these failures. This could cause pressurization problems and if you had an engine failure off the ground you would never get it started again! -Dan Burke-

This is your problem. The yoke only controls the ailerons and the horizontal stabilizer with the auto rudder turned off, not the nose wheel or the rudder. I have a joystick and if I have auto rudder off, I can move my joystick from side to side while taxiing and the ailerons move up and down with no change to the direction of the aircraft...however, if I have auto rudder on, and move the joy stick from side to side it causes the aircraft to turn. Luckily, my joystick acts as a tiller by twisting it from left to right so I can have the auto rudder off and it causes me no issues as I can steer while taxiing. It sounds like you may need to get rudder pedals or a joystick to work in combination with your yoke as I don't think your yoke is going to twist to turn the plane! Does this make sense? -Dan Burke-

While this might be true, its quite impossible to connect the ground power in the NGX without having use of the FMC....so in turn, you'd still have to hold the menu button as mentioned above to connect the ground power..... -Dan Burke-

Its normal...The Fuel pump system on the NGX is designed to work without the use of the pumps. I don't think its recommended as a standard practice...haha...but it won't starve your engines of fuel if they are off. Its gravity and pressure driven system... -Dan Burke-