I run TH2Go de too with a 46" 3d LG off the HDMI.

 

My problem since going to DX10 is that 1. It comes up in windowed mode, can't seem to change it? 2. It came up in the left monitor to start with but I drug it to center screen, maximized, and it comes up there now in windowed mode but I still have to Alt/Enter to go to full screen. Never did that in DX9

 

Any ideas

Rick S.

Paul,

3x23 and one 12" touch.

I tried the tidy up cable stunt, and left the Matrox out and went surround, unfortunately for me, I couldn't get rid of the task bar from the centre screen and with the touch screen I have, win7 64 bit wouldn't co-operate with the 4th screen. (Did with another small screen I had laying about.)

So it was back to the matrox and it works better than ever. :lol:

Running windowed mode and maximized.

 

Track IR gave me a problem last night, BSOD, still running default cpu settings, until I OC to about 4.6, just moving slowly in rebuild.

Hmmm.. thanks, Trevor... so the message looks like "If it ain't broke, don't fi..........!" I'll leave well alone.

 

Hi, Rick - TH2Go is a serious pain to set up, sometimes, but there is an answer to this one - however - I have to dig it out from the gazillions of files on this pc.... :lol:

 

Back later..

 

pj

Thanks Paul, seemed a bit strange; work perfect in DX9. I have been through the cfg over and over and don't see anything there that gets my attention.

I used to play "Empires: Dawn of the Modern World", Rick - and it would ALWAYS open in the left screen. I did find one post on the web two or three years (6) ago, but i have no idea where it is now.

The Matrox instructions are still poor, but not quite useless.

 

http://www.matrox.co...en/support/gxm/

 

Edit: there looks to be a slew of TH2G on YouTube..

 

pj

Hi Paul:

 

Would you please also address the role played by the "Location=" parameter in FSX.Cfg ? :Nerd:

 

 

FYI: Curious examples from my FSX.Cfg for a Radeon HD 7970 with 2 monitors at 2 different resolutions: :Thinking:

 

 

[Main]

Location=0,3,1280,960,\\.\DISPLAY2

 

 

[Weather]

[DISPLAY.Device.AMD Radeon HD 7900 Series.0]

 

 

[GRAPHICS]

[DISPLAY.Device.AMD Radeon HD 7900 Series.1]

 

[Trusted]

[DISPLAY.Device.AMD Radeon HD 7900 Series.0.0]

Mode=1280x960x32

Anisotropic=1

 

[DISPLAY.Device.AMD Radeon HD 7900 Series.0.1]

Mode=1024x768x32

 

 

NOTE: FSX always starts properly centered on the intended "Display 2" monitor at 1280x960x32

 

 

Thanks, :smile:

 

GaryGB

I have the same problem but I seemed to fix it when I close FSX in windowed mode. When it opens up again it is in Windowed mode on the correct panel and once I am all setup and have moved my panels to the second screen, I go full screen and its all good.

 

Another anomaly with DX10 mode is if you undock only one panel and go to full screen you get a never ending blue ring (working) from Windows7. Undock a second panel and it goes away, and if you then close that second panel, it stays away with no problems. Weird.

Hi Paul:

 

Would you please also address the role played by the "Location=" parameter in FSX.Cfg ? :Nerd:

 

FYI: Curious examples from my FSX.Cfg for a Radeon HD 7970 with 2 monitors at 2 different resolutions: :Thinking:

 

[Main]

Location=0,3,1280,960,\\.\DISPLAY2 <-- This is the "Windowed Mode" screen location of a window on a 1280 x 960 monitor. In FSX's case - this will be the position of the opening screen for FSX's Windowed Mode.

 

 

[Weather] The Display Device is it's own section header - not Weather

 

[DISPLAY.Device.AMD Radeon HD 7900 Series.0] Port identifier

 

 

[GRAPHICS] The Display Device is it's own section header - not Graphics

 

[DISPLAY.Device.AMD Radeon HD 7900 Series.1] Port identifier

 

[Trusted] The Display Device is it's own section header - not Trusted

 

[DISPLAY.Device.AMD Radeon HD 7900 Series.0.0] Port identifier

Mode=1280x960x32 Monitor is attached and this is the user-selected resolution within FSX.

Anisotropic=1

AntiAlias=1 <----------- Must add this here

 

[DISPLAY.Device.AMD Radeon HD 7900 Series.0.1] Port identifier

Mode=1024x768x32 Monitor attached

 

 

NOTE: FSX always starts properly centered on the intended "Display 2" monitor at 1280x960x32

...................Because of that line at top.

 

If you go into Start-->All Programs-->Accessories-->Paint, Left-click a rectangle in "Shapes", your mouse pointer becomes a cross, and when the left mouse button is pressed - that spot becomes the top-left corner of a box. If you now keep the button pressed and you drag it down at say 45 deg - a box will form, and wherever you let go of the button - that will be the bottom-right corner. You will have a nice, black rectangle!

 

"0" - identifies the starting column of the window box. It is the furthest left column on the screen

