Same issue(s) here. When MWLL was first released, I was playing on a P4 3.0 Ghz and an AGP HD3850 512MB with 4 gigs of DDR533. Needless to say, the experience was painful. In a small match, with 2-6 people, it was choppy, but playable (10-25 fps) on Medium. Anything over that, and performance would take a large hit (5-15 fps avg). About three months ago, I upgraded to a Phenom II X2 550BE and an HD5770 1GB with 4 gigs of DDR3-1600. Playing 0.2.0 on this system was a breeze on CCC level 4, 35-50 fps average, unless it was a full 32 player server. I was able to reliably play with Win7 32-bit and Win XP Pro 32-bit on both of these systems.
Now, on that same system, 0.3.0 plays like utter crap. I randomly freeze for 5-10 seconds sometimes, for no reason that I can track (I almost always run with profile 6 active). It always seems to happen when it's the most inconvenient...you know, like when I'm dive bombing. Can't keep track of how many times I've flown straight into the ground because I froze as I dropped my ordinance. I also get the "choppiness" that's been described in detail above. I have noticed when it happens, the "Recent peaks" spams some message about a frame buffer being full. Also, when this is happening, the renderer seems to hover around 60-75% rather than its usual 40-50%. If I can get a screenshot of it, I'll post it. This happens regardless of my detail level. It went from playing beautifully in 0.2.0 to playing like shit in 0.3.0, no other system changes. All of this is in addition to the fact that I CTD all the time for no discernable reason. I've updated my video drivers, switched from my Creative Audigy 2 to my onboard sound, uninstalled/reinstalled the game, tried all levels of the CCC (2.21 and the Warhead 3.00), and basically done everything save for reinstalling my OS (Win7 32-bit). None of it makes a difference.
Granted, we're not all whiz kids here, but I think most of us, being Crysis players, are familiar with the basics of 3D game performance. We know how to manage our system and multimedia drivers, DirectX, MS Visual C++ runtime, etc, and we grasp the concept of lowering settings for performance. To suggest that this issue, which popped up only in 0.3.0, and seemingly affects a good portion of the player base across a wide range of hardware and operating systems, is not due to changes made within the mod, is just silly. I understand that the first rule of tech support is to assume the person you're helping is so retarded that they can't tie their shoelaces by themselves, so I know the devs aren't just sticking their fingers in their ears and going "lalala update your drivers lalala nothing wrong lalala", but any sort of information would be appreciated. If it is the renderer not playing nice with ATi, then so be it, I can accept that answer...but my HD5770 ran 0.2.0 absolutely perfectly. All of these issues are new to, and specific to 0.3.0.
