Zeemon

That looks very promising indeed! I will most likely purchase this and might even make that switch to P3D! What I am wondering; did PMDG also update/upgrade the NGX with the screen drawing thing (is there a name for it? )? For example: on the real plane the DEU's take a while to draw the displayed images on the DU's, which the PMDG 777 does very nicely. Whereas when you switch your ND mode on the current (FSX) version it is instant. Does anyone know? It's a small thing but to me a great detail!

You do have to realize that whatever PMDG will make in the future, it will shape our (personal) life in the future! This subject is kinda like "Honey, what's for dinner?" magnified 1000x!

So after some reading I found that: Secret Project #1 is the DC-6 Secret Project #2 is what we are currently guessing here Is this correct?

I was NOT using the correct words at the approach checklist. As a reply to "altimeters" I replied; "altimeters 1005" instead of "1005 set". Though, my point is, when I was using these incorrect/unexpected words, it somehow jumps from the approach checklist back to descent checklist items (even though I have already completed the descent checklist, prior to TOD, and both the ECL and the FS2Crew panel show "Approach checklist"). Where, in my opionion, even using incorrect words shouldn't make it do that, it should just ignore it. So to reproduce: on approach checklist, incorrectly reply "altimeter 1005" to "altimeters". Then you will see that some weird things start to happen. Simply put, it's a problem you won't run into when you use it properly, but it should be a bit more bulletproof to incorrect usage, in my opinion Hope this is of any use B)

Sounds great! Shouldn't the part where it jumps to the descent checklist from the approach checklist be fixed too, though? It makes perfect sense that it for instance ignores me when saying something incorrectly, but it somehow glitching to another checklist as a result is rather weird, isn't it?

I am aware of this now, and when I use that all is fine. But using wrong phraseology shouldn't really make it go haywire should it? What happend is: 1. Me: "Approach checklist, please" 2. F.O.: "Approach checklist; Altimeters....." 3. Me: "Altimeters 1005" (At the time unaware that these are incorrect words, but nothing imposible) 4. F.O.: "Autobrakes....." --> Wait, we are on the approach checklist...? Onscreen ECL confirms this and shows no autobrakes When I later saw I actually had to say "1005 SET", it correctly responded with "approach checklist complete".

A bug still exists however; i was struggling too with finding the proper way of saying it, saying it wrong however makes it somehow read the descent checlist items while you are on the approach checklist like Christian described... Thereafter it keeps bugging; because i couldn't find the proper phraseology i clicked to the landing checklist, but it ignored most voice commands (e.g. Gear Down). I suppose this is a bug somewhere? Regards, Simon

Thanks for the reply I suppose that will fix it, this does, however, mean that timed failures reset after every FSX shutdown doesn't it? I'm pretty sure it does on the NGX. That's why I always save it and have them automatically load, this never used to fail (other than the known caution light that wouldn't extinguish and the CALC fuel thingy). I guess I will have to live with it Thanks again!

Hi, After many hours in the 777, I seem to have encountered my first real problem. Since I installed SP1, I have deleted my old panestates and started off with a new C&D and save it after every flight, just like I did before (pre-sp1). Today, however, after a long preflight with no problems, receiving pushback, starting engine #2 (successfully), my #1 engine just wouldn't start! :( I have tried disabling auto-start, using a ground-start-unit, using x-bleed, etc. Nothing seems to work. No failures show up and reloading the aircraft and FSX several times didn't work. Am I doing something wrong or does it seem I have encountered a bug? My panelstate files: http://www.livegroningen.nl/panelstate.zip Help would be much appreciated! Thanks in advance! Simon

Well, I will give deleting those uiautomationcore.dll files a try... As for the randomness; the crash seems more likely when there has been a higher (memory?) load. After upgrading my Pc a while back I was able to up lots of graphical settings and it would run nicely, but then this problem started happening. I lowered the graphics a bit and it now happends less often. Flying from Schiphol to Heathrow also seems to make it more likely, and my explanation would be because they are both large airports and also have massive amounts of AI traffic (So again, a higher load). Ps. I am also using the combination of FS2Crew, ActiveSky 2012 and AES...

Exact same problem here I am afraid :( Arrival at the gate is problematic for a while now, that's why I found this topic. Just now I did another flight with the 'set wheel chocks instead of parking brake' in mind, and so I did. But unfortunatly at the exact second I set the wheel chocks in the fmc the CTD happend. So I will be following this topic and offcourse if I find a solution myself I will post it. Regards, Simon