That would probably explain it, I'm running ATI, so NVidia's NView doesn't quite do things the same way.
It's an inherent difference in how the Video Card handles output.
For Nvidia, no matter HOW you set it up to windows, the Hardware sees it as ONE monitor (i.e. 1600 x 2400, or 3200 x 1200, i never can remember which). This has bonuses and downfalls. Bonuses include simplicity of programming dual monitor for programs in general, but on the flip side, If "one" is rendering 3d, and the other is not, you'll take a bigger performance hit.
For ATI, no matter HOW you set it up to windows, the Hardware sees it as two monitors. Bonuses include less of a performance hit for having one monitor doing 3D rendering and the other not (i take 0 performance loss for running like this), but on the flip side, I'm stuck with it sitting in windowed mode, albeit a LOT better than it used to be. =)
This has been in debate for years, actually. NVidia has gotten more companies to code programs to make use of it in a "single display" fashion, but running dual monitor in NVidia has always seen a larger performance loss. This is assuming you mean the 3D program on one monitor, and standard windows stuff on the other (browser windows, etc). For Dual monitor 3D rendering (i.e. stretching EQ2 over both monitors), Nvidia does slightly better performance wise (but they both still take a HUGE hit).
I will see what I can get to work in the mean time. =)
ATI has a multi-monitor program that's meant to be used when doing dual monitors. I'll DL that and see if it makes a difference. If it does, I'll post it here for all the ATI users.
|