Even though the title had native support for only AMD HD3d, which was still welcomed and good, the title is also going to have support for 3d vision and 3d vision Surround as well in a future patch.
http://forums.nvidia.com/index.php?showtopic=210263&view=findpost&p=1293463
That is good news.
Just a little follow up, since the game only support HD3D, others who use other means of 3D are left out. Of those, 3d vision users cried out loud in comparison. Usually Nvidia is quick on fixing things like that, but lately it seems to have dropping balls on game support. The one sticky post from Nvidia forum is lead by a mod asking the game dev to add 3d vision support nicely, which is, to me, finger pointing. I lost my hope on that game.
Until one day, a poster, rajkosto at Dx:HR forum, rajkoderp at Nvidia forum, came up with an interesting code, a dx code wrapper which hijacks the dx api calls and rerouted in a way that it works for 3D vision. In simple terms, HD3D puts the image to the left eye and the top and the right eye at the bottom and then render, where 3D vision requires the left eye image at the left, right eye image at the right + 1. In other word(Rajkosto's word), 2xheight for AMD, 2xwidth+1 for Nvidia. That is, if the calls can be hijacked, then the cost of re-ordering the left/right image is really small.
Well, it isn't surprising why rajkosto became the new hero on DX:HR, someone who does something for everyone for free. Although the code is not perfect, the fact it works lead to new questions.
A)If a user can write a code to fix it, then why Nvidia said they can't?
B)Why didn't the game add such a simple change before release?
C)Minimium depth, 0 convergence. Why?
D)"If the SLI engine was smart, it would figure out that the 2 renders to the 1x res rendertarget are independent, and do them in parallel, but unfortunately it isn't", rajkosto, Nvidia forum post 237.
Now he action is far more effective then forum partition post as he showed the possibility of making 3D work without having access to game code or driver, just redirecting calls that are suppose to end up at AMD's HD3D API into Nvidia's 3d vision with a little translation. That is:
Eidos: -1
Nvidia: -1
AMD : I am innocient.
rajkosto: +1000
With the latest patch, depth increases as the seperation increases and the announcement of 3d vision support is made.
Here is the site to get the wrapper, as well as detail usage and bugs with the wrapper.
http://rajko.info/hd3d/