![]() they're running in 32 bit mode on both systems, so no differences there: Here's how it SHOULD look after this step, and does look on my OTHER Windows 7 圆4 machine: It's NORMAL for the PFD to flash red x's for a moment, but once the two simulators have their UDP connections (cross-talk) established, then the red x's go away on my good system.įinally, the MFD comes up, but now it's in reversionary mode, because of the communication link failure between the two displays: PFD is in automatic reversionary mode because the MFD is powered down:Īs soon as I power on the MFD, and the second CDUSIMv2 process launches, the PFD loses all signals. I'm launching them from Garmin's Start Dual Screen batch file, which executes these two commands:Īfter powering up the PFD, we get this (exactly the same as on the other working system).Īfter a few moments, the Terrain functionality self-checks and we get SVT on the PFD. I believe it's a UDP communication problem between the two CDUSIMv2 processes. Here's what I'm seeing, and what I've looked at or tried. of course, it's my best, fastest, dual monitor system, and that's the one where I want to run this. I'm having some trouble with the dual-screen trainer on ONE of my two Windows 7 圆4 systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |