Hi, I just got my 3d vision kit, and I'm trying to set it up with a CRT monitor. I am having some very frustrating problems. Basically, I'll just lay it out like this:

1. Game has the resolution I need in the in-game display config, say 1280x1024, and works fine.
2. I add a custom resolution in Nvidia's control panel of 1280x1024, but I set the refresh rate to something high like 110 or 120hz, which is necessary for 3d vision
3. I test the resolution/refresh rate in windows, and it works fine
4. I go back into the game and now the resolution is no longer available on the display config screen. It has been removed!

Every time I add a new custom resolution to change the refresh rate to something high, the resolution won't show up anymore in the game. I've confirmed this happens in a whole set of games, such as Oblivion and Dragon Age, so s the underlying problem caused by something not game-specific, like directx? (Crysis seems to work, that is, let me choose the custom resolutions)

This is extremely frustrating and I'm at my wits end as to how to make these games stop removing my resolutions!

Please help.

Well, what I figured out how to get the games to "see" a custom resolution, and that was by adding some new custom "resolutions" with typical refresh rates like 85hz. So, apparently directx or something doesn't like high refresh rates. So as of now i have two custom "resolutions": 1400x1050@110hz and 1400x1050@85hz, and at least the games can "see" the 1400x1050 option. Of course I still have a problem, which is how to get the game to load the higher refresh rate. The windows desktop has no problem with 110hz (or 100hz). Is there a way to lock the refresh rate so that the game can't change it? The 3d vision option of "Apply this refresh rate to all games" doesn't work!

Well, I figured out a solution of sorts, here is the link to the thread i opened over at nvidia forums:

http://forums.nvidia.com/index.php?show ... try1190327

The problem is actually with Windows Vista/7 and what Microsoft did with the display driver model (and how this interacts with DirectX). There may be some hacks you can do, like what is posted in that thread, but it is a fundamental limitation of these new operating systems (unless Microsoft releases a patch, but I doubt they care about the niche of 3D gamers using CRT monitors). Of course if you are using a modern 120Hz LCD panel, then special effort was made to ensure that these are recognized correctly (since that info is all contained in the EDID and registers via plug & play with Windows). Probably not too much you can do to actually fix this, although you may hopefully find some work-arounds.