Greetings! I'm not normally one to complain, but I've been unable to find a remedy to this problem after repeated attempts. So, I figured I'd create the topic here, to see if anyone else has a solution and to signal boost it for those searching from Google.
I'm currently running Spiral Knights with a Sapphire Radeon HD 6850 using the latest Catalyst drivers (11.7) in Windows 7. My experience with this has been terrible to say the least: I'm only able to run the game consistently at the lowest graphical settings, and large content areas such as the Ironclaw Munitions Factory and Firestorm Citadel drop my framerates down to the point I'm unable to actively participate in battle. Literally, my rates are so low that repeated attacks all fold into a single charge attack, if they register at all.
I've tried various other driver versions, including those recommended by the wiki (http://wiki.spiralknights.com/Performance_issues_FAQ#ATI.2FAMD_Radeon_Vi...), to no avail. Given this card is very highly received on PassMark (http://www.videocardbenchmark.net/gpu.php?gpu=Radeon+HD+6850) and comes with 1GB of onboard memory and a fairly speedy processor, I'd hoped it sufficient to play this game. This is supported by having no problems with other graphically-intensive games, as verified during a gaming binge fueled by the Steam Summer Camp sale. Out of the full gamut of 30+ games I played in this compressed time period, Spiral Knights was the only one with significant performance issues, with performance decaying rapidly proportional to the number of models on the screen at one time.
I've attempted tuning the card in AMD's VISION Engine Control Center to max out its performance, also to no avail.
Has anyone experienced similar problems with this card that they care to share? I'm pretty sure it's simply underperformant OpenGL issues related to poor support by the Catalyst drivers and an optimistic culling strategy on the part of Three Rings' engine developers, but it helps to be thorough. Regardless, it helps to have this data on hand, so the folks at Three Rings can fix the problem... or provide guidance to do so.
What kind of data? Its been a known problem since Cat 11.2, and its been all downhill since.