BF2142 Patch

Shockeh

<div class="IPBDescription">EA has outdone itself</div>You know, just when I thought EA could possibly not go lower in my expectations...

Hurray, EA have released a patch for BF2142. Shall we go through the Readme?

<!--QuoteBegin-"BF2142 Patch Readme.txt+--><div class='quotetop'>QUOTE("BF2142 Patch Readme.txt)</div><div class='quotemain'><!--QuoteEBegin-->Players who have the Windows security update KB917422 installed may suffer from an application error when running Battlefield 2142. This error can be solved by uninstalling the KB917422 update.<!--QuoteEnd--></div><!--QuoteEEnd-->

Ooh, that's interesting. So, in order to play BF2142, you need to uninstall a <i>critical security update</i> for my Operating System. Now, let's see what that update did, shall we?

<!--QuoteBegin-"Microsoft.com"+--><div class='quotetop'>QUOTE("Microsoft.com")</div><div class='quotemain'><!--QuoteEBegin-->Supported Operating Systems: Windows XP Service Pack 1; Windows XP Service Pack 2

A security issue has been identified in the Windows Kernel that could allow an attacker to compromise your Windows-based system and gain control over it. You can help protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer.<!--QuoteEnd--></div><!--QuoteEEnd-->

Perhaps you need to uninstall it as it's blocking EA. I mean, it's meeting a lot of the requirements for a virus at this point. Please, someone, defend this. I'd love to see it this time.

- Shockwave

RustySpoon

But the game still rocks, so ein fuhrer ein reich ein EA <img src="style_emoticons/<#EMO_DIR#>/sad-fix.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad-fix.gif" />

TychoCelchuuu

God, suddenly it's EA's fault for Windows screwing something up? Windows Security Patches have been known to break many, many games before, not just BF games. The game is designed to utilize certain DLLs and then the security patch blocks access. There's nothing EA can do about it. I have seen Warzone 2100, Splinter Cell: Chaos Theory, Dungeon Siege II, and BF2142 broken by security patches. This is not the first time, nor is it the last time if Microsoft keeps putting out these bandaid fixes without addressing the root of the problem.

Of course, you probably won't get this with Vista, since they redesigned the architecture and stuff. Until then, ITS NOT EA'S FAULT STOP TAKING EVERY OPPORTUNITY TO PICK A FIGHT WITH THEM WHEN THEY HAVE DONE NOTHING WRONG THIS TIME.

Shockeh

Tycho:

I'd actually agree with you were it not for one. simple. little. thing.

Release date on KB917422: 8/7/2006

EA knew about this long before the actual release of BF2142. But we can't let a little issue like 'not working on the O/S if it's fully patched' get in the way of our almighty Chrismas release, now, can we?

- Shockwave

Talesin

Shockwave, how long do you think it takes to burn a gold master? Much less start main press production, box-stuffing, and inventory prep? Much less shipping?

It's most likely they already were deep in the initial stocking phase before the security patch was released, and faced with either a delay to re-burn and build up new stock, discarding what they already had done on the initial run(s), they figured they could patch it afterward.

So yes. If it's a choice between releasing a game that will glitch due to a dumba$$ Microsoft patch (unless the user uninstalls it), or losing at least half a million in reprinting and sales revenue... I'd release, and then address it in a later patch, when a workaround has been found.

Alcapwn

You guys seem to neglect the fact that the security update affected many games, not just 2142.

So...yeah. Stop hatin.

TychoCelchuuu

If you've built your engine on a certain set of assumptions about access to the OS, and Windows suddenly releases an optional patch that breaks your engine when your game is A FEW WEEKS FROM WORLDWIDE RELEASE, do you reengineer your engine? Here's a hint: no.

Shockeh

I haven't checked the 1.0 Readme, so I can't confirm. Was this an issue in the first release, or introduced by the 1.1 Patch? I suppose that would sway my opinion significantly.

Either way, surely your first patch (in Talesins' situation) would to be to correct this, as the bug is apparently due to where Windows allows file write access during execution. I won't even go into that one, before my get my BOFH hat on.

- Shockwave

Talesin

Short version, no. It's in the initial release, and still affects the 1.01 patched version.

It is not 'highest priority' as the vulnerability that was patched by the security update has not been spotted in the wild, as an actual exploit. The 1.01 patch addressed a number of stability issues with certain hardware configurations, and crashing with some settings in their new gameplay mode. The patch was also in development concurrently with their first-pressing of the game DVD.

The next patch MAY fix the problem if a workaround can be found for the issue. Short version, the issue is a problem on Microsoft's part, who essentially used a sledgehammer where a nail file would have worked, and worked much better.