Hi,
I've read through the other topic regarding this and they don't provide too much help on this topic.

I own a ATI HD 5850 card that is 3D stereoscopically capable, I have the latest drivers installed (11.5) and I have a hdmi 1.4a 3dtv (acer hd244hq) and the stereo option is greyed out for me. I can get stereo working on many pc games using tridef, but i would prefer to use the 3d made specifically for the game rather than a profile on ignition if possible.

I've already read that you can insert the stereo commands into the system.cfg file. I have tried this with no success. The game.txt output file has the following lines in it:
[Warning] Unknown command: sys_game_folder
[Warning] Unknown command: sys_dll_game
[Warning] Unknown command: sys_user_folder
[Warning] Unknown command: r_StereoDevice
[Warning] Unknown command: r_StereoMode
[Warning] Unknown command: r_StereoOutput
[Warning] Unknown command: r_StereoSupportAMD
[Warning] Unknown command: r_ShaderCompilerServer
[Warning] Unknown command: log_IncludeTime
[Warning] Unknown command: log_verbosity
[Warning] Unknown command: sys_PakLogInvalidFileAccess
[Warning] Unknown command: sys_float_exceptions
Which makes me think that it isn't loading things from the system.cfg file correctly. Any thoughts?

Outside getting the amd stereo support working, does anyone know if the Above-below stereo option will become usable soon? my 3dtv sadly can only take above/below 3d (on 720p/60,1080p24 like all 1.4a 3d). usually amd hd3d can handle this ok and most of the time i don't need to worry about this but i read in another thread here that the a-b type is not supported yet.

I'm a little saddened that the 3D option on Crysis2 seems to still be a WIP.. can anyone advise me what to do?

Wait. Unfortunately, Crytek turned off the 3D ability for AMD/ATI cards with patch 1.4. I had it working before the patch by adding this line to my system.cfg file, r_amdstereosupport=1. Once I installed patch 1.4, my config stopped working. We'll have to wait for them to unlock it again with another patch, or try un-patching back to 1.2.