|
Motherboard: ASUS
CPU: AMD Phenom II X4 955 AM3
GPU: XFX ATI Radeon HD 5870
RAM: 2x2GB DDR3 OCZ Platinum
HDD: 250 GB main / 1.5 TB secondary, game installed on secondary
PSU: Thermaltake 700W
OS: Windows 7 Pro(64 bit)
Hey there mates.
I've noticed, and this only happens with SC2, that no matter what I change in my graphics settings, my framerate always maxes at 30 fps.
I have no idea why it plateaus like that, I've tried changing all the settings multiple times, this happens in fullscreen and in windowed fullscreen(my current setting)
Any ideas on how to fix this so I can get a higher framerate?
|
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game. Change them to what you want the max to be.
If thats not it, delete the Variables.txt and reset your vid settings.
|
On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings.
Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher.
You can however change the second variable.
|
On June 28 2011 04:49 TadH wrote:Show nested quote +On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings. Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher. You can however change the second variable.
I'm pretty sure they fixed that after the patch and adding that line was a temporary fix since the line is still not in my variables.txt and im fine. Then again, I was allso fine before the patch.
|
On June 28 2011 04:49 TadH wrote:Show nested quote +On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings. Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher. You can however change the second variable. not true. Not only that, but you could CHANGE the value to something like 70 and things would still be fine, it's just rather pointless.
The biggest problem would be to remove the frameratecapglue line completely...but even that should not overheat a video card. It was a mistake in PR (or tech support or whatever you want to call it) when Blizzard mentioned that supposed problem.
Anyway, that said... that (Frameratecapglue, Frameratecap) is most likely what's causing your framerate cap.
However, it's also possible that you're running Vsync on, and monitor is displaying at 60 Hz, but in 3D mode (assuming it has one), where it is cutting the video split in half by sending a different image every other screen refresh. Personally I think it's a bad idea to run with Vsync anyways (when there's an optional to manually set the FPS cap, and is used), so I'd recommend that regardless.
Funny story: When I switched my framerate cap from like 30 or 40 (can't remember) to about 60 or 70... my APM seemingly went up by like 25-40%!
|
On June 28 2011 04:55 Xapti wrote:Show nested quote +On June 28 2011 04:49 TadH wrote:On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings. Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher. You can however change the second variable. not true. Not only that, but you could CHANGE the value to something like 70 and things would still be fine, it's just rather pointless. The biggest problem would be to remove the frameratecapglue line completely...but even that should not overheat a video card. It was a mistake in PR (or tech support or whatever you want to call it) when Blizzard mentioned that supposed problem.
I have PTSD from the beta when I fried my GPU because of that. If it's fixed, then great change it to whatever you want.
|
On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game. Change them to what you want the max to be.
If thats not it, delete the Variables.txt and reset your vid settings.
Thanks for the fix! This sounds like it's probably exactly what's limiting. Once I try it out I'll post whether it fixed or not.
|
On June 28 2011 04:59 TadH wrote:Show nested quote +On June 28 2011 04:55 Xapti wrote:On June 28 2011 04:49 TadH wrote:On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings. Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher. You can however change the second variable. not true. Not only that, but you could CHANGE the value to something like 70 and things would still be fine, it's just rather pointless. The biggest problem would be to remove the frameratecapglue line completely...but even that should not overheat a video card. It was a mistake in PR (or tech support or whatever you want to call it) when Blizzard mentioned that supposed problem. I have PTSD from the beta when I fried my GPU because of that. If it's fixed, then great change it to whatever you want. The reason the GPU would have fried is because it was manufactured/designed bad. No video card should be (and generally it's how they make them) able to break/crash by being overloaded.... it would just typically run choppy, or crash. The problem with the video card would mostly likely have been something like incorrect heatsink contact, but it could have been something else.
|
hey dude considering the OP got his question answered can I throw one out there? Will turning V-sync off make my cpu/gpu run hotter, and consequently make my rig louder?
|
On June 28 2011 05:05 Xapti wrote:Show nested quote +On June 28 2011 04:59 TadH wrote:On June 28 2011 04:55 Xapti wrote:On June 28 2011 04:49 TadH wrote:On June 28 2011 04:45 Madoga wrote:
You have to edit your Variables.txt located in My Documents -> Starcraft 2
Frameratecapglue=30
Frameratecap=60
Those are the two fps vallues. first one is for the menu screen second one for in game.
If thats not it, delete the Variables.txt and reset your vid settings. Do NOT change the frame rate cap for the menu, it WILL overheat your card if you set it higher. You can however change the second variable. not true. Not only that, but you could CHANGE the value to something like 70 and things would still be fine, it's just rather pointless. The biggest problem would be to remove the frameratecapglue line completely...but even that should not overheat a video card. It was a mistake in PR (or tech support or whatever you want to call it) when Blizzard mentioned that supposed problem. I have PTSD from the beta when I fried my GPU because of that. If it's fixed, then great change it to whatever you want. The reason the GPU would have fried is because it was manufactured/designed bad. No video card should be (and generally it's how they make them) able to break/crash by being overloaded.... it would just typically run choppy, or crash. The problem with the video card would mostly likely have been something like incorrect heatsink contact, but it could have been something else.
Considering this was a known issue back in the beta, and dozens of people's GPU's suffered the same fate as mine. I'm confident in blaming Blizzard.
|
On June 28 2011 05:07 Geordie wrote:
hey dude considering the OP got his question answered can I throw one out there? Will turning V-sync off make my cpu/gpu run hotter, and consequently make my rig louder?
Yes, for both CPU and GPU, providing that it actually increases your frame rate.
|
Considering this was a known issue back in the beta, and dozens of people's GPU's suffered the same fate as mine. I'm confident in blaming Blizzard.
Then you are being ignorant. Any quality hardware piece is designed to run safely (although hot as hell for cpu/gpu) under full 100% load, otherwise any benchmarking tool would fry your pc just the same way.
The glitch in sc2 beta was resulting in the title screen using 100% of the gpu's power (not more, a programm can't request more), which lead to a heat buildup in your gpu. And while any proper hardware component is designed to have sufficient cooling under full load, user stupidity or ignorance is not taken into account. Any GPU that was fried "because of SC2" was either: shoddily built in someone's cellar / covered in a layer of dust like the fossils of dinosaurs / retardedly overclocked without actual stability testing of the overclock.
True, Blizzard derped by not having a frame limiter on these screens, however this simply brought out an existing problem in someones pc, which was bound to backfire at one point or another.
|
On June 28 2011 07:23 Blindlad wrote:Show nested quote +Considering this was a known issue back in the beta, and dozens of people's GPU's suffered the same fate as mine. I'm confident in blaming Blizzard.
Then you are being ignorant. Any quality hardware piece is designed to run safely (although hot as hell for cpu/gpu) under full 100% load, otherwise any benchmarking tool would fry your pc just the same way. The glitch in sc2 beta was resulting in the title screen using 100% of the gpu's power (not more, a programm can't request more), which lead to a heat buildup in your gpu. And while any proper hardware component is designed to have sufficient cooling under full load, user stupidity or ignorance is not taken into account. Any GPU that was fried "because of SC2" was either: shoddily built in someone's cellar / covered in a layer of dust like the fossils of dinosaurs / retardedly overclocked without actual stability testing of the overclock. True, Blizzard derped by not having a frame limiter on these screens, however this simply brought out an existing problem in someones pc, which was bound to backfire at one point or another.
I'm not going to debate semantics with you. I had a perfectly sound (non overclocked setup). It ran games like CoD MW, LoL etc etc fine. Nothing was overheating, nothing was dusty. The GPU was a 4 month old GTX 460, and Starcraft made it overheat to the point of artifacts, choppy display etc etc. I'm not the only person that it happened to. I'm not "ignorant" as you put it. I simply know there was nothing wrong with the computer and sc2 pretty much fried the gpu.
End of story.
|
On June 28 2011 07:27 TadH wrote:Show nested quote +On June 28 2011 07:23 Blindlad wrote:Considering this was a known issue back in the beta, and dozens of people's GPU's suffered the same fate as mine. I'm confident in blaming Blizzard.
Then you are being ignorant. Any quality hardware piece is designed to run safely (although hot as hell for cpu/gpu) under full 100% load, otherwise any benchmarking tool would fry your pc just the same way. The glitch in sc2 beta was resulting in the title screen using 100% of the gpu's power (not more, a programm can't request more), which lead to a heat buildup in your gpu. And while any proper hardware component is designed to have sufficient cooling under full load, user stupidity or ignorance is not taken into account. Any GPU that was fried "because of SC2" was either: shoddily built in someone's cellar / covered in a layer of dust like the fossils of dinosaurs / retardedly overclocked without actual stability testing of the overclock. True, Blizzard derped by not having a frame limiter on these screens, however this simply brought out an existing problem in someones pc, which was bound to backfire at one point or another. I'm not going to debate semantics with you. I had a perfectly sound (non overclocked setup). It ran games like CoD MW, LoL etc etc fine. Nothing was overheating, nothing was dusty. The GPU was a 4 month old GTX 460, and Starcraft made it overheat to the point of artifacts, choppy display etc etc. I'm not the only person that it happened to. I'm not "ignorant" as you put it. I simply know there was nothing wrong with the computer and sc2 pretty much fried the gpu. End of story.
Sorry, I wasn't trying to be rude, and I know that you weren't the only one affected. I also run SC2 on a 460, and did not have such issues (hovered around 80c).
I'm just trying to specify, that blaming blizzard for this is like blaming the government for you being stuck in traffic due to a snowstorm. True, the government could have taken preparations to effectively clean the road or redirect traffic, but they did not choose for it to snow at 8am.
The thing with current games is that none of them actually have 100% utilisation of hardware resources (unless you're doing something really whacky), and that's why these issues only pop up in synthetic benchmarks that are specifically created to bleed everything out of the hardware.
Let's just say that the SC2 title screen got to be such a benchmark for a bit. 
|
Madoga your fix worked, but it only seems to work in fullscreen and not in windowed fullscreen. Any idea how to make my fps not cap in windowed fullscreen?
|
That is quite peculiar and/or puzzling.
Have you not-yet tried turning v sync off?
Aside from that I couldn't really think of anything, aside from 3rd party software of some kind, but that seems very unlikely (typically one would know about something causing a limitation if it was set up).
I didn't think SC2's FPS display shows the real FPS from cut vsync frames though (aside from it's refresh rate cap), maybe you're using a different program to measure the FPS? Anyway, that's why I originally suggested it could have been 3D mode or something... but if somehow the FPS is actually getting displayed as 30 instead of 60 when at 60Hz, then that could still be the vsync.
|
Oh I forgot to ask you if you were running crossfire/SLI.
Apparently I somehow have just encountered the same problem myself!
I am running crossfire, and think it is related. I exited SC2, then just disabled crossfire, re-enabled, then ran starcraft again.
Now it works good.
It's possible I just needed to restart SC2 (I leave it on for days at a time sometimes).
|
Wow alot of drama in this thread that I wont bother reading. Sounds like your using a TV ! or HDMI its a Vsync issue. Make sure your resolution isn't set to interlaced..
|
Hi this happened to me for a while with my 5830 and 3 monitor setup, no eyefinity. I got fps of about 30 for any game i play. Anyways i figured out what was screwing it up. Set the process to lower priority and limit the affinity of cores used to 2. I didnt check which of these 2 settings did the trick but it worked. Give it a go and tell me what happens.
I figure its cos i have 3 screens and when i use the mouse ingame it leaves the border of the game briefly and thinks i am not in the game anymore and runs as if it were alt tabbed.
|
|
|
|
|
|
EPT
