by p1nkfl0yd1an on Fri Aug 13, 2010 5:17 am
Surprisingly my e6600 plugged into a board with a 4x Pcix slot combined with an 8800gt runs everything on a mix of medium detail and high textures at 1280x720 on a 50something inch HDTV via DVI->HDMI cable with no problems. That being said, it was totally worth 30 dollars. I don't know if it's just the nature of the engine or what, but it still "feels" very much like a battlefield game. It's tough to describe this in a manner that makes it sound like I'm NOT bashing the engine, but it always seems like with a game on this scale, the engine has to do funny things to keep track of your one pathetic little soldier... it leads to a very distinct experience, one which I enjoyed for WEEKS worth of time on 1942, and this is no different. I miss being able to plane whore to my hearts extent.
I only have one complaint, and it's a minor one at that. I was a HUGE fan of the 1942 mod Desert Crisis. If anyone played the VERY early versions of DC, you'll remember what a challenge learning to fly the helicopters was. However, this was because the nature of the piloting system was such that it allowed you to pull off RIDICULOUS turns on a dime, pinpoint maneuvers, and in general feel like you were really flying a nimble attack helicopter... but getting the hang of it was DIFFICULT. Anyway, the helicopters in BC2 are slow to respond, prone to fits of lag, and worst of all, aren't even coded correctly to operate with usb joysticks. If you just plug and play, you'll quickly find that for whatever reason, the yaw axis is backwards. Twist left? You pivot right. Twist right? You pivot left. This has apparently been an issue with BC2 on the PC since the beta stages, but EA/DICE never got around to fixing it. The fix? Go into the .dbx file for air and change a single line of code in which the value is set to "1"... to "-1"(thank god some knowledgeable users on the EA forums figured this out for everyone else)
All in all you're just another brick in the wall