Let's back up a bit. I was complaining about the demo shown, which was single-player. It is entirely possible that those elements are toned down in multiplayer and I won't have issue. I played the BC2 campaign and hated that for how I was shooting at silhouettes so fricking often. I never got around to the multiplayer. It's entirely possible they reserve the over-emphasis on atmospherics in SP to compensate for some performance issues. Who knows? It was just a little too convenient in BC2's campaign that every time I was about to get in a firefight, I knew because a fog descended on the area and my visibility went to crap.
The last BF game I put any time into multiplayer was 1943 and I didn't have a problem, so I'm hopeful that it's just the BF3 campaign that I will have to avoid like the plague. I mean, you can talk about 250m, but in that demo, those shits were 15 meters away at most.
Last edited by ejburke; March 5th, 2011 at 10:11 PM.
Yeah there's your problem, never ever ever judge a BF game based on its single-player
I personally never have a problem with visibility in BC2 MP, even on the rare occasions I (gasp) go sniper; any time I do, it's because somebody just blew a hole in a building or laid down a smoke grenade, in which case it's perfectly reasonable and justified
BC2's campaign was poorly constructed. I don't think it was the glare killing you so much as the level layout, because every single level forced you through god damn bottleneck with no cover. The first game's campaign was MUCH more fun because it was open combat and you could achieve your objective however the hell you wanted. THAT was Battlefield. The shit we got in BC2 was them trying to appeal to the Call of Duty crowd. The graphics in campaign and multiplayer are the same, but the way the levels are constructed in single player makes it irritating to deal with.
I can't tell how BF3 will be, that was just a single encounter. I need to see more before I write it off as an extension of BC2's campaign style.
It was the bottlenecking, the scripting, the crappy AI that doesn't know how to interact with destructible environments, and the magic haze that would descend on any set-piece battle, but be nowhere to be found any other time. It wasn't even a matter of being killed. I didn't have any trouble with the campaign on the default difficulty, I just couldn't stand playing it for more than 20 minutes at a time and it took me forever to finish.
The BF3 demo gave me a rage flashback. Maybe I was being too harsh, maybe I wasn't. I don't expect the campaign is going to be any good, but I know the MP is going to be great, even if I would do things slightly differently.
I do lament the loss of crisp, clear graphics in favor of blurred, smeared, bloomed-out, desaturated "current gen" graphics, but the issue is, for the most part, tolerable. And it is not unique to battlefield.
Last edited by ejburke; March 6th, 2011 at 02:00 AM.
Well, BC2 was none of those things except it wasn't very clear and had too much environment effects on the two previously mentioned maps. Otherwise I don't know what you're talking about. It's not so hard to see enemies in the game, and they definitely weren't hard to see in BF3 Demo vid.
Hmm, that's unfortunate, but not the fault of the developers. Halo 2 was a pretty crisp looking game for its time. I doubt ejburke is having this problem he seems to be able to play other games fine. Or that's what it sounds like. Also, what were the specs of the TV when your bro was playing Halo 2? Might not have been his vision but a crappy TV.
Yeah its not that great, but we have been to friends who had high res flat screens (mid 07 before H3 came out) and he still had a really hard time seeing without getting a migraine. It wasnt the devs fault, he just has really bad eyes. One is perfectly okay and the other is really bad. Puting on his glasses is like being drunk in one eye.
My point is that it may be just a problem only Burke is experiencing.
There are currently 5 users browsing this thread. (0 members and 5 guests)
Bookmarks