how to spot a draw() function that gets slower and slower

Started by
3 comments, last by lomateron 10 years, 3 months ago

Hello I am having a problem in my application were the FPS go down as time passes, so to solve this problem I have to know which draw() is the slow one.

I asked before if I could measure the time a draw() takes with graphic diagnostics of VS2012 but the answer is a no, so I want to know if there is another way to spot that slow draw() in my code.

Advertisement

You could comment out the draw calls one by one and see for which one the program keeps slowing down. This will not work if the draw calls are not independent, of course.

“If I understand the standard right it is legal and safe to do this but the resulting value could be anything.”

I already know that is between 10 draws were the problem is, and they depend on each other so I can't do that

Attach a profiler to your program near the start when FPS is good and save it. Then attach one after waiting for the FPS to get really bad and save that separately. Compare the two profiles.

ohhh "profiler", I didnt know that existed, I will try that

This topic is closed to new replies.

Advertisement