FSX-MS Wrong Monitor

[sdenton]

When FSX starts up it always on the wrong monitor??? I have Google it with no fix.....Thanks for any help

[Jim Young]

Before you shutdown FSX, make sure the sim is on the right monitor.  When you restart, it should appear on the same monitor used when you quit.  Same goes with full screen mode and Windows mode.  If you shutdown in Windows mode, it will start up in Windows mode.

[sdenton]

I'am shutdown in the right monitor but when I re start FSX it goes right back to the wrong monitor...I look in CFG. file could not find any thing so I back it up and got a new int stalled but no change...

[bobbyjack]

Monitors are assigned a number priority that I thought you could change. Either in the software or by where they are plugged in. But it's been along time since I used multiple monitors.

[Enko]

In Windows you could set the monitor you want to use as the main monitor?

[Jim Young]

12 hours ago, sdenton said:

shutdown in the right monitor but when I re start FSX it goes right back to the wrong monitor.

As others have suggested, make sure the monitor is your main monitor.  FSX probably thinks it is opening and closing on your main monitor.  On your desktop, right click and select NVIDIA Control Panel.  Goto Setup multiple displays and make sure the main monitor, whether numbered 1 or 2, is shown left of your secondary monitor.  You can go to multiple displays and drag the monitor you consider your primary monitor.  In my case, my 34" monitor is shown as 2 and my 25" monitor is shown as 1 but FSX always opens on Number 2.

[sdenton]

Yes I look and my #1 monitor is my primary #2 is extended so switch the cables all it did was change the numbers it still started in wrong one?? 

[Jim Young]

I definitely have no other solution.  Hope you find a fix.

[sdenton]

Thanks it is ok at least I can fly 

[Jim Young]

This is a possible solution - https://www.thewindowsclub.com/desktop-icons-moved-primary-to-secondary-monitor.

[Surfaceflying]

I don't know if you have solved this issue or not. However, the solution is to untick the DX10 preview. This is most likely due to a conflict with a newer version of the DirectX software. I hope this helps you.