"3" - third row down from the top, so the top-right "box corner" pixel is at column "0" and third row down.

 

"1280" - identifies the furthest pixel on right of the window box

"960" - bottom row down from the top of the screen.

 

I hope this is what you wanted!! :lol:

 

pj

 

 

Thanks, :smile:

 

GaryGB

I have the same problem but I seemed to fix it when I close FSX in windowed mode. When it opens up again it is in Windowed mode on the correct panel and once I am all setup and have moved my panels to the second screen, I go full screen and its all good.

 

Another anomaly with DX10 mode is if you undock only one panel and go to full screen you get a never ending blue ring (working) from Windows7. Undock a second panel and it goes away, and if you then close that second panel, it stays away with no problems. Weird.

 

I just discovered this myself this afternoon. Go to Windowed Mode before shutting down and it will start up in Windowed Mode and there is no longer a StackHash error when I close FSX. In full screen I'll get the StackHash error always. This is good info to know in case others run into this issue with dual monitors.

 

I also saw the anomaly when I undock the GPS gauge and move it over to the 2nd monitor (in full screen) it will be okay until I try to resize it. Doing so will result in that never ending working ring. I tried undocking another window and closing the GPS gauge but it would not work. Still have the working ring. Goto Windowed Mode and there's nothing on the 2nd monitor but the working ring still persists. The only way I can stop this is by resetting fsx or shutting it down. I got the idea of moving a gauge over to the black 2nd monitor (in full screen) from that first video Paul provided in Post#2. I could even put the wing view over to the other monitor. It's not all that clear though and it looks like it is taking up resources (although FPS remain the same). Learning new things every day. Getting rid of the StackHash error when closing FSX was major and now that has gone away but think my video card GTX580 is not fully seated as the Nvidia driver program won't install new or updated drivers. Windows update or going into the Device Manager and selecting update my drivers and showing the location of the Nvidia driver update program works. Still Nvidia says I have no video card compatible with their drivers. Thanks Mark.

 

For PJ: I could understand your excellent explanations in the above posts #23 but my main location line reads:

 

[Main]

Location=825,323,1865,1101,\\.\DISPLAY1

 

I don't see the resolution as my full screen is 2560x1600. As I stated here I open up my FSX in Windowed Mode now and it is much, much smaller but still can't see the screen size. Not a biggie. I guess I should close in Windowed Mode with the max size.

 

Best regards,

Jim

Hi Jim;

2560 x 1600 is your resolution. The numbers are column and row. The first pixel in the monitor will be (V) Column 0 @ (H)Row 0 , the last one will be (V)Column 2560 @ (H)Row 1600

 

so, the first pair of numbers in "Location" is the position of the the top, left corner of your FSX window. It will be how far it is along that first horizontal row - 825 pixels, and then how for down. It will be 323 pixels down on the 825 vertical column. That point will be the top, left corner of your opening "Windowed Mode" window. The second pair of numbers are 1865 across, and 1101 down. This will be the bottom-right corner of the box - the "window".

 

You won't see any screen size anywhere except with one of the Microsoft developer tools, but I must say I'm glad you're getting closer to an answer.

 

pj

I also saw the anomaly when I undock the GPS gauge and move it over to the 2nd monitor (in full screen) it will be okay until I try to resize it. Doing so will result in that never ending working ring. I tried undocking another window and closing the GPS gauge but it would not work. Still have the working ring. Goto Windowed Mode and there's nothing on the 2nd monitor but the working ring still persists. The only way I can stop this is by resetting fsx or shutting it down.

 

 

Hi

I have the same problem when resizing GPS or other gauge windows.

 

I can usually solve the problem by undocking another window and then re-docking that window again; then out of nowhere the GPS or whatever other window went astray reappears in whatever window I had placed it.

 

Also found out that my main window position was misplaced in the fsx.cfg to x:-8, y: -8. I corrected that to 0, 0 and was able to resize the windows without issues. The problem is that if I resize the main window during next session it reverts back to -8, -8 and problem arises again.

 

Somehow the dammed FSX or nVidia driver is miscalculating window sizes and coordinates.

 

Cheers.

Hi Ramon! Thanks for the info. I recall doing that a few days ago (undocking another window and then redocking the window again) but it didn't work today for some reason. I most likely messed up somewhere. I think Nvidia has issues with two or more monitors. Of course they will blame it on FSX or Windows 7 and Microsoft will blame it on the display driver. Thanks again for your help!

 

Best regards,

Jim

...and some FSX users will blame it on Microsoft ACES bad coding.....

StackHash error (did not know it was called that) is another benefit. Same here closing in full screen you get the error, close windowed no error. As for the undocked panels, as long as you have more than one (set in windowed mode first) you will not have a problem, if you close them after you are all set up in full screen mode, no problem either.

Thanks for the tip Mark, i'll try that tonight.

 

...and some FSX users will blame it on Microsoft ACES bad coding.....

 

Of course Paul, I forgot about the EX-ACES team.

 

The only ones not to be blamed is US.