Author Topic: vertical sync (Read 4798 times)

vidjogamer · « **on:** March 12, 2011, 09:35:18 am »

I am testing on a number of machines and architectures and my windows 7 machine seems to not limit the frame rate on vsync. Does anyone have any idea why this would be happeneing?

Laurent · « **Reply #1 on:** March 12, 2011, 01:09:22 pm »

In graphics drivers there's usually an option to control it, and it can be set to "force v-sync off". It should be set to "let application choose".

vidjogamer · « **Reply #2 on:** March 12, 2011, 10:07:03 pm »

Yeah, we turned it to always on and still doesnt work. Maybe its a driver issue.

Contadotempo · « **Reply #3 on:** March 13, 2011, 03:08:21 am »

What's the graphics card in question?
I have the exact same problem with an Intel onboard card (Intel Graphics Media Accelerator 950).
It's an IBM Thinkpad R60e laptop if it has any relevance.

vidjogamer · « **Reply #4 on:** March 14, 2011, 02:21:02 am »

Yeah, its a Thinkpad with an integrated intel chip. I dont know the exact models off hand. So you think there is nothing we can do about it?

Contadotempo · « **Reply #5 on:** March 18, 2011, 05:48:18 pm »

I'm not sure.
I tried changing almost every option and eventually ran out of ideas.

I'll try to find another laptop with a similar integrated intel graphics chip and test it to see if it could be a problem with intel drivers.

Gibgezr · « **Reply #6 on:** March 19, 2011, 06:52:36 pm »

An ugly kludge that you can do is to simply only perform the rendering code if a certian amount of time has passed. This won't lock you to the monitor refresh rate, but it will allow you to do multiple calls to your physics loop etc in between calls to the rendering loop, on systems where the physics etc is running quite fast. I have done something simple like that in the past to lockmy framerate down to "no more than 60fps" for example. It's not ideal, but if the main consideration is not wasting time drawing frames that will never be seen, it helps.

Contadotempo · « **Reply #7 on:** March 19, 2011, 10:39:22 pm »

Wouldn't that have the same effect as SetFrameTime(60)?
That's I'm using currently but I'd like to understand where the problem is.

EDIT: Actually, disregard that. I tested it and got a lot smoother movements. Thanks for the tip! Still going to search for another laptop to confirm if it's a driver problem.

Contadotempo · « **Reply #8 on:** April 22, 2011, 07:08:17 pm »

Sorry for bumping this topic.
Just wanted to say that I tested on an old Dell Optiplex GX270 with an Intel onboard graphics chip and the problem persists.

So I guess the problem is caused be Intel's crappy drivers, I think.