Kwacker

Hi Bryan,Actually it is a little more inconvenient that just something that occurs when the panel is opened. I keep the main panel open at all times but every time I click outside FSX in windowed mode the FS2Crew and FSX pause state become unsynchronized. The work around is as outlined above.Is there a way to ensure the FS2Crew pause is always in the same state as the FSX pause?Enjoying the latest FS2Crew immensely!Thanks,Simon.

Had the same problem.Go from full screen to window mode and toggle the pause in window mode. The FS2Crew pause won't be changed and the two will then be back in sync.Simon.

Thanks - that did the trick.Yes I know the problem had been previously reported - but I couldn't find a clear recovery - as you provided.To confirm, uninstalling & reinstalling AS2012 did not fix the problem but uninstalling, deleting the ASE and ASA folders in the path mentioned above, then reinstalling did fix the problem. I don't have a AS2012 folder in this location on my system.Thanks again for the help DJ.

I've been running AS2012 since release with no problems but the application now does not run on startup. I get the following error message:A critical error occurred: Application failed to load - Root element is missing.Anyone run into this? Any idea how to recover?No changes were made to my system and I've tried uninstalling / reinstalling AS2012.

Hi Ryan,I think I've found the problem - following the train of thought from your earlier comments. I installed an earlier Navigraph data set (1109) and had no problem. I then reinstalled 1111, which was the one I had been using and still no problem in 2 approaches..... I can only assume the original navigraph install was corrupt.I'll run a few more tests to see if the issue reappears - thanks for pointing me in the right direction.Simon.

Ryan, thanks for the education on STARs versus approach mode!Peter, the saved flight I sent to Ryan/PMDG support had the same issue into 25L and this was an ILS approach - so I don't think it is anything to do with the approach mode.I think what Ryan is guessing is that the glide slope data is wrong - if so it must be wrong for at least 2 runways and both ILS and RNAV IAPs. Is this data in the Navigraph data package? Assuming so I think I'll install an updated version and see if that resolves it.... I'm on version 1111.Simon.

I ran a test disabling my MegaSceneryX KPHX photoscenery - same result - terrain warning on final to 25L.I'll send the save file to support.Thanks for your help,Simon.

Thanks Andrea.I'll break down the problem a little further as you suggest - disable mesh and scenery and see how that goes....Simon.

Duplicate post...

ok - I uninstalled the NGX using remove programs, rebooted, reinstalled my original installer (version from NGX release) and updated with SP1b.Flew RNAV to 25L KPHX - same result as above - yellow terrain near start of runway and pull up warnings. Inhibited EGPWS and landed normally.Anyone have any other ideas :( Simon.

Mmmm... unless someone has a better idea I'll try a clean install?ThanksSimon Bedford.

Same thing occurs on full autoland ILS into 26, same yellow blob on EGPWS changing to red and pull up warnings:

Hi Ryan, Andrea and all, thanks for the replies.I flew the MS ultralight from the start of 25L to the hill by the football stadium. The hill is most certainly there. I must have been above it in the earlier screenshot. I also checked that there is no terrain (invisible or visible) to hit, the ground is very flat - I had no problem flying the ultralight at 100 feet.It looks to me like there must be a small error in the terrain database the EGPWS uses. I'll fly approaches into the other runways from that direction tomorrow to test those.Regarding RNAV into 25L, the reason I was using that is that if I look at the real world routes used on flightaware >95% are via GEELA5. That's published as an RNAV route. A few fly ARLIN3 from KSAN. I assumed as the plate for GEELA5 says RNAV this is what you should use - is it permissible to use ILS from GEELA5? 25L is certainly equipped for it. I've no real idea what is really done in the real world.... :(

Ok, I ran a test. Landing 25L RNAV KPHX. About 700 feet radio altitude I get a terrain warning - see attached images. I believe I have the aircraft fully configured, speed correct, full flaps, gear down, right on glide slope according to instruments. I have to inhibit the GPWS to avoid getting pull up warnings.Any ideas? Maybe this approach is not in the terrain database?

ok - I found the GPWS inhibit switch - it's on the co-pilot side forward panel by the yoke. I wasn't seeing it as I don't fly copilot!Strange thing is I've never needed this before into KPHX..... is it standard procedure to inhibit this on final?I also noted there is an aircraft config option to set the GPWS to peaks mode - I'll play with this to see if something has changed.