Nvidia GTS240 Help.

[IceFire]

Oh ok ... so if it's around 9600 performance (and I had one of those) then the settings are way to high. Anything to do with Anti-Aliasing should be turned down to minimal levels.

[AdMan]

now that I think about it I ran those settings before I had the 9800 with a 8500gt but if a 240=8600 you definitely want the AA at about 8x

and TURN OFF VSYNC, although it's only supposed to limit fps to the refresh rate it's been known to be a little screwy and you'll often see an immediate 20+ fps jump as soon as you turn it off, you can make sure it's off by watching the fps during title screens (where no 3d scenes are being rendered) the fps can reach into the hundreds and thousands, with vsync on it will stay at 60

[KG26_Alpha]

Originally Posted by AdMan

now that I think about it I ran those settings before I had the 9800 with a 8500gt but if a 240=8600 you definitely want the AA at about 8x

and TURN OFF VSYNC, although it's only supposed to limit fps to the refresh rate it's been known to be a little screwy and you'll often see an immediate 20+ fps jump as soon as you turn it off, you can make sure it's off by watching the fps during title screens (where no 3d scenes are being rendered) the fps can reach into the hundreds and thousands, with vsync on it will stay at 60

This may help clarify what vsync does and doesn't do.

http://www.tweakguides.com/Graphics_9.html

Tearing

It is an unfortunate fact of computer graphics that if you disable VSync, your graphics card and monitor will go out of synch. Whenever your FPS exceeds the refresh rate (e.g. 120 FPS on a 60Hz screen), or in general at any point during which your graphics card is working faster than your monitor, the graphics card produces more frames in the frame buffer than the monitor can actually display at any one time, so the end result is that when the monitor goes to get a new frame from the primary buffer of the graphics card during VBI, the frame may be made up of two or more different frames overlapping each other. This results in the onscreen image appearing to be slightly out of alignment or 'torn' in parts whenever there is any movement - and thus it is referred to as Tearing.

[AdMan]

Originally Posted by KG26_Alpha

This may help clarify what vsync does and doesn't do.

http://www.tweakguides.com/Graphics_9.html

Tearing

It is an unfortunate fact of computer graphics that if you disable VSync, your graphics card and monitor will go out of synch. Whenever your FPS exceeds the refresh rate (e.g. 120 FPS on a 60Hz screen), or in general at any point during which your graphics card is working faster than your monitor, the graphics card produces more frames in the frame buffer than the monitor can actually display at any one time, so the end result is that when the monitor goes to get a new frame from the primary buffer of the graphics card during VBI, the frame may be made up of two or more different frames overlapping each other. This results in the onscreen image appearing to be slightly out of alignment or 'torn' in parts whenever there is any movement - and thus it is referred to as Tearing.

why are you telling me? I know exactly what vsync does and many times it fucks up your fps, if your having fps issues the very FIRST thing you should do is turn off Vsync

[KG26_Alpha]

Well obviously you don't understand.

Reading the link I provided should help, try again.

Turning off vsync will not let you see more FPS

It allows the graphic card to run higher FPS but you monitors refresh rate will all ways limit what you see with Vsync on or off, with it on it keeps it synchronised to stop tearing.

You might see 250fps displayed in Fraps of other fps counter on a 75Hz monitor with Vsync off but the reality is the refresh rate cant display 250fps only 75.

If there's an issue with Graphics card FPS, turning Vsync off isn't going to fix anything.

And please mind your language, I hate swearing.

[Flanker35M]

S!

I always run VSync ON, that "tearing" drives me nuts. Sure I could get my gfx card to show 290fps on screen, but what's the point? If I get a steady 60FPS I am happy Thanks for the link Alpha.

[AdMan]

Originally Posted by KG26_Alpha

Well obviously you don't understand.

Reading the link I provided should help, try again.

Turning off vsync will not let you see more FPS

It allows the graphic card to run higher FPS but you monitors refresh rate will all ways limit what you see with Vsync on or off, with it on it keeps it synchronised to stop tearing.

