04-27-2015, 07:19 AM
I just fired up TF2.
Framerate couldn't even stay above 60.
I was like wtf is worng with my machine, I remember running this game at stable 132 (the optimum for the source engine, and yes, the engine bases calculations on the framerate >_<).
Started troubleshooting my machine, set windows to maximum performance mode no eye candy.
Remembered I had just shrunk my windows boot partition from my ssd to a really small size and decided to remove the partition I had made for linux and extend the partition back.
Checked pagefile, hiberfile and all that ssd junk.
Checked CPU & GPU clockspeeds.
rebooted a couple of times.
Still couldn't get over 60 with chris' maxframes cfg running in DirectX 8 mode.
I was confuzzled; I had properly broken something.
Then it hit me: I had been messing around with PCI passthroughing my GPU in my Fedora install and my screen was still plugged into my motherboard, meaning I had run the game on my Intel HD graphics 2000 all this time. DERP.
Framerate couldn't even stay above 60.
I was like wtf is worng with my machine, I remember running this game at stable 132 (the optimum for the source engine, and yes, the engine bases calculations on the framerate >_<).
Started troubleshooting my machine, set windows to maximum performance mode no eye candy.
Remembered I had just shrunk my windows boot partition from my ssd to a really small size and decided to remove the partition I had made for linux and extend the partition back.
Checked pagefile, hiberfile and all that ssd junk.
Checked CPU & GPU clockspeeds.
rebooted a couple of times.
Still couldn't get over 60 with chris' maxframes cfg running in DirectX 8 mode.
I was confuzzled; I had properly broken something.
Then it hit me: I had been messing around with PCI passthroughing my GPU in my Fedora install and my screen was still plugged into my motherboard, meaning I had run the game on my Intel HD graphics 2000 all this time. DERP.
