Setup Nvidia and Portrait Landscape Portrait Monitors
Jul 19, 2016 8:16:16 GMT
Post by dfr on Jul 19, 2016 8:16:16 GMT
If you have an AMD video card you can ignore this post.
I have an Nvidia 980Ti and I wanted to use 2 x 27" monitors in portrait mode (800x1280) and a 40" TV in landscape (1920x1080). These sizes work well because of their size and similar dot pitch at these resolutions.
Nvidia surround won't work because it will only setup monitors with an identical resolution and orientation. I searched for a solution but the only advice I found was to use SoftTH. Unfortunately on my PC SoftTH crashes FSX 60 seconds after it starts.
Through experimentation I stumbled across a "working" solution. It's not perfect but I am satisfied and it might help others.
1. In the nvidia control panel, create a custom resolution for your main monitor that is the size of your desired screen size. For me, it was 3520x1280. You don't permanently set this resolution on your monitor, you're just creating it as an option. If you don't know how to do this look it up on google. Make sure the refresh rate is 60Hz (for some reason 75Hz wouldn't show up in FSX).
2. Start flying FSX in window mode and stretch the window size to cover all your screen area, ie 3520x1280. Initially FSX will only draw using the resolution of your main monitor, in my case 1920x1080. Everywhere else it was black, sometimes red.
3. Open display options, select your custom resolution, press OK and it takes you back to FSX. Then left click anywhere in the area that FSX is running and it will magically fill up the entire screen area.
It's not perfect because if you click outside of the original screen area (1920x1080) it will revert back to it's original 1920x1080 space. If if it does revert, just do step 3 again.
I use it in Cockpit mode or VC mode for outside viewing and while using an undocked screen in a fourth monitor for instruments.
This is the first time I've used FSX and I have only tried it in a couple of default planes. I tested it in DX10 preview mode and with a few other configuration options and they all seemed to work.
Maybe it was the way Microsoft intended it to work but never got the bugs worked out.
I have an Nvidia 980Ti and I wanted to use 2 x 27" monitors in portrait mode (800x1280) and a 40" TV in landscape (1920x1080). These sizes work well because of their size and similar dot pitch at these resolutions.
Nvidia surround won't work because it will only setup monitors with an identical resolution and orientation. I searched for a solution but the only advice I found was to use SoftTH. Unfortunately on my PC SoftTH crashes FSX 60 seconds after it starts.
Through experimentation I stumbled across a "working" solution. It's not perfect but I am satisfied and it might help others.
1. In the nvidia control panel, create a custom resolution for your main monitor that is the size of your desired screen size. For me, it was 3520x1280. You don't permanently set this resolution on your monitor, you're just creating it as an option. If you don't know how to do this look it up on google. Make sure the refresh rate is 60Hz (for some reason 75Hz wouldn't show up in FSX).
2. Start flying FSX in window mode and stretch the window size to cover all your screen area, ie 3520x1280. Initially FSX will only draw using the resolution of your main monitor, in my case 1920x1080. Everywhere else it was black, sometimes red.
3. Open display options, select your custom resolution, press OK and it takes you back to FSX. Then left click anywhere in the area that FSX is running and it will magically fill up the entire screen area.
It's not perfect because if you click outside of the original screen area (1920x1080) it will revert back to it's original 1920x1080 space. If if it does revert, just do step 3 again.
I use it in Cockpit mode or VC mode for outside viewing and while using an undocked screen in a fourth monitor for instruments.
This is the first time I've used FSX and I have only tried it in a couple of default planes. I tested it in DX10 preview mode and with a few other configuration options and they all seemed to work.
Maybe it was the way Microsoft intended it to work but never got the bugs worked out.