I want to believe you, I really do.
But you can't tell me SMS didn't known about this issue pre-release. Knowing it existed and bearing in mind what a huge factor it is (it seems the general consensus is, fix the lag, Shift 2 becomes an excellent racing game) why didn't they fix it before launch? Or after it was a known problem in the first iteration of Shift?
The simple (although unpopular) answer is it's not a simple fix. To have a game lauded almost unanimously for a bug and to then produce a sequel to said game with the same bug ubiquitously present is a telling sign.
I pray I'm wrong, but the writing is seemingly on the wall.
I know. That's why I wrote "should". Still, there's any number of games that make it to release with game-breaking bugs, so it's not like Shift 2 would be the first.
The obvious answer is that the game is the way it is because it was too difficult for them to fix in time for release. That's one possibility. Unfortunately, if that's true we're pretty much all boned.
The optimistic answer is that something went wrong with some late change before release, and it was missed in testing. Or someone fatfingered it and pulled the wrong file to put in the release bundle. I don't know.
The facts supporting this is that there's apparently a fix for PC. I say apparently because I haven't got a PC version myself, and I haven't seen any footage of it running cleanly on PC. But the fix supposedly consists of editing one line in a config file to turn off input dampening. ONE LINE.
If that's the case, that's about the easiest fix ever. Console owners can't do it themselves, but a patch to fix a single config line can't be that hard.
I'll admit, it's optimistic. But that's it, I want to like the game. Without the input lag, I think it's seriously good. It has other issues with crashing, graphical glitches and such, but that's stuff that all games have to deal with. If they can get this out of the way, I think they'll have done well.
Unfortunately, once again they've killed their reputation by having a game-breaking bug in the release version though. With Shift 1 it was the bouncing. With this it's input lag. What are we going to get in Shift 3?