jonstatt Posted June 14, 2010 Posted June 14, 2010 1.0 and 1.0.1c work perfectly the nVidia 3D vision and for me at least, adds a lot to the simulation. But 1.0.2 breaks nVidia 3D completely. The nVidia Drivers no longer detect the profile for the game (the binary must have changed so much that they no longer recognise which game is playing). And although 3D mode still engages, it is completely messed up with each eye getting totally the wrong image. I reverted back to 1.0.1c and it works again.
EtherealN Posted June 14, 2010 Posted June 14, 2010 Binary used to be dcs.exe It is now simulator.exe [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
jonstatt Posted June 14, 2010 Author Posted June 14, 2010 Binary used to be dcs.exe It is now simulator.exe Would you suggest I re-install 1.0.2 and rename simulator.exe to dcs.exe and see what happens? Or is that likely to break something else, such as when going from the menu screens to the simulator and back etc....? Thanks, Jonathan
EtherealN Posted June 14, 2010 Posted June 14, 2010 I would not expect things to work with a renamed executable. Specifically because other portions of the simulator are hardcoded to call for simulator.exe, and if you rename it they'll break. Basically: say goodbye to singleplayer. Better option would be to see if you can make your 3D drivers associate to simulator.exe instead of dcs.exe. This is a much easier fix. [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
FRA599 Posted January 13, 2011 Posted January 13, 2011 I had the same issue but in fact it works perfectly now. What you have to do is adjust in-game 3D vision convergence. It will fully solve the problem. Google is your friend.
Recommended Posts