You might see 250fps displayed in Fraps of other fps counter on a 75Hz monitor with Vsync off but the reality is the refresh rate cant display 250fps only 75.

If there's an issue with Graphics card FPS, turning Vsync off isn't going to fix anything.

And please mind your language, I hate swearing.

You're truly clueless

http://it.anandtech.com/showdoc.aspx?i=3591&p=2

The most common approach to combat tearing is to wait to swap buffers until the monitor is ready for another image. The monitor is ready after it has fully drawn what was sent to it and the next vertical refresh cycle is about to start. Synchronizing buffer swaps with the Vertical refresh is called vsync.

While enabling vsync does fix tearing, it also sets the internal framerate of the game to, at most, the refresh rate of the monitor (typically 60Hz for most LCD panels). This can hurt performance even if the game doesn't run at 60 frames per second as there will still be artificial delays added to effect synchronization. Performance can be cut nearly in half cases where every frame takes just a little longer than 16.67 ms (1/60th of a second). In such a case, frame rate would drop to 30 FPS despite the fact that the game should run at just under 60 FPS. The elimination of tearing and consistency of framerate, however, do contribute to an added smoothness that double buffering without vsync just can't deliver.

Input lag also becomes more of an issue with vsync enabled. This is because the artificial delay introduced increases the difference between when something actually happened (when the frame was drawn) and when it gets displayed on screen. Input lag always exists (it is impossible to instantaneously draw what is currently happening to the screen), but the trick is to minimize it.

http://www.hardforum.com/showthread.php?t=928593

VSync solves this problem by creating a rule that says the back buffer can't copy to the frame buffer until right after the monitor refreshes. With a framerate higher than the refresh rate, this is fine. The back buffer is filled with a frame, the system waits, and after the refresh, the back buffer is copied to the frame buffer and a new frame is drawn in the back buffer, effectively capping your framerate at the refresh rate.

That's all well and good, but now let's look at a different example. Let's say you're playing the sequel to your favorite game, which has better graphics. You're at 75Hz refresh rate still, but now you're only getting 50FPS, 33% slower than the refresh rate. That means every time the monitor updates the screen, the video card draws 2/3 of the next frame. So lets track how this works. The monitor just refreshed, and frame 1 is copied into the frame buffer. 2/3 of frame 2 gets drawn in the back buffer, and the monitor refreshes again. It grabs frame 1 from the frame buffer for the first time. Now the video card finishes the last third of frame 2, but it has to wait, because it can't update until right after a refresh. The monitor refreshes, grabbing frame 1 the second time, and frame 2 is put in the frame buffer. The video card draws 2/3 of frame 3 in the back buffer, and a refresh happens, grabbing frame 2 for the first time. The last third of frame 3 is draw, and again we must wait for the refresh, and when it happens, frame 2 is grabbed for the second time, and frame 3 is copied in. We went through 4 refresh cycles but only 2 frames were drawn. At a refresh rate of 75Hz, that means we'll see 37.5FPS. That's noticeably less than 50FPS which the video card is capable of. This happens because the video card is forced to waste time after finishing a frame in the back buffer as it can't copy it out and it has nowhere else to draw frames.

Essentially this means that with double-buffered VSync, the framerate can only be equal to a discrete set of values equal to Refresh / N where N is some positive integer. That means if you're talking about 60Hz refresh rate, the only framerates you can get are 60, 30, 20, 15, 12, 10, etc etc. You can see the big gap between 60 and 30 there. Any framerate between 60 and 30 your video card would normally put out would get dropped to 30.

Now maybe you can see why people loathe it. Let's go back to the original example. You're playing your favorite game at 75Hz refresh and 100FPS. You turn VSync on, and the game limits you to 75FPS. No problem, right? Fixed the tearing issue, it looks better. You get to an area that's particularly graphically intensive, an area that would drop your FPS down to about 60 without VSync. Now your card cannot do the 75FPS it was doing before, and since VSync is on, it has to do the next highest one on the list, which is 37.5FPS. So now your game which was running at 75FPS just halved it's framerate to 37.5 instantly. Whether or not you find 37.5FPS smooth doesn't change the fact that the framerate just cut in half suddenly, which you would notice. This is what people hate about it.

