You just got more sensitive to input lag. I avoid using v-sync even with triple buffering on FPS games where I use mouse and keyboard as it drives me crazy. For games I use controllers on or non-fps MKB games the input lag is far less noticeable.Easy_D said:Has this been asked? If it has, pardon me. Anyway, why is it that no matter what, Vsync introduces lag, despite forcing tripple buffering? I thought it was just Dead Space but it happens in more games. Is this AMD having shitty drivers? Or some kind of shit going on with the 5k series?
Must be my new mouse then, it's much more sensitive and accurate and I regularily turn off mouth smoothing. Geez I'm ultra sensitive thenStallion Free said:You just got more sensitive to input lag. I avoid using v-sync even with triple buffering on FPS games where I use mouse and keyboard as it drives me crazy. For games I use controllers on or non-fps MKB games the input lag is far less noticeable.
Zoolader said:Am I not allowed to set graphics settings using Rivatuner while using the newest Nvidia drivers? Or am I doing it wrong?
I use a mix of in-game and Nvidia Inspector which is just a better interface for the Control Panel.Zoolader said:I'm good on using d3d for triple buffering but I thought i read that techies preferred using rivatuner for forcing anti aliasing, anisotropic filtering, and such. Should I just leave that for in game setting or the Nvidia control panel?
Don't do "force off" in control panel, set it to application controlled.Smokey said:For some reason I can't get D3D to take affect in Crysis 2?
I hear the beep when the game starts, yet there is still tearing. I have vsync to "force off" in nvidia control panel, and I have it set to off in Crysis 2 as well.
Any suggestions here ?
Stallion Free said:Don't do "force off" in control panel, set it to application controlled.
Yeah.Smokey said:But leave it off within Crysis 2?
Des0lar said:OK I'm at a loss here. I hear the "beep" when I launch the game, there is a d3doverrider.exe in the taskmanager, but for the love of my life I cannot find the tray icon to change the settings of this thing. It's just there in the background somewhere... lingering
entrydenied said:Same problem here...
Do you by chance have overdrive enabled or are overclocking?dark10x said:I do have one issue that crops up on occasion and I'm wondering if anyone has any ideas as to what can be done.
Basically, with a few select games, running in fullscreen causes slight stuttering in the framerate (like microstuttering). It completely ruins the fluidity of the game despite the fact that FRAPS reports 60 fps constant. If I switch to windowed mode, however, this issue clears up and the game runs flawlessly.
The games I've encountered this with are Mafia II, World of Warcraft, Duke Nukem Forever, and perhaps one or two others.
I just tried WoW out for the first time yesterday (the free option) just out of curiosity, and I was surprised to experience this issue. I simply switched to "windowed fullscreen" mode and the problem, of course, cleared up. I had to do the same for Mafia II.
With Duke Forever, enabling shadows causes this problem. In fullscreen, it appears to drop frames (despite FRAPS suggesting otherwise), while in windowed mode things are flawless.
I cannot for the life of me figure out what is causing this issue. I've even just re-installed Windows 7 on a new SSD drive and yet the problem continues.
It's obviously something to do with my graphics card (Radeon 5870) and the way the games in question were coded, but it just doesn't make sense to me. What is it about fullscreen mode that causes it to respond different than windowed mode?
In WoW go to Advanced options and enable "Reduce Input Lag".dark10x said:I do have one issue that crops up on occasion and I'm wondering if anyone has any ideas as to what can be done.
Basically, with a few select games, running in fullscreen causes slight stuttering in the framerate (like microstuttering). It completely ruins the fluidity of the game despite the fact that FRAPS reports 60 fps constant. If I switch to windowed mode, however, this issue clears up and the game runs flawlessly.
The games I've encountered this with are Mafia II, World of Warcraft, Duke Nukem Forever, and perhaps one or two others.
I just tried WoW out for the first time yesterday (the free option) just out of curiosity, and I was surprised to experience this issue. I simply switched to "windowed fullscreen" mode and the problem, of course, cleared up. I had to do the same for Mafia II.
With Duke Forever, enabling shadows causes this problem. In fullscreen, it appears to drop frames (despite FRAPS suggesting otherwise), while in windowed mode things are flawless.
I cannot for the life of me figure out what is causing this issue. I've even just re-installed Windows 7 on a new SSD drive and yet the problem continues.
It's obviously something to do with my graphics card (Radeon 5870) and the way the games in question were coded, but it just doesn't make sense to me. What is it about fullscreen mode that causes it to respond different than windowed mode?
IIRC Amnesia is an Open-GL title which isn't what you would use D3Doverrider for.zazrx said:I did what it says in the OP but I keep getting tearing. I'm trying Amnesia: The Dark Descent but it's just not working. So much tearing in that game.
Got it, thanks.Stallion Free said:IIRC Amnesia is an Open-GL title which isn't what you would use D3Doverrider for.
Try forcing v-sync/triple buffering through the video card control panel.
I've never had a problem, having played at least 100 games.hauton said:I don't think this is very good advice anymore, with D3DOverrider development having been discontinued and there being an increasingly overwhelming amount of titles/hardware configurations/renderer settings that either don't work or actively make things worse with D3DOverrider's force TB/vsync.
Is this true?hauton said:I don't think this is very good advice anymore, with D3DOverrider development having been discontinued and there being an increasingly overwhelming amount of titles/hardware configurations/renderer settings that either don't work or actively make things worse with D3DOverrider's force TB/vsync.
K.Jack said:I'd like to see this overwhelming list.
Corky said:I'll chime in with the "played 100s of games"
and the ones I've had problems with have so far been :
- GTA 4 : d3doverrider does it job and removes all the tearing and whatnot, but introduces added minutes to loading times.
IIRC somebody in this very thread suggested a fix for it but I don't have it installed anymore to try.
seldead said:gta 4 is a strange case. If i recall, youll find the load times increase drastically simply by not using the games vsync, not specifically because of the triple buffering. its one of the few games i use ingame vysnc on for this reason
AEREC said:Just out of curiousity...why is triple buffering not a standard feature in video cards driver control suites nowadays?
In almost every game Ive used D3Doverrider in Ive gotten a considerable boost in performance...are there drawbacks I am missing here?
AEREC said:Just out of curiousity...why is triple buffering not a standard feature in video cards driver control suites nowadays?
In almost every game Ive used D3Doverrider in Ive gotten a considerable boost in performance...are there drawbacks I am missing here?
They can do it for OpenGL. I heard that for DirectX it wouldn't get WHQL approved or something similarly stupid.AEREC said:Just out of curiousity...why is triple buffering not a standard feature in video cards driver control suites nowadays?
I think the options in the ati and nvidia panels are just for openglCorky said:I'm pretty sure there are options for triplebuffering in the nvidia control panel, but I stick to d3doverrider. Could be wrong.
Durante said:They can do it for OpenGL. I heard that for DirectX it wouldn't get WHQL approved or something similarly stupid.