Author Topic: Extremely low frame rate on 2012 computer and gaming graphics card  (Read 1102 times)

0 Members and 1 Guest are viewing this topic.

Extremely low frame rate on 2012 computer and gaming graphics card
When I first started playing yesterday I went through the tutorials and was getting ~100 fps using the default launch options. Now I get between 4.5 and 7.0 fps. This PC was build from brand new parts in late 2012 except for the graphics card which was added on later.

Specs:
                       Processor: Quad-Core AMD Athlon II 3GHz
                              RAM:  8GB
                        Graphics:  Nvidia GTX 560
     Attempted Resolution:  1920*1080

I've tried installing the patch and turning off shaders, no dice. As of 2014-09-11 Nvidia drivers are up to date.
Debug log is attached.

[attachment kidnapped by pirates]

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Extremely low frame rate on 2012 computer and gaming graphics card
When I first started playing yesterday I went through the tutorials and was getting ~100 fps using the default launch options. Now I get between 4.5 and 7.0 fps.
Hmm... since nothing in particular is jumping out at me from the log, have you tried rebooting? That kind of drastic performance difference with no changes is... unusual.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.