Where is the Forum Mod? Why no Stickies to Fixes here?

[FreemanForPrez]

Hey I just bought GRAW this morning through Steam and, like many others, had the problem with cross-com not working AT ALL.
I scoured this forum, saw many numerous complaints, and finally found my fix in THIS THREAD, specifically in post #33, to wit:

edit "ctrl_set_def.xml" in your "..\Ghost Recon Advanced Warfighter\Settings" folder.

there's a line in there that reads:
<button id="hud_select" binding="2" device="mouse" group="misc"/>
change it to read:
<button id="hud_select" binding="2" device="mouse" group="tactics"/>
and your done.

found it in:
http://forums.filefront.com/gr-aw-pr...m-problem.html

hope this helps

Okay so that fixed it for me, but I have a couple of gripes here:

1) Apparently both Steam and Ubisoft are aware of this and have chosen to do nothing about it, in spite of it being a relatively simple fix. Granted, there are other fixes that worked for other people, and apparently this one hasn't worked for everyone, but at least it's something.

2) Not only has it not been fixed by Ubisoft, but Steam apparently can't even be bothered to put a frickin' sticky in this forum to the fix. I guess that's too much trouble for the mods or someone from Valve? I mean, there's a sticky for Invalid CD Key errors, so why not a sticky for this DEBILITATING GAME KILLER BUG?
(And other forums here have many stickies for various issues)

3) That Steam can continue to sell this game in spite of the MANY reports of this IMPORTANT game feature not working, combined with their lack of interest in sticky-ing potential USER-discovered fixes is, to me, reprehensible.

You can find pasted support responses from both Steam and Ubisoft in threads here about this issue, so it's not like Steam isn't aware of it, and yet they can't be bothered to make a simple sticky. It's not like it's new either - they've had two years to get around to posting it, and here I am, doing it on my first day with the game.
I guess Steam just doesn't give a f... Is that what it is?

If anyone from valve bothers to read this, I expect to see a sticky here soon or a good explanation why there isn't one or won't be one. My faith in Steam has dropped several points in the past few hours. Your lack of concern is shameful and reprehensible.

And to the guy in that thread who said Steam isn't responsible for fixes, yes, that's right. But they ARE responsible for selling games that work, as I see it.
And even if they aren't, there's this thing called having pride in yourself and knowing you are offering something of quality.
Maybe that doesn't matter to Steam anymore. Hopefully they'll prove that suggestion wrong.

And in case you haven't caught the drift of this, it's not just about me either. I have it fixed now, but the only reason I'm wasting this time here is because this really "jareted" me off. I could have found the fix a whole lot quicker if there had been a sticky... but I have to wonder how many other people just gave up, or wasted far more time finding a fix.
And it's not just about a simple sticky either - it's a matter of showing your customers that you do in fact give a s**t about us.

Edit:
I also made a post in the Steam discussion forum, linking back to this one:
HERE... which got locked really quickly. I'm amazed how quickly it got locked. So someone's on the ball at least. Obviously it must be a much higher priority to silence the squeaky wheel with a lock than to grease it with some help.
(I'm amazed this thread didn't get locked at the same time.)

If anyone even cares about all this, that is. For all I know I may be the only one playing this game.
.
.

[A Noobcake]

Ubisoft made the game, so it's their responsiblity to fix it.

[FreemanForPrez]

Originally Posted by A Noobcake

Ubisoft made the game, so it's their responsiblity to fix it.

Perhaps you should re-read the part where I wrote:

And to the guy in that thread who said Steam isn't responsible for fixes, yes, that's right. But they ARE responsible for selling games that work, as I see it.

Especially notice the part in it where I said "yes, that's right".

In other words, I agree that Ubisoft is responsible for fixing it.

You see, this isn't really about Steam or Ubisoft's responsibility to fix it.
This is about Steam knowing there's an issue and not bothering to address it with a simple mention of where to find more info. A sticky, in other words, like they do for many other games.

What Steam has done is to continue selling a broken game - a game with a major debilitating, game-killing bug that seems to affect almost everybody, even though they *know* there's an issue and even though they know Ubisoft won't fix it.
Maybe there's something wrong with my thinking, but to me that is not okay.
And what makes it worse is that whoever mods around here couldn't take the time to notice the threads about it and post a simple sticky note for potential fixes. They do that elsewhere on this site, why not here? Lack of concern is the simple answer (and it's probably the correct answer), and when you're a retailer, lack of concern for your customers isn't a particularly good trait to have.

[FreemanForPrez]

And on the off chance that somebody from Valve, or the forum mod does actually bother to read this and endeavor to do something about it, I should mention another major huge mongo game-killing bug and post the fix for it:

Mission...whatever... called "ready for bear" WILL wig out on you in the Steam PC version of GRAW 1.
What you have to do is go to the patch.bundle file > \Steam\steamapps\common\ghost recon advanced warfighter\Bundles\patch.bundle and rename it to Xpatch.bundle by right clicking on it and selecting rename.

If you had to do the cross com fix of renaming "interface" to "tactics" (as mentioned in my first post), you will probably have to change that back to "interface". My cross com stopped working again after changing the name of patch.bundle, so on a whim I tried renaming "tactics" back to "interface" and it magically started working again.

There doesn't appear to be any need to change Xpatch.bundle back to patch.bundle after the "ready for bear" mission, and I played it all the way through without any more problems afterwards. It might be a good idea to simply rename it before even starting a new game, but I haven't tried that. Knowing this game and all its weirdness, who knows what that might break.