Dunno if this is ok, since this is pretty much a Crysis 2 forum, but I have a severe big with the first one, it's not very obstructing, but it kills my frames and... Well, you can see for yourself why it is annoying: Stomping Bug

Game is fully patched, 1.21 that is, using an Intel i5 2500K stock, 8GB DDR3 1,333 MHz, P8H67 mobo, GTX 580 with latest drivers and Windows 7 x64 Ultimate.

Hope there is a solution that does not require re-installing the game as it is on an SSD, rather not want to as it'll wear my SSD out.

Can anyone help, is this a common bug or is it indeed very strange?

Very strange indeed. I haven't seen it before but as you've already done the usual patching/driver updates, i'd suggest contacting EA support at http://support.ea.com who may be able to assist. If not then a re-install is going to be your only remaining option.

Not seen that one before,at first it made me laugh quite a bit but im sure its damn annoying and ruins your gameplay after a while.

Is this vanilla or modded install in any way?

Made me laugh as well at first, when I first discovered the issue, I was sneaking in cloak mode near the Koreans, thinking: "Oh come on, how am I supposed to sneak up on them if I sneak like an Elephant?!?"

Must be the mod that I installed that ruined it, but since the mod did not work properly (It was a mod that was supposed to give higher resolution foilage, but instead it screwed up the Streaming Textures.), I removed it entirely, could be the cause of it. Could this possibly give anyone of you an idea how to fix it if there is way around re-installation?

Been a while, but finally could be bothered to reinstall it, in fact, my whole OS needed to so even that is fresh, only thing that remained were the config files and the savegames...

... And, well... The bug persists... Is there a chance it is something in the savegame or the config files that is causing this?

Meanwhile I'm just gonna play through and see if the bug still persists on the next map, maybe it won't, I hope at least.

Edit: Problem was indeed solved by going to the next map, weird...