I’m not sure if it helps anyone, but I experienced huge framerate drops myself and what I changed seemed to work, but if someone wants to try the same, read below and try at your own risk.
I’m currently running 2 hard-drives in my system, my main one is a 128 GB SSD (Solid State Drive), the other is a Western Digital Green Drive (which only runs at 5400 RPM same as a lot of laptop hard-drives). All my steam apps are installed on the second hard-drive since it has more space. I haven’t had any issues with games in the past such as Portal 2 running on the 5400 RPM, but this one seemed to be running fine until I either interacted with a new resource on the screen or came into a frame where physics objects (barrels), etc were. When turning CL_SHOWFPS 1 on in console, it spiked to red FPS (8-10) when I would move my mouse and walk forward really quick into a new room and same if I did a 360 turn then it would act normal when everything was in view.
Long story short, I ended up moving my D-DRIVE\Steam\steamapps\sourcemods\BMS folder to my SSD at something like C-DRIVE\BMS (stopping/closing steam first obviously)
After doing this, I created a Symbolic link from my D Drive (Wester Digital Green Drive) to my SSD so that I could keep my current steam configuration and try hosting the resources on a more responsive hard-drive. This seemed to work very well, it loads a lot quicker this way anyways and I haven’t experienced the glitches at all anymore and I run on full settings.
Here’s a link talking about NTFS symbolic links: http://en.wikipedia.org/wiki/NTFS_symbolic_link
I ran a command like this:
mklink /D D:\Steam\steamapps\sourcemods\BMS C:\BMS
If you don’t know what a symbolic link is, you need to pretty much have Vista or Windows 7 for this to work. The above command creates a special type of shortcut that allows the one drive to point to the space on another drive (or even just the same drive). As long as they are both NTFS partitions, it should work fine. Steam loads it super well. It’s a handy trick to make games load faster as you’re playing them, then you can jump into command line (cmd) and run a RMDIR command on the D-DRIVE\Steam\steamapps\sourcemods\BMS command and move the C-DRIVE\BMS folder back there.
It’s almost like a tunnel to the information. So, if I click on the “shortcut” in the D-DRIVE\Steam\steamapps\sourcemods folder entitled “BMS” the filesystem thinks that the files in this directory are still on the D-Drive, so it keeps that path when you click on it, but they are really on the C-DRIVE\ in this case.
Does that help anyone? I would venture to guess if someone is running on a slow hard-drive they could be experiencing similar problems which isn’t necessarily Memory/CPU/GPU issues if it’s reading from ~7 GB of information for resources.