test content
What is the Arc Client?
Install Arc

MAXFPS command line no longer working. Temps raising because of it.

SystemSystem Member, NoReporting Posts: 178,019 Arc User
I don't know what has happened, but all of a sudden the game is not using the -maxfps commandline option anymore. This is causing my machine to render over 100fps and raise my temps very rapidly and very near a dangerous level. The same is happening to every one of my family members. (I live in Hawaii...it is really hot here to begin with.)

If this command line option was disabled on purpose PLEASE bring it back. If this was a mistake, PLEASE fix it soon. Right not one of our machines is shutting down due to temps the others get dangerously close to shutdown temps. This command line option set to something reasonable like 35-45FPS was the only thing keeping our machines away from redline. Please get this sorted out. Thanks.
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    I never had to use the maxfps command but there is another way to limit the frame rate.

    Options > Video > Advanced > Troubleshoot. Last one in that list.

    I'm not sure if it's the same as the maxfps command but I figured I'd post anyway.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    I emailed the guy that added it, but he is out for gamefest right now so I probably won't hear back until Monday.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Dragon-RD wrote: »
    I never had to use the maxfps command but there is another way to limit the frame rate.

    Options > Video > Advanced > Troubleshoot. Last one in that list.

    I'm not sure if it's the same as the maxfps command but I figured I'd post anyway.

    It looks like both the maxfps and PerFrameSleep (10ms delay between frames) commands were moved to the Troubleshooting tab with today’s patch.

    It also appears that the command line options were affected too, so if you need either one enabled, you will need to do so from the Troubleshooting tab.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    You can set your max FPS in the Video Options screen. It is way down at the bottom of the advanced settings, under "Troubleshooting". You need to click the Advanced checkbox, and then click the Troubleshooting category to get the options. This is also where Software Cursor is hidden.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    No wonder my card went nuts again yesterday.

    @Coderanger: These changes really MUST end up in the patchnotes too. Could you please check in on your teams routines for how you add notes to the summary of the patchnotes?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    All the people using the MaxFPS command, Why?

    Just grab this little program and when set-up will auto limit your frames in STO.

    FPS Limiter
    http://www.caveofdistraction.com/2009/07/22/fps-limiter-smoother-gameplay-in-arma2-and-other-titles/

    Scroll down a bit. Couldn't find a better download link.


    Hope this helps.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Loxanna wrote:
    All the people using the MaxFPS command, Why?

    Just grab this little program and when set-up will auto limit your frames in STO.

    FPS Limiter
    http://www.caveofdistraction.com/2009/07/22/fps-limiter-smoother-gameplay-in-arma2-and-other-titles/

    Scroll down a bit. Couldn't find a better download link.


    Hope this helps.
    simply because nobody but you knew this utility existed and Cryptic have built this ability into their software so theres no need to install a third party tool to do the same thing. unless you like installing tools to play with

    just a note on the /maxfps setting. it appears the advanced command line from the launcher - options still works use '-maxfps' not '/maxfps' but you can change this setting ingame under troubleshooting now
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    or try vsync ;) limits it also @ refreshrate of your screen.

    I can't live without vsync because of the tearing, so 60fps is more than enough for me
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    d33f wrote: »
    or try vsync ;) limits it also @ refreshrate of your screen.

    I can't live without vsync because of the tearing, so 60fps is more than enough for me

    same here :)
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    I also started having heat issues again since the 11th, will try out one of these. Has anyone used both?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    OK, I simply do not understand this. If running your videocard full blast is causing it to overheat then you have a cooling problem that needs to be fixed. Properly cooled hardware should *never* overheat. Ever.

    Sometimes it's a fan/driver issue in that the auto fan function doesn't work and the fan doesn't speed up like it's supposed to. In this case you need something like RivaTuner or nTune to manually force 100% fan speed.

    If your vid card's fan is already running at 100% and you're still overheating then you have a physical cooling problem. Your case fans are clogged up, blocked, or otherwise obstructed. Open the case and clean out all the fans (including the GPU and CPU) to restore proper airflow. Make sure you haven't put an add-in card directly next to the video card as this can reduce airflow and cause overheating. Make sure all the case fans are blowing in the right direction (front fans blow in while rear fans blow out).

    Limiting the frame rate of the game may relieve the problem, but it certainly won't fix it. If you have a cooling problem it's going to take it's toll on the entire system so it's best to get to the root of the problem instead of just slapping a band aid on it.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    What do you not understand? Of course you can run a fan at 100% 24/7 and have it hang out at 40 degrees no matter what you do.

    When from 10th to the 11h the fan has to run MUCH higher to keep the same temp... Or if you keep the fan speed at the same level and the average GPU temp is 30 degrees higher from one day to the next there is clearly an issue.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Ryum wrote: »
    What do you not understand? Of course you can run a fan at 100% 24/7 and have it hang out at 40 degrees no matter what you do.

    When from 10th to the 11h the fan has to run MUCH higher to keep the same temp... Or if you keep the fan speed at the same level and the average GPU temp is 30 degrees higher from one day to the next there is clearly an issue.

    First off, the OP is saying he's got machines shutting down due to overheating. This clearly is not normal and indicates something is wrong with these systems, not the game.

    And honestly, I really don't understand your point. Auto fan control is there for a reason. If the card is working harder its temperature is going to rise. And the fan will speed up in response to this. This is how it's supposed to work. This is not a problem, this is by design. You don't hurt the card by running it at 100% so long as the fan is keeping it cool.

    It sounds like you want to impose some sort of limiter on the game so it won't run at full speed so that the card doesn't heat up, which in turn causes the fan to spin faster. And if that's the case I'm really lost. This would be like putting a speed limiter on your car so that the engine doesn't get hot enough to trip the thermostat. Why would you want to do this? What's the point of having a high-end video card if you're not going to let it flex its muscle?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    CaptainFabulous is correct no video card should be over heating to the stage where the computer shuts down.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Then you don't get it, I am not shocked, and no I have never had my PC shut down due to heat issues.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    OK, So I can confirm what someone elsewhere mentioned. If you set these options under the "Troubleshooting" tab the setting resets when you leave/exit the game. Upon logging back in the setting is set back to 120FPS. The other "button" based settings still work, but the FPS resets itself. I need it at 30 or 60 to not heat up. (Prefer 30...just to be safe.)
    coderanger wrote:
    I emailed the guy that added it, but he is out for gamefest right now so I probably won't hear back until Monday.

    Thanks Ranger. Much appreciation.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Why are people so fast to blame the machines.

    If the game is allowed to force your machine to render 120FPS then it will and THAT will start roasting your machine. A liquid cooled machine that runs Crysis maxed at 60-80FPS and is somewhere around 60c WILL overheat if it is forced to render that same game at 120FPS, from the engine, at any length of time. You doubt this? Let me know.

    They run this game and never overheat as long as they are not rendering 120FPS. THAT is the issue here. In other games they do not overheat. Ever. JUST THIS GAME and ONLY when the game engine is set to run at the 120FPS. (IE without the maxFPS commandline setting. If your machine CANNOT push the 120FPS then you will never overheat your machine trying to push that many frames because your machine CANNOT render that many frames. The game acts like there is no limit to how hard it can push your card so it does. With an FPS limit (from the commandline codes in the launcher) this never happens. Simple.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Okay, the command line arg has been sorted, but you are still better off setting it in your prefs anyway.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Why are people so fast to blame the machines.

    If the game is allowed to force your machine to render 120FPS then it will and THAT will start roasting your machine. A liquid cooled machine that runs Crysis maxed at 60-80FPS and is somewhere around 60c WILL overheat if it is forced to render that same game at 120FPS, from the engine, at any length of time. You doubt this? Let me know.

    They run this game and never overheat as long as they are not rendering 120FPS. THAT is the issue here. In other games they do not overheat. Ever. JUST THIS GAME and ONLY when the game engine is set to run at the 120FPS. (IE without the maxFPS commandline setting. If your machine CANNOT push the 120FPS then you will never overheat your machine trying to push that many frames because your machine CANNOT render that many frames. The game acts like there is no limit to how hard it can push your card so it does. With an FPS limit (from the commandline codes in the launcher) this never happens. Simple.

    See, this is wrong. Your machine should NEVER overheat. Whether you're running at 120 fps or 500 fps, a properly cooled machine does NOT overheat. If you're overheating there is a problem. Sorry to use the car analogy again, but it's like saying you can't drive over 50 MPH cause the car will overheat. And then thinking that's normal. It's not normal. Cars only overheat when there is a problem, no matter how fast they are going.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Why are people so fast to blame the machines.

    If the game is allowed to force your machine to render 120FPS then it will and THAT will start roasting your machine. A liquid cooled machine that runs Crysis maxed at 60-80FPS and is somewhere around 60c WILL overheat if it is forced to render that same game at 120FPS, from the engine, at any length of time. You doubt this? Let me know.

    They run this game and never overheat as long as they are not rendering 120FPS. THAT is the issue here. In other games they do not overheat. Ever. JUST THIS GAME and ONLY when the game engine is set to run at the 120FPS. (IE without the maxFPS commandline setting. If your machine CANNOT push the 120FPS then you will never overheat your machine trying to push that many frames because your machine CANNOT render that many frames. The game acts like there is no limit to how hard it can push your card so it does. With an FPS limit (from the commandline codes in the launcher) this never happens. Simple.

    WTH are you talking about?

    1) All hardware is DESIGNED to run at 100% at rated clock speeds constantly and consistently.

    2) People 'overclock' thier hardware all the time, and that's the only time you might run into issues that could cause your hardware to fry - No game software can 'overdrive' your hardware, and modify it's clock or timing speeds.

    3) If your hardware overheats ay 100% usage, your setup has a cooling issue - againcards and fans are designed to generally work at 100% rated speeds constantly; but the manufacturer also expects the tech who installs it to understand how to pop something into a case and still ensure proper airflow, etc.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Armsman wrote: »
    WTH are you talking about?

    1) All hardware is DESIGNED to run at 100% at rated clock speeds constantly and consistently.

    No they certainly are not. Infact they have different quoted MTBF figures on utilisation variations. Hell video cards ramp down their clock speed according to load to ensure prolonged life. ATi designed their fans to only run at 100% in the arest of situations as the fan will meet a premature end as opposed to the qouted MTBF figure for a fan running at 30%.
    Armsman wrote: »

    2) People 'overclock' thier hardware all the time, and that's the only time you might run into issues that could cause your hardware to fry - No game software can 'overdrive' your hardware, and modify it's clock or timing speeds.

    You are obviously not aware of the G80 and G82 chipset issues.

    Nor are you aware that ALL 5850 and 5870 video cards belonging to the Rev 1.0 heatsink family are FAULTY by design as they do not make proper contact with the components.
    Armsman wrote: »
    3) If your hardware overheats ay 100% usage, your setup has a cooling issue - againcards and fans are designed to generally work at 100% rated speeds constantly; but the manufacturer also expects the tech who installs it to understand how to pop something into a case and still ensure proper airflow, etc.

    So now they are only "generally" designed to operate at 100% all the time?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    The lack of info from people who seem to claim they know ANYthing about GFX cards is getting scary.

    There needs to me a disclaimer on when opening the PC & Tech issues forum to NOT take advice from other players or risk killing your PC.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    Ryum wrote: »
    The lack of info from people who seem to claim they know ANYthing about GFX cards is getting scary.

    There needs to me a disclaimer on when opening the PC & Tech issues forum to NOT take advice from other players or risk killing your PC.

    Riiight, cause I guess it's easier to ignore people who know more than you rather than admit it and possibly learn something. Whatev. No skin off my nose. If you're dead set on having an improperly-cooled rig far be it for me to stop you.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    smoke1987 wrote: »
    Nor are you aware that ALL 5850 and 5870 video cards belonging to the Rev 1.0 heatsink family are FAULTY by design as they do not make proper contact with the components.

    And of course, it's Cryptic's fault if you purchase faulty hardware and it experiences... faults...
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    See, this is wrong. Your machine should NEVER overheat. Whether you're running at 120 fps or 500 fps, a properly cooled machine does NOT overheat. If you're overheating there is a problem. Sorry to use the car analogy again, but it's like saying you can't drive over 50 MPH cause the car will overheat. And then thinking that's normal. It's not normal. Cars only overheat when there is a problem, no matter how fast they are going.

    OK, saying a graphics card is running at 120 FPS is NOT the same as a car at 50MPH (depending on the resolution it's pushing). Running at higher resolutions, most modern graphics cards "max" around 120 FPS, but that doesn't mean they are designed to run at that level indefinitely. It is expected that MOST of the time, you won't be running a 3D game on your machine that requires 100% of your GPU, but occasionally you will (might). This is why, even if you over clock (or even UNDER clock) an ATI card in the catalyst control center it doesn't run at the set speeds all the time, only when 3D or video intensive apps are running. The rest of the time (2D apps) it throttles the card down to enhance product life (so sayeth the AMD ATI product FAQ).

    Taking your car model into account, cars are EXPECTED to average speeds of about 35MPH, staying between 0 and 75 MPH most of the time, they are designed this way, and can MAX at about 120-150 MPH (on average, unless there is a digital limiter). So saying a graphics card running at FULL BLAST for a couple of hours is NOT the same as a car at 50 MPH, more like running that car at 120MPH for a couple hours… still think it won't over heat... and in Hawaii's weather (the OP is in Hawaii) - think again!

    That being said, no graphics card should overheat to the point of bricking, it should have limiters on it to kill the app or shutdown the card before it gets to that point, just like when a car overheats the radiator cap should "pop" and let out the excess pressure, and you'll have to pull over and wait for the car to cool off... and maybe add some more water/radiator fluid. It should NOT blow the engine if the car is designed properly. Then again, perhaps this IS the problem... if the game has no limit on the FPS (which was the problem) it could, in theory, run your card at it's max for extended periods of time needlessly, thus lowering product life, and possibly causing crashing issues as the card kills the program to keep itself within the temp limits as all good graphics cards should (the card stops processing the game's code, the game, or PC, crashes) or as the product begins to fail due to reaching it's end of life (due to a shortened life span).


    Now, if you're over clocking you card and it overheats, that's all on YOU. If you OC, you best be ready to actively monitor your temps, and quite possibly upgrade your cooling system (esp. on higher end cards).
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited February 2010
    DocDove wrote:
    OK, saying a graphics card is running at 120 FPS is NOT the same as a car at 50MPH (depending on the resolution it's pushing). Running at higher resolutions, most modern graphics cards "max" around 120 FPS, but that doesn't mean they are designed to run at that level indefinitely. It is expected that MOST of the time, you won't be running a 3D game on your machine that requires 100% of your GPU, but occasionally you will (might). This is why, even if you over clock (or even UNDER clock) an ATI card in the catalyst control center it doesn't run at the set speeds all the time, only when 3D or video intensive apps are running. The rest of the time (2D apps) it throttles the card down to enhance product life (so sayeth the AMD ATI product FAQ).

    You're missing the point. If playing a game for a short amount of time is causing your video card to overheat then you have a cooling problem. Period.

    We can debate the merits and/or pitfalls of long term, 100% GPU usage, but suffice to say it's irrelevant to this conversation. And though you might not do 3D gaming for an extended amount of time, you *might* do things like SETI or folding@home, which run for hours and hours at a time, and if set up to use CUDA, will keep your GPU at 100% the whole time.

    And just about every modern CPU and GPU will throttle down when not in use. This serves two purposes; the first is to save power, the second is to "enhance product life", which honestly is kinda BS. You're much more likely to upgrade a part long before it reaches the end of its product life, even if it's been over-stressed (such as overclocking). "Shortening the product life" is really something that no one should be concerned with unless you require your computer to last a decade or more.
    Taking your car model into account, cars are EXPECTED to average speeds of about 35MPH, staying between 0 and 75 MPH most of the time, they are designed this way, and can MAX at about 120-150 MPH (on average, unless there is a digital limiter). So saying a graphics card running at FULL BLAST for a couple of hours is NOT the same as a car at 50 MPH, more like running that car at 120MPH for a couple hours… still think it won't over heat... and in Hawaii's weather (the OP is in Hawaii) - think again!

    Well, that's not what I said, but nice try. Go read it again. You do bring up an interesting point in regard to ambient temperature. I admit this can play a role, but again, it comes down to inadequate cooling. If the ambient temperature is so high that your components are overheating you either need to get better component cooling (water cooling if necessary) or reduce the ambient temperature (as in, get yourself an air conditioner). Either way, it's not the game's fault.
    Then again, perhaps this IS the problem... if the game has no limit on the FPS (which was the problem) it could, in theory, run your card at it's max for extended periods of time needlessly, thus lowering product life, and possibly causing crashing issues as the card kills the program to keep itself within the temp limits as all good graphics cards should (the card stops processing the game's code, the game, or PC, crashes) or as the product begins to fail due to reaching it's end of life (due to a shortened life span).

    Games don't limit your FPS. They will run as fast as the hardware will allow (unless you're using vsync). This is nothing new and I find it kinda idiotic that you and others even think this way. Do you expect a video transcoding application to limit CPU cycles so that your CPU won't run full blast for hours on end? When you defrag your hard drive do you expect the program to stop and let the hard drive rest every few minutes so you don't "shorten its lifespan" by running it full tilt hour after hour? Seriously, this line of thinking is really TRIBBLE.
Sign In or Register to comment.