1000FPS in launcher / causing gfx capacitor squealing

Discussion in 'Support!' started by zaphodx, June 8, 2013.

  1. zaphodx

    zaphodx Post Master General

    Messages:
    2,350
    Likes Received:
    2,409
    http://pa.lennardf1989.com/Tracker/inde ... ask_id=342

    Main menu has no FPS limit and exceeding 1000FPS is causing high pitched capacitor squeal on my graphics card. Would be nice to limit the FPS to avoid gfx damage. Currently I'm using v-sync In catalyst control manager to limit FPS to my refresh rate.
    Last edited: June 8, 2013
  2. cola_colin

    cola_colin Moderator Alumni

    Messages:
    12,074
    Likes Received:
    16,221
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    I dont think this can cause damage to the gfx card, but yeah a framelimit of like 60 would be nice for the menu at least.
  3. LennardF1989

    LennardF1989 Uber Contractor

    Messages:
    798
    Likes Received:
    323
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    This is actually one of the first things I said when I started playing PA: The menu NEEDS a FPS limiter.
  4. dacite

    dacite Member

    Messages:
    109
    Likes Received:
    19
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    My motherboard beeper screams at me whenever I open PA. This must be the reason.
  5. crseth

    crseth Member

    Messages:
    66
    Likes Received:
    1
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    Yes this is a big problem that needs to be addressed asap!
  6. infuscoletum

    infuscoletum Active Member

    Messages:
    606
    Likes Received:
    37
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    My GPU clock doesn't go much beyond normally just running my OS, so not much of a problem for me, but ya, 60 fps is more that enough!
  7. subedii

    subedii New Member

    Messages:
    16
    Likes Received:
    5
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    Actually it can. Similar happened in Starcraft 2 once.

    Nice summary of how this works:
    http://www.dailytech.com/Hot+Starcraft+ ... e19224.htm

    Last edited: June 8, 2013
  8. cola_colin

    cola_colin Moderator Alumni

    Messages:
    12,074
    Likes Received:
    16,221
    I was referring to the capacitor squealing. That's just annoying.
    Also imho it is still the fault of the gfx card when it breaks due to a bad cooling under a longer time of 100% load, but yeah it might be a good idea not to test how many ppl in the PA community have a proper cooler.
  9. AusSkiller

    AusSkiller Member

    Messages:
    218
    Likes Received:
    0
    This. It's always bothered me that people blame software for these kinds of hardware issues :(.
  10. Daddie

    Daddie Member

    Messages:
    275
    Likes Received:
    21
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    Actualy it can. Starcraft 2 had the same problem initial which resulted in some people blowing up their gfx card.
  11. subedii

    subedii New Member

    Messages:
    16
    Likes Received:
    5
    Combination of both. If you get a fail there's pretty likely a cooling issue going on to begin with, but the software doing the equivalent of revving your engine in first gear certainly doesn't help matters.
  12. infuscoletum

    infuscoletum Active Member

    Messages:
    606
    Likes Received:
    37
    would setting up vsync thru the nvidia control panel (and/or whatever ati's is) solve this?

    EDIT: I know it would only be a temp workaround, not a real fix.
  13. uruku

    uruku New Member

    Messages:
    5
    Likes Received:
    0
    Re: 1000FPS in launcher / causing gfx capcitor squealing

    If you set you're overclock settings are too high yeah, if you're not using aftermarket cooling systems, then you shouldn't overclock your GPU, altho it should shutdown before it breaks anyways.
  14. infuscoletum

    infuscoletum Active Member

    Messages:
    606
    Likes Received:
    37
    Not always. Burned out half a cpu one time because too much dust, and too much encoding. My comp didn't shut down, and still worked for a while, somehow. When it finally did kick it, the tech actually found scorch marks on the back of the mobo :shock: and every mobo he put the chip in after would fry as well :(

    So ya. Doesn't always happen the way it should.

Share This Page