So I finally made the leap and got a 3D monitor with nVidia 3D Vision so that I can play one of my all time favorite games in glorious real 3D, but I've encountered some major issues with my first time using it.
I installed the hardware today and tested it first with MWO (I did enable the option and restarted the game) and saw that 3D Vision didn't automatically engage. I found nothing searching online, so I tried with Diablo 3 and it worked the first time. On a hunch, I tried running the game Full Screen instead of Windowed and it did turn on like it was supposed to. I suggest that in a future patch, a prompt should pop up when enabling 3D vision that it might not work unless the game is run Full Screen. A similar prompt should pop up when changing from Full Screen to Windowed with 3D Vision enabled.
After the successful launch, I was rather disappointed that the mechbay was really flat; the UI was the only thing that was popped out. The mechs were shown the same way they look in 2D mode. I was not happy with that.
The real disappointment came when I did a test run on a Testing Ground map.
http://steamcommunit...s/?id=647138255
As you can see, the cockpit of this Ebon Jaguar has some texture issues and the depth slider for 3D Vision did nothing at all. They do fix themselves on occasion, but it's mostly this odd refraction look. Another eyesore was the targeting reticle. It was never in focus. It would look right when I was looking far away, but became unfocused (double vision) when I was focusing on a close range enemy. About less than 250 meters is when the focusing goes whack. I suggest either using one side for the targeting reticle, or having it's depth change based on the arm cursor's reported distance as I personally focus on my enemy to try and hit vulnerable parts, but it's hard to do when the cursor is split in two.
Until that last issue is addressed, I will just use normal 2D mode.