• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

Triple buffering: "Why we love it"

Should one use Vsync, Tripple buffering or neither if a game is getting 30-60 FPS though rarely reaches 60?

Vsync will make it 30fps unless it jumps to 60 or goes below 30. Triple buffering will show the 45fps or anything in-between 30-60.

I have not been using D3DOverider lately, I've ran into some games which won't boot with it, but I need to try it with Skyrim.
 
The driver setting is only for OpenGL game. Thankfully Croteam are awesome, if you enable Vsync in the game then triple buffering is switched on, so D3DOverrider isn't needed.

Man, they really did everything right with this release. Except the release date I guess!
 
Honestly, very few games nowadays don't have triple buffering built-in.

Would this work for emulators that use dx as well? Like Dolphin or PCSX2?

Not much point for either, I think. Both emulators have built-in triple buffering, and IIRC, PCSX2 just doesn't run very well at all if you can't maintain full speed (I seem to recall a lot of audio stuttering).
 
Does it work with Crysis 1? In Crysis there is not even a vsync option...

I thought Crysis had an ingame Vsync option?
Just googled and according to THIS, it does:
Vertical Sync: Just a note that VSync is disabled by default in Crysis, and this provides the best performance. However if you wish to enable it, either force it via your graphics card's control panel, or use the r_Vsync console command. Note that if you do enable VSync using either method, I strongly recommend also enabling Triple Buffering using the d3d9_TripleBuffering setting, or if using DX10, via one of the tools in the Triple Buffering link just above.

Update: As of the 1.1 Patch, Crysis now has an in-game VSync option to control Vertical Sync. This controls whether VSync is enabled (ticked) or not (unticked), whether in DX9 or DX10 mode.

For me, d3doverrider worked in Crysis 32bit but NOT in Crysis 64bit.
 
Some slight help. I'm using RadeonPro to make profiles. Should I just let D3DOverrider do the tripple buffering side and just disable VSYNC in games? Or does the app auto detect any D3D instances (games) and just manually enable it? I'm late to the party but it seems extremely useful.
 
Some slight help. I'm using RadeonPro to make profiles. Should I just let D3DOverrider do the tripple buffering side and just disable VSYNC in games? Or does the app auto detect any D3D instances (games) and just manually enable it? I'm late to the party but it seems extremely useful.

Depends on the game. Some use triple buffering automatically. D3DOverrider is the safe option, but RadeonPro should do the same thing just as effectively... in theory.
 
Any idea why D3DOverrider isn'nt opening? It's there, running in task manager under processes but when i click to open it, nothing happens..?
 
Any idea why D3DOverrider isn'nt opening? It's there, running in task manager under processes but when i click to open it, nothing happens..?

Close your browser and try again. I had my mind blown by this the other day in the Steam thread.
 
So I see this feature in Nvidia's new beta drivers:

NVIDIA Adaptive VSync

Many gamers enable Vertical Synchronization (VSync) to prevent screen-tearing, an unsightly occurrence caused by frame rates exceeding a monitor’s refresh rate. The downside is the occasional and equally annoying stutter when frame rates drop below the locked VSync frame rate, and again when they return to the locked rate.

To fix the problem, the GeForce 301.24 beta drivers come loaded with NVIDIA Adaptive VSync, an automated technique that disables VSync when frame rates fall below the locked rate, and re-enables it when they return to the locked rate, significantly reducing stuttering whilst still preventing tearing.

http://www.geforce.com/whats-new/articles/nvidia-geforce-301.24-beta-drivers-released/

How is this different than vsync + triple buffering?
 
Nice. They also added a frame rate target feature which allows you to set a max framerate. This is useful for people that would rather have a game run at a solid 30 FPS instead of a messy 60.

Pretty good driver update, actually. And I usually don't care about driver stuff.
 
Because it doesn't need triple buffering to avoid performance hits... and has no extra input lag that's added with triple buffering. It just shuts VSync off when the FPS goes below your monitor's refresh rate.

Why even use that when frame rate target is available. Won't frame rate target limit your fps to your monitor refresh rate so that you wouldn't need v sync ever?
 
So far I prefer adaptive vsync to this solution. I'm probably not qualified to judge this, but I feel like I have less input lag, and the tearing is very minimal. I really had a distaste for the little stuttering problem, and this really seems to help. Skyrim is a prime example...slowly panning is so much better now.

Why even use that when frame rate target is available. Won't frame rate target limit your fps to your monitor refresh rate so that you wouldn't need v sync ever?

I don't really know how this is different from the frame limiter that's been around, but I'm always interested. Also the tearing is worse when using that method. Far worse than any I've seen since using adaptive vsync. I never noticed the stutter from 60-61 as opposed to 60-59.
 
Because limiting your frame rate does not prevent screen tearing. Vsync does.

I thought that tearing occurs when the frames per second goes above your monitor refresh rate? Mine is 60 so if I limit the frames so they never go past 60 I thought I'm good. I thought all v sync does is lock your frame rate to 60 or 30. I must not understand it correctly.

From Nvidia's Page

Using third-party tools such as EVGA Precision X, all NVIDIA GPU users can now enable NVIDIA Frame Rate Target to limit application frame rates to a specific, pre-defined frame rate. Its uses are many - for example, frame rates in decade-old games can be limited to 30 to prevent incompatibility issues; frame rates in today’s games can be limited to 60, preventing the GPU from working to the max, reducing heat and noise output; and frame rates can be capped to the monitor’s refresh rate, preventing tearing without enabling VSync.
 
