diamondstar

On the "MENU" page. It happens when I do a quick traffic circuit, with the 777 on the runway with engines running. First FO action in this case is "RWY entry procedure". So, the FO did'nt touch anything on the FMC prior to the descent flow. Regards, Tim

Hi! Due to whatever reason, the FO will not select vref during his descent flow. Instead, he is stuck somewhere on his FMC using the Display select PNL function, thus, Display select PNL is shown on the upper EICAS. The rest of the descent flow is completed normally, all succeeding checklists are not affected. Regards, Tim

Yes, that would be great! Thanks!

Yes, absolutely!

Is it by intention the FO doesn't confirm the "Gear up" and "Gear down" call? I find this a bit distracting. Regards, Tom

Same here...! Regards, Tom

Yes, I did. Departure and Approach.

I choose the Microsoft LX-3000 Live chat headset. No issues at all...

No, he's not... No matter what's set, he leaves it off after the before start flow. And turns it off when "ok to clean up"...

No matter what I select in the Briefing section: F/O won't turn the XPDR on during taxi to the runway / won't leave it on during taxi to the gate. Regards, Tom

Really disappointed there's no longer a pushback-option included in the 777 Edition! Major drawback compared to the NGX! This means another month-long wait and additional expense ( well, not the case for me: wouldn't purchase...! ). Not amused at all! Tom

Thank's Steve, that helped! Ultra smooth on 344.11!!! Best regards, Tom

Today I've updated to 344.11. I choose the expressinstallation, in order to retain my preferences and settings. Everything went fine. However: Before, I was using the nvidia inspector settings as defined by "Word Not Allowed". Everything was fine with the previous nvidia driver, nice and smooth anti alliasing. With the updated driver, there seems to be the problem, that none of the profile settings work anymore in FSX. The "Word Not Allowed profile" is still available within nvidia inspector and still allocated to fsx. But I seem to be unable to apply the settings to FSX: - no AA at all...! Any thoughts on that? I tried to enable AA within FSX, which works, but it isn't by far as smooth as the Word Not Allowed-setup. As the Word Not Allowed-setup AA is not working in FSX, I presume, that all other settings within that set are not applied to FSX at all as well... Best regards Tom

Hi! I'm considering an upgrade from a GTX760 to a GTX780Ti or even a GTX980. Will it be worth the money ( considerable improvement )? The card will be used in a i7 4770k @ 4,2GHz / 8GB RAM / WIN7 64bit / PMDG / ASN environment. Best regards Tom

Hi there! I´m facing a strange problem: Almost any time I run FSX ( mostly using PMDG ) I observe the keyboard is not responding after a while. Either it is not responding at all, or the assigned commands are mixed up. E.g. "F7" is assigned to "Flaps extension". However, in some cases "F7" is either not responding any more, or it selects commands, which are not assigned to the key? Sometimes, the keyboard is not responding even after FSX is shut down... Any ideas? Best regards! Toto