Anyone that has been around this forum about a year or longer has run across posts about my woes of owning a QUAD-SLI setup and getting it working correctly in 3D Vision and more specifically, and I might add ironically, with Directx 9 games.
I recently iterated some of those troubles [url="http://forums.nvidia.com/index.php?showtopic=196268&st=0&p=1212971&#entry1212971"]here[/url] regarding Crysis 2 since it is [currently] a Directx 9 game.
Well I did some digging this morning, having a hunch in the back of my mind that I could possibly run this in 3D by bypassing Nvidia's USB emitter and just have the game output checkerboard mode to my DLP, SINCE I own a pair of DLPLink glasses too. You see the problem I run into with DX9 and QUAD SLI is that soon as that Nvidia USB emitter kicks in, my graphics cards render the game as if they were using only one gpu and sometimes worse with considerable input lag. Toggling 3D Vision off using CTRL-T, or turning if off completely in the Control Panel, and QUAD SLI kicks in with a vengeance.
Well I found my answer using these variables for Crysis 2:
[quote]
variable: r_StereoDevice DUMPTODISK, REQUIRE_APP_RESTART
type: int
current: 100
help: Sets stereo device (only possible before app start)
Usage: r_StereoDevice [0/1/2/3/4]
0: No stereo support (default)
1: Frame compatible formats (side-by-side, interlaced, anaglyph)
2: HDMI 1.4 (PS3 only)
3: Stereo driver (PC only, NVidia or AMD)
4: Dualhead (PC only, two projectors or iZ3D screen)
100: Auto-detect device for platform
variable: r_StereoOutput DUMPTODISK
type: int
current: 4
help: Sets stereo output. Output depends on the stereo monitor
Usage: r_StereoOutput [0=off/1/2/3/4/5/6]
0: Standard
1: IZ3D
2: Checkerboard (not supported on X360)
3: Above and Below (not supported)
4: Side by Side
5: Line by Line (Interlaced)
6: Anaglyph
variable: r_StereoSupportAMD REQUIRE_APP_RESTART
type: int
current: 0
help: Disables/Enables [0/1] stereo support on AMD hardware[/quote]
I added these variables to my system.cfg file in the root Cyris 2 directory:
I'm now plowing through Crysis 2 with all four of my GPUs scaling nicely and at 60+ frames per second per eye. I really only needed two GPU's to kick in to get 60 frames/eye in 3D, but it makes me smile to see all four of them running properly.
I realize that this is only going to help a very small minority people. A) People that are actually still running the GTX 295 QUAD SLI setup, and B) That you own a DLP and also own a pair of DLP Link glasses.
My other reason for writing this post is to further document my case that the issue isn't QUAD SLI and 3D, but rather QUAD SLI plus the 3D Vision driver in DX9 games (as I have stated tons of times in the past, this is not a problem in DX10), and even more so now that Nvidia has officially released their next gen MultiGPU card, the successor to the GTX 295, the GTX 590.
Anyone that has been around this forum about a year or longer has run across posts about my woes of owning a QUAD-SLI setup and getting it working correctly in 3D Vision and more specifically, and I might add ironically, with Directx 9 games.
I recently iterated some of those troubles here regarding Crysis 2 since it is [currently] a Directx 9 game.
Well I did some digging this morning, having a hunch in the back of my mind that I could possibly run this in 3D by bypassing Nvidia's USB emitter and just have the game output checkerboard mode to my DLP, SINCE I own a pair of DLPLink glasses too. You see the problem I run into with DX9 and QUAD SLI is that soon as that Nvidia USB emitter kicks in, my graphics cards render the game as if they were using only one gpu and sometimes worse with considerable input lag. Toggling 3D Vision off using CTRL-T, or turning if off completely in the Control Panel, and QUAD SLI kicks in with a vengeance.
Well I found my answer using these variables for Crysis 2:
4: Dualhead (PC only, two projectors or iZ3D screen)
100: Auto-detect device for platform
variable: r_StereoFlipEyes DUMPTODISK
type: int
current: 0
help: Flip eyes in stereo mode.
Usage: r_StereoFlipEyes [0=off/1=on]
0: don't flip
1: flip
variable: r_StereoMode DUMPTODISK
type: int
current: 0
help: Sets stereo rendering mode.
Usage: r_StereoMode [0=off/1/2]
1: Dual rendering
2: Post Stereo
variable: r_StereoOutput DUMPTODISK
type: int
current: 4
help: Sets stereo output. Output depends on the stereo monitor
Usage: r_StereoOutput [0=off/1/2/3/4/5/6]
0: Standard
1: IZ3D
2: Checkerboard (not supported on X360)
3: Above and Below (not supported)
4: Side by Side
5: Line by Line (Interlaced)
6: Anaglyph
variable: r_StereoSupportAMD REQUIRE_APP_RESTART
type: int
current: 0
help: Disables/Enables [0/1] stereo support on AMD hardware
I added these variables to my system.cfg file in the root Cyris 2 directory:
r_StereoDevice=100
r_StereoMode=2
r_StereoOutput=2
r_StereoSupportAMD=0
I'm now plowing through Crysis 2 with all four of my GPUs scaling nicely and at 60+ frames per second per eye. I really only needed two GPU's to kick in to get 60 frames/eye in 3D, but it makes me smile to see all four of them running properly.
I realize that this is only going to help a very small minority people. A) People that are actually still running the GTX 295 QUAD SLI setup, and B) That you own a DLP and also own a pair of DLP Link glasses.
My other reason for writing this post is to further document my case that the issue isn't QUAD SLI and 3D, but rather QUAD SLI plus the 3D Vision driver in DX9 games (as I have stated tons of times in the past, this is not a problem in DX10), and even more so now that Nvidia has officially released their next gen MultiGPU card, the successor to the GTX 295, the GTX 590.
I recently iterated some of those troubles [url="http://forums.nvidia.com/index.php?showtopic=196268&st=0&p=1212971&#entry1212971"]here[/url] regarding Crysis 2 since it is [currently] a Directx 9 game.
Well I did some digging this morning, having a hunch in the back of my mind that I could possibly run this in 3D by bypassing Nvidia's USB emitter and just have the game output checkerboard mode to my DLP, SINCE I own a pair of DLPLink glasses too. You see the problem I run into with DX9 and QUAD SLI is that soon as that Nvidia USB emitter kicks in, my graphics cards render the game as if they were using only one gpu and sometimes worse with considerable input lag. Toggling 3D Vision off using CTRL-T, or turning if off completely in the Control Panel, and QUAD SLI kicks in with a vengeance.
Well I found my answer using these variables for Crysis 2:
[quote]
variable: r_StereoDevice DUMPTODISK, REQUIRE_APP_RESTART
type: int
current: 100
help: Sets stereo device (only possible before app start)
Usage: r_StereoDevice [0/1/2/3/4]
0: No stereo support (default)
1: Frame compatible formats (side-by-side, interlaced, anaglyph)
2: HDMI 1.4 (PS3 only)
3: Stereo driver (PC only, NVidia or AMD)
4: Dualhead (PC only, two projectors or iZ3D screen)
100: Auto-detect device for platform
variable: r_StereoFlipEyes DUMPTODISK
type: int
current: 0
help: Flip eyes in stereo mode.
Usage: r_StereoFlipEyes [0=off/1=on]
0: don't flip
1: flip
variable: r_StereoMode DUMPTODISK
type: int
current: 0
help: Sets stereo rendering mode.
Usage: r_StereoMode [0=off/1/2]
1: Dual rendering
2: Post Stereo
variable: r_StereoOutput DUMPTODISK
type: int
current: 4
help: Sets stereo output. Output depends on the stereo monitor
Usage: r_StereoOutput [0=off/1/2/3/4/5/6]
0: Standard
1: IZ3D
2: Checkerboard (not supported on X360)
3: Above and Below (not supported)
4: Side by Side
5: Line by Line (Interlaced)
6: Anaglyph
variable: r_StereoSupportAMD REQUIRE_APP_RESTART
type: int
current: 0
help: Disables/Enables [0/1] stereo support on AMD hardware[/quote]
I added these variables to my system.cfg file in the root Cyris 2 directory:
r_StereoDevice=100
r_StereoMode=2
r_StereoOutput=2
r_StereoSupportAMD=0
I'm now plowing through Crysis 2 with all four of my GPUs scaling nicely and at 60+ frames per second per eye. I really only needed two GPU's to kick in to get 60 frames/eye in 3D, but it makes me smile to see all four of them running properly.
I realize that this is only going to help a very small minority people. A) People that are actually still running the GTX 295 QUAD SLI setup, and B) That you own a DLP and also own a pair of DLP Link glasses.
My other reason for writing this post is to further document my case that the issue isn't QUAD SLI and 3D, but rather QUAD SLI plus the 3D Vision driver in DX9 games (as I have stated tons of times in the past, this is not a problem in DX10), and even more so now that Nvidia has officially released their next gen MultiGPU card, the successor to the GTX 295, the GTX 590.
I recently iterated some of those troubles here regarding Crysis 2 since it is [currently] a Directx 9 game.
Well I did some digging this morning, having a hunch in the back of my mind that I could possibly run this in 3D by bypassing Nvidia's USB emitter and just have the game output checkerboard mode to my DLP, SINCE I own a pair of DLPLink glasses too. You see the problem I run into with DX9 and QUAD SLI is that soon as that Nvidia USB emitter kicks in, my graphics cards render the game as if they were using only one gpu and sometimes worse with considerable input lag. Toggling 3D Vision off using CTRL-T, or turning if off completely in the Control Panel, and QUAD SLI kicks in with a vengeance.
Well I found my answer using these variables for Crysis 2:
I added these variables to my system.cfg file in the root Cyris 2 directory:
r_StereoDevice=100
r_StereoMode=2
r_StereoOutput=2
r_StereoSupportAMD=0
I'm now plowing through Crysis 2 with all four of my GPUs scaling nicely and at 60+ frames per second per eye. I really only needed two GPU's to kick in to get 60 frames/eye in 3D, but it makes me smile to see all four of them running properly.
I realize that this is only going to help a very small minority people. A) People that are actually still running the GTX 295 QUAD SLI setup, and B) That you own a DLP and also own a pair of DLP Link glasses.
My other reason for writing this post is to further document my case that the issue isn't QUAD SLI and 3D, but rather QUAD SLI plus the 3D Vision driver in DX9 games (as I have stated tons of times in the past, this is not a problem in DX10), and even more so now that Nvidia has officially released their next gen MultiGPU card, the successor to the GTX 295, the GTX 590.