I thought that tearing occurs when the frames per second goes above your monitor refresh rate? Mine is 60 so if I limit the frames so they never go past 60 I thought I'm good. I thought all v sync does is lock your frame rate to 60 or 30. I must not understand it correctly.

From Nvidia's Page

Screen tearing still occurs without Vsync when your FPS goes below 60 FPS without Vsync. And I believe even at a cap of 60 without Vsync, it still will tear to some degree.

For example, I don't use Vsync/triple buffering in BF3, just limit the FPS so that it stays locked at 60 and my GPU doesn't work overtime. But screen tearing still happens.
 
Didn't really work for me. Downloaded the beta drivers with a GTX 460 and was getting some tearing even with it enabled. Worse, when I decided against using it and disabled it, it completely wrecked D3D and it wouldn't work. Tried restarting and everything. Was getting massive tearing. Had to uninstall the beta drivers and reinstall the last official drivers to get D3D working again.
 
nothing in the tray, but D3Doverrider.exe is in task manager, even went to customize on the tray and still nothing there.

Edit: read a couple of forums and no one knows why its happening to them either, no solutions, and these posts are from 2009 and 2010.

Here is a picture of what im talking about
http://imageshack.us/photo/my-images/189/22255932.jpg/

I now got the same problem though it was working several weeks ago. The process is running, but it doesn't show up in the tray and it does nothing. An idea?
 
I did, doesn't help....

did you try the other d3dov exe?

iJG1WEDcgKUGK.jpg
 
Is it possible to DISABLE triple buffering? Someone said that recent games already comes with triple buffering built-in, and I do notice that, since even without forcing triple buffering, my framerate never drops from 60fps directly to 30fps.

I was wondering how Nvidia's adaptive vsync also works with games that already have triple buffering built-in, since both are not meant to work together.
 
There is no real way to reinstall it. But I did deinstall and reinstall the complete rivatuner package... :(

Did you try putting it into compatibility mode? I googled it and alot of people say pretty much the same thing that it's an active process but it's not in the system tray but after a few minutes it shows up. if it still doesn't work use radeon pro assuming you have an ati card.
 
Did you try putting it into compatibility mode? I googled it and alot of people say pretty much the same thing that it's an active process but it's not in the system tray but after a few minutes it shows up. if it still doesn't work use radeon pro assuming you have an ati card.

No, not yet. Which compatibility mode should I try? In the past it was always in an instant in the tray. It was working within the browser too., f.e. while watching a youtube video or so. :D How long should I wait?? I let it idle for 10 minutes but it still didn't show up. :(
 
I can't get D3DOverrider to work with Source games. There's a built in profile for hl2.exe which is set to medium and I also have the global one set to medium but it doesn't work. Setting either one to high or low doesn't help and it's bumming me out.

The games aren't running in a borderless window or anything like that, so I can't really figure out why it isn't working.
 
I'm trying to use D3DOveriderr for Just Cause 2 but I'm still getting tons of tearing and I'm not getting a sound or anything from D3DOveriderr when I start up the game. Any ideas?
 
Is there any harm in using D3Doverrider with games that natively support triple buffering like BF3? Also, how can you tell if a game's vsync is triple buffered.
 
Is there any harm in using D3Doverrider with games that natively support triple buffering like BF3? Also, how can you tell if a game's vsync is triple buffered.

No, and you can tell if it's working or not by how the game reacts when the framerate drops below 60. If it stays in the 50s/40s, it's triple buffered, if not, it drops immediately down to 30.
 
quick question, if i already have my triple buffering turned on in my nVidia panel, is it gonna cause any problem if I also enable it in the games that support it?

also, is it necessary to turn on both v-sync and triple buffering?

thank you all
 
quick question, if i already have my triple buffering turned on in my nVidia panel, is it gonna cause any problem if I also enable it in the games that support it?

also, is it necessary to turn on both v-sync and triple buffering?

thank you all
nvidia control panel triple buffering only works on OpenGL games AKA 99% of your games won't be supported. You need to use D3Doverrider if you want triple buffering on most of your games.
 
So far I prefer adaptive vsync to this solution. I'm probably not qualified to judge this, but I feel like I have less input lag, and the tearing is very minimal. I really had a distaste for the little stuttering problem, and this really seems to help. Skyrim is a prime example...slowly panning is so much better now.



I don't really know how this is different from the frame limiter that's been around, but I'm always interested. Also the tearing is worse when using that method. Far worse than any I've seen since using adaptive vsync. I never noticed the stutter from 60-61 as opposed to 60-59.

I find this weird because I do not like adaptive at all. Tried it quite a while ago with my 460 and quickly disabled it (for reasons posted earlier). But when I got my 660ti, I figured I'd give it another go. Loaded it up and Darksiders II was immediately jittery. Turned it off, loaded up the exact same point, and butter smooth. Maybe in the future I'll give it a third shot, but I'm not real sure I ever will again. I guess with a 120hz monitor, it's just become something I can live without now.
 
No, and you can tell if it's working or not by how the game reacts when the framerate drops below 60. If it stays in the 50s/40s, it's triple buffered, if not, it drops immediately down to 30.

I didn't see a game dropping to 30 in ages with active vsync.
 
So, after months and months of on and off usage, I've decided to take screen tearing over input lag. Triple buffering does a lovely job of cleaning up the image, so the graphics whore in my loves it, but fuck that input lag. Fuck it to hell. Its just not worth it. I value precision and response time far too much.

Unless there's some magical fix I'm missing?

Try turning down graphics options. My assumption is that the faster your frames render, the lower the input lag. (At least that's my assumption due to the ordering of things).
 
Top Bottom