Vauban

LOL, now I'm on track. Thank you Kyle! Geoff Kent

Thanks for your swift response Kyle, I really appreciate it. As you suggested, I uninstalled NGX completely as per your instructions and ran the latest installation file. Now I have the Operations Centre which is what I was looking for when I had the installation problem. But I still have a strange version number when I click: Add-ons > PMDG > About PMDG... It tells me "Version (App): 10,0,61355,62" Am I looking in the right place to see what version of NGX I'm running? I'm expecting to see 1.10.6461 Thanks Geoff Kent

Duplicate - sorry, can't see how to delete this. Cheers Geoff Kent

Duplicate, sorry - can't see how to delete this. Cheers Geoff Kent

Hi guys, Returning to the NGX after a break. I have SP 1c installed in FSX, Windows 7. I see to install a livery I need the Operations Centre To get that I need SP 1d. So I downloaded the latest installation file from the PMDG site. I extracted the three files in the package: PMDG 737 8900 NGX Base Package FSX and the two readme's The non-Steam readme tells me it's v 1.10.6461 24 March 2105. When I run the installation exe, the InstallShield wizard displays the Repair or Remove window. That doesn't seem right, but I select Repair and continue the installation. When done, I start FSX and load an NGX flight. Now, Add-On > PMDG > About tells me I have v 10,0,61355,62. Any help appreciated. I'm looking forward to getting airborn again. Cheers Geoff Kent

It's the same issue Will. I'm still hoping someone will pick this up and suggest a solution.CheersGeoff Kent

Thanks Clarke.But Skyrim is just a game, right? So why...?Ok, never mind. :Talk to the Hand:Geoff Kent

Hi Clarke, thanks for your help here. I just meant I hit the 'Y' key to freeze the simulation and displace the aircraft manually to see at which altitude the magenta profile spot would rise to the centre of the line. Check back to my original post, Clarke, and you'll see the profile passes BLM at around 14500', and not above 20,000 as you're suggesting. Yes, but Clarke, the aircraft shouldn't be held at 20,000' in the first place to 'begin descending again once...". The profile is well below the aircraft at BLM. The question is, why is the aircraft being held at 20,000' when the BLM altitude restriction is 'at or below' 20,000'? I understand, but the aircraft was held at 20,000 for so long approaching BLM, that it had no chance of losing enough altitude to land.If the 'at or below' restriction always locks the altitude AT the given value, then no one would have been able to complete the Heathrow to Zurich tutorial. So it must be a problem with my system. Anyone want to volunteer to see what happens to them at BLM?Here's the PERF page, by the way...CheersGeoff Kent

I definitely set the FCP altitude to 4000 during the descent from FL370. I remember seeing the PROF TO value on the FDA change as I wound the altitude down. It's colour was white most of the time, but changed to magenta each time it corresponded to any limit set in the FMC; that is at 20000, 12000, and 4000. Here's another screen shot.CheersGeoff Kent

Thanks for that Kyle. Of course, you're right - I'm above profile. I don't know why I wrote 'below'.But on your second point, PROF TO 4000 is my manual altitude setting on the FCP.HOLD 20000, as you know, is the next limit given to the autopilot, and I can only assume it comesfrom the FMC.Because the MCDU shows the limit at BLM to be 'at or below FL200', I would expectthe FMC to allow me to follow the profile and be at 14,500' by BLM. So I'm still confused.CheersGeoff Kent

This is probably normal behaviour, but I'd appreciate it if you'd help me understand what's happening here.Tutorial Heathrow to Zurich:You can see from the MCDU that I've been descending from FL370 to arrive at BLM at or below FL200. (If BLM isn't legible, it's the waypoint next to LFSB.) The magenta spot has been centred on the profile indicator during the descent. What I don't understand is why now, 20 miles before BLM , the aircraft levels out at FL200, and the magenta dot sinks showing I'm above profile. Using SLEW, I found the profile passes BLM at around 14500'. So why does the aircraft not follow the profile?Thanks for your helpGeoff Kent

That's great, Ian. Now I can set the horizon just as I want it.Thanks for your help.CheersGeoff

Hi everyone,When I start a flight in the 2D cockpit, the panel takes up the lower 2/3 of the screen, and the upper 1/3 is taxiway or runway - I don't see the horizon or sky. Zooming out would help, but at the start of a flight the zoom keys (- and =) don't work.I found a work-around for both of these problems: I select and then deselect the 'Undock panel' option (right-click on the panel). Now, not only is the sky well visible, but also the zoom keys work. I find I'm at zoom factor 1 initially, and then I can set whatever zoom factor I want.But the problem occurs again if I switch to Locked Spot view (F11) and then back to the 2D cockpit (F10) - that is, above the panel I see only taxiway. This time, however, the zoom keys work and I find the zoom factor is not greater than 1 as you'd expect (since that would be the reason I can't see the sky), but it is 1.0. By zooming out to 0.40, I can get the correct view that corresponds to the view I get after undocking and docking the 2D panel.I'm using a wide screen, though I can't see that this could be the problem since after undocking and redocking the panel, the display is correct.Any ideas anyone?ThanksGeoff

Thanks for the information Matt. My problem was that, like you, I didn't have the Map view at all. But then I found that the Carenado GPS does not have full functionality. And their own version of the Garmin 430 manual tells you how to get the Map view.CheersGeoff

Hey Matt, did you get the Map problem fixed? I'm having the same problem myself.CheersGeoff