mkear

Thank you everyone. It's nice to have friendly voice in my torture at last. Bob, I'd have stayed with Windows 7 but it has to happen at some stage - eventually they're going to remove support for it, and I had some free time now to do the job so (stupidly and wrongly, it turns out) I figured now was the time to do it. I thought at first that it had upgraded cleanly and just as advertised. Nice!!! I spoke too soon. Then i went for a fly in my PMDG NGX and found that was broken. (hence this thread) Then so also was my Garmin 1000 therefore my Flight One Duke was broken. Then it was time to do some work and i found that my key application - my IIS Web server was broken. Without it (or a non-microsoft alternative) I can't work. I have about 200 applications on my workstation - most of them only used once in a while and I'm gradually learning that some of them open just fine but when you come to use some of the features they're broken. I guess those are features built with licensed libraries or something. Anyway, it took me 5 months to clean the installation of Windows 95 after I was a beta tester for that. And several months to get Windows 98 working ok, and the Win2000 server. My Windows 7 machines were new machines so they just worked ok. But this upgrade is going the same way as all the previous ones. Sigh. Cheers Mike Kear Windsor, NSW, Australia.

Thank you Kyle. I've done that. Just for anyone else's interest, Dont take it for granted that when Microsoft tells you all your personal and app files are left where they were, that's true, but notice they dont say the same thing about registry entries. Any program that relies on registry settings to work or validate or any other purpose will quite possibly be broken by installing Windows 10. And then dont expect anyone from Microsoft to help. So far I've spent FIVE days trying to get my Windows 10 working properly, and FSX is the LEAST of my problems. The applications I use in my professional web development life are in a shambles and I can't do any work. And I've been passed around from one person to another at Microsoft, few of whom will actually attempt to help me. Believe it or not there is NO ONE in Microsoft Australia you can talk to. You can only talk to people in the Phillippines who sound like they are speaking on a tin can and string from the moon. Cheers Mike Kear Windsor, NSW, Australia (Very frustrated and ANGRY at Microsoft - once a great company, now a shambles.)

I've upgraded my windows to Windows 10 Professional, and now my PMDG NGX is wanting an activation code. If i dont give it a code it likes, it tells me that I dont have a valid licence for my NGX. This concerns me greatly because I am scrupulous about only using valid software. Anyway, I figured it wanted the licence keys originally given to me when I bought the aircraft. But it says they're not valid. What do i do now? I have the PMDG NGX 8700 base package, the PMDG NGX 600 add-on, the two 777s, and the 4100 turboprop. I havent tried a 777 or a 4100 but I'm assuming that whatever's broken the first validation has also broken the second. Any one have any ideas what I do now? Cheers Mike Kear Windsor, NSW, Australia.

Thanks Bryan. I hadn't noticed the button control setting, never having needed to use it before. I just skipped past that. Fixed it. And thanks a lot for being available, even on Christmas day. Cheers Mike Kear Windsor, NSW, Australia.

I have updated to v1.1, and now my FS2CREW NGX Reboot wont change from SOP2 to anything else. All the other options in the setup menu will change but SOPS is fixed on Set 2 and won't change. Have i done something wrong? I'm using FSX with EZDOC and Active Sky Next if that makes any difference. Cheers Mike Kear Windsor, NSW, Australia.

Oh yes good point. I'm thinking about this thing... Saitek Pro Flight Yoke Pro Flight 3-position Mode Switch 3 axis levers on Quadrant [post=http://tinyurl.com/njcxgap]Kogan catalogue page for Saitec Yoke[/post] ( I haven't gone shopping for the best deal yet, so this isnt necessarily where I"m planning to buy - just a look at the equipment I'm considering that's all. ) I think that should do well for the B737 NGX and B777 as well as the other light aircraft I like to fly, as long as the rudder issue can be worked out. Cheers Mike Kear Windsor, NSW, Australia.

I am looking to buy the Saitec yoke, and throttles, but my budget wont stretch to getting the rudder pedals as well just yet. Will that setup be worth it with no rudder pedals? I'm currently using a logitec joystick with twist rudder and I'm wondering if i am going to replace my joystick with the Saitec stuff, how will it work? Anyone done this? Cheers MIke Kear Windsor, NSW, Australia

THAT'S IT!!!! Brilliant, Budbud. That's where it changed. I was looking about the settings, and changed that the other day! It had been set to Realistic AP engagement = NO before. That's why it's never bothered me before. Thanks!!! Cheers Mike Kear Windsor, NSW, Australia.