http://www.xtremesystems.org/forums/...ad.php?t=96785

http://getsatisfaction.com/futuremar...ring_kills_fps

and finally from the link YOU provided:

There is however a more fundamental problem with enabling VSync, and that is it can significantly reduce your overall framerate, often dropping your FPS to exactly 50% of the refresh rate. This is a difficult concept to explain, but it just has to do with timing. As we know, when VSync is enabled, your graphics card pretty much becomes a slave to your monitor. If at any time your FPS falls just below your refresh rate, each frame starts taking your graphics card longer to draw than the time it takes for your monitor to refresh itself. So every 2nd refresh, your graphics card just misses completing a new whole frame in time. This means that both its primary and secondary frame buffers are filled, it has nowhere to put any new information, so it has to sit idle and wait for the next refresh to come around before it can unload its recently completed frame, and start work on a new one in the newly cleared secondary buffer. This results in exactly half the framerate of the refresh rate whenever your FPS falls below the refresh rate.

As long as your graphics card can always render a frame faster than your monitor can refresh itself, enabling VSync will not reduce your average framerate. All that will happen is that your FPS will be capped to a maximum equivalent to the refresh rate. But since most recent monitors refresh at 60Hz, and in most recent games it is difficult to achieve 60FPS consistently at your desired resolution and settings, enabling VSync usually ends up reducing your FPS. Fortunately, because this problem is pretty much caused by the frame buffers becoming filled up, there is a solution and that's to enable a third frame buffer to allow more headroom. However this is not a straightforward solution, and to read more about this see the Triple Buffering section.

So Which is Best, VSync On or Off?

VSync poses a real dilemma for many people: with VSync off, tearing can occur whenever your graphics card and monitor go out of sync, and this can be very annoying for some people, especially in fast motion games. However with VSync on, your FPS can often fall by up to 50%. This can be resolved on many systems using Triple Buffering, but that also brings potential problems with it. So which choice is right for you?...

...In general, I recommend starting off with VSync disabled in any game as this is the most trouble-free method of gaining the fastest possible performance. This is the simplest solution, and on monitors which have lower refresh rates, or for games in which your framerate is not very high, this appears to be the best solution. You may notice some tearing, but this will generally be minimal if your FPS remains below your refresh rate anyway. Remember though that even if your FPS matches your refresh rate exactly, or is even below it, whenever VSync is disabled the graphics card and monitor are not strictly in sync, and tearing (however minor) can occur at any time.

vsync comes in handy when you have a game that your card has no problem of chewing through and would hence pin at 60/75 with vsync on to minimize tearing and perhaps a few headaches, otherwise it can hurt performance, if you read bobsqueeks original post he's only pulling about 40fps max and sometimes as low as 11, get it?

now run along

[KG26_Alpha]

Thanks for the links

None of which is any different from the link I first posted.

You obviously took offence at the post I made quoting you, it was a reference post and you shouldn't take it as a personal attack.

I know his frame rates are low he needs a decent graphics card.


But I do see an error in what I said regarding capped frame rates to refresh rates, what I also forgot to mention was the monitors resolution can also come into effect regarding poor frame rates.


If you wish to discuss this further please take it to PM as I don't want to waste the bandwidth in this thread.


Edit:


Strangely enough I just ran IL2 with Vsync off and my highest FPS is still capped at 60fps max the same as my monitor.

[AdMan]

maybe if you disable triple buffering, enabling triple buffering shouldn't automatically enable vsync but since the two are used in conjunction there may be some connection.

also it's best to disable/enable it in-game vs control panel. last post in this thread unless more help is needed.

[Necrobaron]

Can't help but good to see you around Bobs...
________
Lovely Wendie99