Hey everyone,

This is not going to be an easy one to solve (i think), but I hope someone on these forums can help me out! I have a Samsung 2233RZ monitor that is compatible with 3D Vision. However, I decided to implement my own 3D system for the hell of it (see this thread).

Results have been positive and I am now gaming happily this way. However, there is still some slight ghosting in the top of the screen. I have done some research, and found out that with 3D vision, the 2233RZ enters a special display mode that is normally inaccessible. This mode has a higher horizontal refresh rate than normal, meaning the frame has more time to stabilize and the shutters can be open longer without getting ghosting due to the next refresh cycle. Normally the monitor runs at 120Hz vertical, 129kHz horizontal. In this special mode, it turns into 120Hz vertical, 185kHz horizontal!

I need to access this display mode if I want my ghosting issues completely gone. I can tweak every aspect of my own shutterglass system (timings for each eye, duty cycle of shuttering, eye switch), but have noticed that it is simply impossible to eliminate ghosting completely without this special display mode used by 3D Vision.

The closest I have seen anyone come to deciphering the exact display timings for this mode was in this thread: NVidia Forums. Here the topic was on how to activate the 3D Vision mode under Linux. One user (Keitht) managed to make Powerstrip do a readout of signal parameters during 3D operation, although the resulting data seemed to be faulty.

I am still hoping someone knows how to figure out the exact display timings I need to make the monitor operate at the aforementioned frequencies! Any geniuses out there?

I myself am not an owner of a 3D Vision kit, nor an Nvidia card. I tried reading out the EDID of the monitor, but I couldn't find any info about resolution modes and timings supported by the monitor that way (all the other info was retrieved, but somehow the timings were all 0).

Maybe you need an Nvidia card to find this information. I contacted NVidia customer support and they said that in the Nvidia graphics drivers, there is an option to view all the EDID display modes supported by the monitor.

Could someone on this forum who has a 3D Vision kit with a Samsung 2233RZ maybe dive into his drivers for me, and try to find the timings supported by the monitor?

...Or are there any other clever ideas?

I have the Samsung 2233 with Nvidia 3D vision, and I can confirm that when the 3D mode is activated it goes into a frequency of 185.2kHz. In 2D operation, the value is 129.5. As to how to activate this mode without the Nvidia drivers, I'm afraid I won't be much help, unfortunately; I've had a look around the Nvidia control panel and there is nothing obvious that I can see that allows you to control it manually.

On a side note, I would say that this monitor is very prone to ghosting when running in 3D mode. A number of reviewers have noted that it is worse on this monitor than on many other models, so it may be that you will not be able to improve the picture that much. (This is one of the reasons I will always prefer Head-Mounted Displays: no loss of brightness and no ghosting!)

Good luck with your project; it sounds really interesting!

Too bad, i guess it would've been too easy if the information was simply listed in the Nvidia control panel... Thanks for trying though!

I also read that this monitor has some ghosting issues on 3D Vision. I might not be able to eliminate it completely, but I'm guessing it will at least improve!

Well, no surprises there...

--edit--: I also got my hands on a service manual, but that didn't mention anything about display modes at all. Samsung tech support here in the Netherlands didn't know anything.
I had a quick look at the capabilities of the DDC line. I didn't know that it can not only be used to read out EDID, but it does other stuff as well; f.e. set brightness/contrast and such from the computer. Could be that that's the way monitor settings are locked by NVidia, but it seems highly likely that they added some proprietary communication sequence over DDC to get the monitor in 3D mode - in that case i'm basically screwed.