Thank you Budbud. I havent had this problem before, I guess the new version of the NGX is a little more picky on this aspect than previously. I'll have another look at that - make sure the NGX is flying stabilised and in a stable climb when I try to engage the A/P Cheers MIke Kear Windsor, NSW, Australia

Frequently when I fly the NGX, the autopilot wont engage. I suspect there is a setting I have missed somewhere but I can't find it. Can anyone give me a hint as to what I might have missed? I have learned that the autopilot wont engage if: 1. the IRS isnt properly aligned. 2. the aircraft isnt in the air and above the minimum height AGL (about 1500ft or so I think) 3. the flight directors arent turned on. These are the only things i can find in the FCOM Is there anything else? Cheers Mike Kear Windsor, NSW, Australia

Jeez Bryan, I should take more time to consider things before i press the panic button. You're dead right. The liveries were some from PMDG's free set, and the others were downloaded from AVSIM, so therefore of varying quality. I looked at PMDG 737 Options.ini and that enable line was not there. A 30 second interface with the FS2Crew configuration application and it was fixed. Bloody obvious when I think of it . I'm kicking myself for not looking at that before I wrote the post you just replied to. Thank you Bryan. Having some humble pie with my breakfast. Cheers Mike Kear Windsor, NSW, Australia.

Oh fer pete's sake - after starting half a dozen times just fine, I added some liveries, and now the SDK warning is back again. To try to minimise the things that might be causing the problem, I now get the SDK error from FS2Crew if i start FSX in this sequence: 1. Start FSX 2. Select the default aircraft (Trike) to a gate at an airport I want to use as the departure point for this flight. (I'm assuing that doesnt make any difference - the aircraft and FS2Crew doesnt care what airport and scenery I"m using do they? ) 3. Ensure that EZDOK is disabled 4. Ensure that the trike has loaded in the 2D cockpit. 5. Load the NGX (I've tried the house PMDG livery as well as some of the ones I loaded - same result) 6. Before I did anything else, pressed ALT-C to open the FS2Crew control panel - got the SDK warning message - SDK failed to load. So does that mean that somehow I've corrupted my NGX instal and need to go back and do it again? Any other possibilities that might have caused this to start happening again, given that all I did between last night's successful operations and today's failed operation was loading liveries. Cheers MIke Kear Windsor, NSW, Australia .

Well the issue related to IRC aligning was a RTFM problem. I didn't know what I was looking at meant. I dkdn't know that when the "ALIGN" lights flash that means there's a problem with the address its trying to verify. And entering the location manually in the CDU fixes that. I thought those lights flashed when the align process was ongoing. I expected to see the "ON DC" light come up when the alignment process was finished. WRONG!! It was all there in the FCOM2 manual if i'd only read it. The problem with not being able to turn on the autopilot is still a mystery. I am assuming its because I didnt have a setting of some kind somewhere that I hadnt selected. Because when I went through the process carefully and made sure the aircraft was at sufficient altitude AGL before connecting it, the autopilot worked fine. So it's all good, and all working now. Thank you everyone for all your suggestions. In the process I've learned quite a lot. I thought I was reasonably sure of the NGX and was able to fly it properly, at least until it came to failures - I'm not studied in that area at all. But no I found I had lots still to learn. That's good - it gives me plenty to keep it interesting for a long time to come. Cheers Mike Kear Windsor, NSW, Australia.

I didn't remove the old version. I just installed the new version over the top of the old one, the way most upgrades/updates are done. Did I RTFM there too and should have removed the old NGX first? There is nothing in the installation notes that says the old version should be removed first. Jeez. You'd think being in the computer industry myself, and having run support departments, I'd have learned that woudlnt you. So if I was supposed to remove the old NGX before installing update SP1d (ver 1.10.6461 ) the best thing would be to remove NGX completely, and reinstall it from the SP1d (ver 1.10.6461) downloads woudln't it. Cheers Mike Kear Windsor, NSW, Australia.

Ok. I've been flying the NGX since it came out and getting on ok, and in most cases I've been able to arm and use LNAV and VNAV. But plainly I've skipped over a lot of the stuff about the IRS and therefore I obviously dont know enough about it. SO you're right folks, I need to know more. I'll go and read that part of the FCOM and come back if/when I still have a problem. Oh and if (as is more than likely) the problem turns out to be a RTFM** problem, I'll tell you that too. Cheers Mike Kear Windsor, NSW, Australia. (** RTFM - a technical term in computer support. stands for "Read The Damn Manual!" )