johndrago

Same thing here. I thought I was doing something wrong, but lower DU shows no brake values no matter what the braking is. - John

Ok, I figured out how to make it work. It appears as if the baggage carts will ignore the NGX's commands via the FMC, and won't acknowledge that the cargo doors are open. The way I made it work is to use my normal FSX commands to open the cargo doors (in my case it's D2. I hold D for 2 seconds, and then push the number 2. The baggage cart will think I opened the cargo door, even though the NGX doesn't show it. I then go to the FMC, and open the cargo door using the NGX switch. It will then open, and all baggage functions will continue. To close I reverse. I use my FSX key command to make the cart think it's closed, then I actually close it via the FMC in the NGX. Pain in the butt, but it works for now. I think FSX is ignoring some of the custom key mapping and FS Actions that the NGX is producing. John

Hi Guys, Since I've loaded the NGX, I can't get the baggage carts to approach the aircraft. I have both cargo doors open, and I'm parked on the line, but they won't come. They will come to other add-on aircraft. Is there something I'm missing in the settings for this plane? I'm currently flying the 800WL AA livery. Thanks, John

Hi Guys, I know this is going to sound like a standard question, but here it goes... Why doesn't this happen with the LDS 767 and the 747x when using the same navdata? Thanks, John

Hi Guys, First off, what an incredible plane the NGX is. I've been waiting years for this as I was a previous owner of the NG for FS9. Well worth the wait. Now to the issue I'm having. I've flown two flights so far (KLAX-KLAS) in the 800WL, AA livery. All is well until I'm on final approach. The LOC and GS are captured, ILS rwy 25R frequency is entered into both NAV radios, Course set (auto feature turned on in PMDG settings). As I'm approaching the runway, I can see on the ND, and out the window visually that I'm coming in just right of the runway, meaning that if I were to allow an autoland, I would have landed on the right side of the runway (basically in the grass/dirt). Both times I've disconnected the AP at 1000 and corrected the landing. It seems as if I'm offset from the true course of the runway. I startup from cold and dark, perform the realistic IRS alignment, and enter the POS into the FMC. I've tried both line selecting the POS from the FMC and entering below, and manually entering my position via the data from hitting SHIFT-Z from FSX. Any help would be really appreciated, as this really screws up the end to an otherwise great flight. Thanks in advance, John Win7 64 Ultimate6GB RAM

I have not used any patches yet. John

I had this problem twice yesterday with default KLAS.John

Hi Joe, I probably should have mentioned that I have an HDMI port in my monitor (Samsung 46" HD TV), and that it has sound built-in. The sound quality is so good from the monitor, that I opted not to use external speakers. If you don't have that option, then perhaps using your motherboard's built in sound, or the Soundblaster card may be the only way. Sorry for any confusion. John

The 460gtx has sound on board. I disabled the sound on my motherboard, and used the hdmi port on the 460 to deliver sound and video. John

Same thing here as well. Trying with the most minimal numbers still results in a large turning arc that puts me into the gates behind. Maybe it's a calculation error between feet and meters. I'm sure it will be addressed. John

Did you click the LSK keys next to each V speed? If you do, that will transfer the speed from the FMC to the PFD. John

Hi Guys I have a CH Yoke, and have the gear and flaps mapped to two seperate switches. The gear switch works fine on all other aircraft, but when I fly the 738, and push the switch, all that happens is the gear handle will flash. I have to resort to using the mouse, or pushing "G" to get the gear up or down. All other mapped buttons or switches seem fine in NGX, just not the gear. Why would this happen only with the NGX? Thanks, John

I don't use FSUIPC, and this is happening to me with my CH Yoke. The flaps button I have assigned works fine, but the gear button just flashes the gear lever in the VC, and nothing happens. I had to hit "G" for the gear to go up and down. Any ideas on how to get my button working with the NGX? I tested on other aircraft, and the button works fine. Thanks, John

Are you using the Saitek throttle quadrant? If so, I advance the throttles to 40%, then to full, and then push TOGO. I think what's happening is that sim is reading your physical throttle handle position, and overriding the AT. There are also settings for this that may help in FMC under the PMDG settings. - John

Hi Jason, I'm dense here. Are we using the weights from the FCOMv1 manual, or the weights stated in the FMC, and at Boeing's website? Thanks, John

Hi Chris,Do you follow the complete checklist before takeoff, including programming the FMC?- John

Hi Vin,I just took another flight to see if the issue still showed up. The same thing happened. The closeup view of the FMC worked fine while on the ground, but once in CRZ, I couldn't click on anything within that view. I tried to adjust the view, but it was locked. Pressing and holding the hat swtich didn't slide the view in any direction.Any suggestions?Thanks again, and sorry for typing your name as Vic :( that was a typing error I asure you. John

Hi Emanuel,If you don't register the dll, windows won't know it's there. To register, open a command window, type REGSVR32 C:\path to the file\uiautomationcore.dllYou should get confirmation that it registered. John

Does it act like it's working (lights, buttons, PFD annunciation), but doesn't actually engage, or are the normal signs not present? Have you checked your failures section to make sure it isn't "broken?"- John

Thanks Vic, makes sense. I will try that next time.- John

Hi Guys,I have experienced an issue that I'm hoping you can help me with. I took a flight the other day in the 747x. In the VC, when clicking the "A" button to get to the third view (closeup of the FMC), I was able to program he FMC during preflight, and all was well. After getting to cruise, I didn't use that particular closeup view any longer, as I could see what I needed from the regular VC view looking at the FMC at a distance.During decent, I was given a different runway than I had initially programmed into the FMC. So, I switched to the closeup FMC view, and tried to make the adjustment. No matter where I clicked on the FMC, nothing responded. It was like the clickspots disappeared. I tried cycling through the views just to refresh, but no luck. So, I used one of the other FMC views to get through the flight. After landing, I tried again, but again, the closeup FMC view would not allow clicking.Do you know why this would happen? That closeup view allowed full use of the FMC while on the ground during preflight, but not after that. Strange.Any help is appreciated.Thanks,John

I found the fix! I wasn't aligning the IRS', because I was only testing taxing around, and didn't go through the full checklist.After alignment, the nosewheel, and yaw dampers were working.- John

Turned out to be a simconnect issue. I reinstalled UT2, and it fixed the problem.Thanks for helping.- John

Hi Guys,I'm not new to the 747x, I've been using it for years. I just built a new system, and reinstalled it. I'm being plagued with the "nosewheel not turning" issue while taxing. I have autorudder set to off, and it still does not move. I even turned it on, and stil no luck. Advanced animations is on, and I've set my Flight Simulator X folder to have full permissions by the local users. Settings appear to be saving properly, but the nosewheel just won't turn!I'm running Windows 7 Ultimate 64. Any help would be appreciated.Thanks,John

Did you ever find a fix for this. Mine is doing the exact same thing now.Thanks,John