DiRT Rally

DiRT Rally

View Stats:
wacky maky Jul 29, 2015 @ 5:31pm
Game very choppy without vysnc on? anybody else?
I seem to have to play with vsync on, without it, my reported framerate is high but something weird is happening it feels extremely choppy, and no im not referring to screen tearing it feels like really intense frame dropping. Does naybody have this problem/have a fix. I only really ask because I tend to play games with vsync off because I am not a fan of that input lag!
< >
Showing 1-15 of 48 comments
Meszes Jul 29, 2015 @ 11:49pm 
It's been like that for me ever since release despite having constant 60+ fps. I've just been using v-sync instead to get a fluid gameplay, input lag isn't a problem at all. It's a racing game, not a shooter.
zamoy72 Jul 30, 2015 @ 1:03am 
Yep, the same problem. Very choppy without vsync.
Squad Rallying Jul 30, 2015 @ 2:06am 
Another for the v-sync. Even though it ran fine for about a month with out it on ultra settings, for some reason the whole thing degraded.
DocStrangelove Jul 30, 2015 @ 4:37am 
I'm not sure anymore, but I think I have this since the last update. It's really fluent only when I'm over 120fps or so. VSync does add a small input lag, it feels a little bit more sluggish to me, although that may be psychological. Whether or not, I have more trouble driving cleanly, so I have to turn it off.

They said they're working on the replay-related stuttering issue, although that's about the heavy stuttering in a few areas mainly in Monte Carlo, I think. And possibly unrelated to this problem.

edit: just tried turning on vsync again, solves the problem only partially, and adds terrible input lag, more than I remembered. So out of question for me. Oddly enough, I seem to have tearing only with vsync on, so I really think there's some technical issue involved.
Last edited by DocStrangelove; Jul 30, 2015 @ 9:45am
Well Meszes: regarding input-lag, I think we agree to disagree. I do not wish for any. But then again: I am still planning on upgrading that old bugger of a graphics card. Waiting for the release of the "Nano" and then I think I will decide whether it is wort it upgrading to either that one or something else.

input-lag for me is as much gameplay-degrading as is ffb-clipping (or underperforming ffb in general). Oh -- and for all the "ultra-quality-bling-bling"-lovers: 60 frames a second as a minimum (at all times) is not a "nice-to-have". It is a necessity. I would gladly take triple 27" screens with 100fps minimum. I just cannot afford, let alone BUY stuff that guarantees this level performance.
And multiple graphics-cards as in sli or crossfire setups seem to behave weridly with all sorts of nasty side-affects in most racing sims. Which kind of makes it a no-no, anyway.
Meszes Jul 30, 2015 @ 7:05am 
Originally posted by Simon said DIE ♥♥♥♥♥!:
Well Meszes: regarding input-lag, I think we agree to disagree.

We agree as I'd love to eliminate input lag once and for all. But in my case without v-sync the game is so choppy that it's unbearable, so having v-sync ON is just the lesser of two evils.
wacky maky Jul 30, 2015 @ 7:38am 
Right well Im glad to hear its not just my gpu dying or something. Im surprised that Codies haven't acknowledged this issue seeing as it seems to be quite widespread.
Originally posted by wacky maky:
Right well Im glad to hear its not just my gpu dying or something. Im surprised that Codies haven't acknowledged this issue seeing as it seems to be quite widespread.
Yet they did acknowledge this a long time ago, already. In the current / or last / Dirtblog one of the stand-out improvements of the upcoming patch mentioned seems to address this apparently replay-related issue: replays are being moved into system-RAM with the next patch. Hopefully that will cancel out the problems with different drive-configurations and all that unnecessary IO load.
wacky maky Jul 30, 2015 @ 8:06am 
Originally posted by Simon said DIE ♥♥♥♥♥!:
Originally posted by wacky maky:
Right well Im glad to hear its not just my gpu dying or something. Im surprised that Codies haven't acknowledged this issue seeing as it seems to be quite widespread.
Yet they did acknowledge this a long time ago, already. In the current / or last / Dirtblog one of the stand-out improvements of the upcoming patch mentioned seems to address this apparently replay-related issue: replays are being moved into system-RAM with the next patch. Hopefully that will cancel out the problems with different drive-configurations and all that unnecessary IO load.
Well there we go, I stand corrected!
DocStrangelove Jul 30, 2015 @ 9:15am 
Originally posted by Meszes:
Originally posted by Simon said DIE ♥♥♥♥♥!:
Well Meszes: regarding input-lag, I think we agree to disagree.

We agree as I'd love to eliminate input lag once and for all. But in my case without v-sync the game is so choppy that it's unbearable, so having v-sync ON is just the lesser of two evils.

Vsync makes it a bit better, but adds terrible input delay, which I find unacceptable too. I found that getting really high framerates of 120 and more solves the issue without vsync and input delay. I have to reduce graphics options a lot and go to 720p to achieve it though, which isn't desirable either... but imo still better than input lag or stuttering.
Last edited by DocStrangelove; Jul 30, 2015 @ 9:42am
DocStrangelove Jul 30, 2015 @ 9:28am 
Originally posted by Simon said DIE ♥♥♥♥♥!:
Originally posted by wacky maky:
Right well Im glad to hear its not just my gpu dying or something. Im surprised that Codies haven't acknowledged this issue seeing as it seems to be quite widespread.
Yet they did acknowledge this a long time ago, already. In the current / or last / Dirtblog one of the stand-out improvements of the upcoming patch mentioned seems to address this apparently replay-related issue: replays are being moved into system-RAM with the next patch. Hopefully that will cancel out the problems with different drive-configurations and all that unnecessary IO load.

I don't think the replay's the reason. At least not if we're talking about the same issue.

There are two different issues:

A) in a few places, there's hefty stuttering seemingly unrelated to GPU load, but that's really only in some places, mostly in Monte Carlo and Germany iirc, and it always happens at the same spots. It feels like a loading issue, but it seems to be a saving issue. This is fixed with a workaround that disables replays. By the way, Dirt 1 had this problem already, and apparently people used the same workaround in the entire Dirt series, and it's taken the Codies quite long to acknowledge the problem and find a solution now.

B) Constant micro-jittering which looks and feels like inconsistent framerate, even if you've got stable 60fps or more. Enabling vsync makes it a bit better, but that in turn adds the typical input delay. It is also solved if you have *really* high framerates as I already mentioned, upwards of 120fps. But disabling replays doesn't do anything about it.

I believe in earlier versions of the game, neither of these issues were present, it only started with more recent versions, notably the Tarmac Terrors one. I might recall this wrongly, but that's how it felt to me.
Last edited by DocStrangelove; Jul 30, 2015 @ 10:18am
Meszes Jul 30, 2015 @ 9:44am 
Originally posted by DrStrangelove:
There are two different issues:
Nice summary preventing people to confuse the two issue.

Originally posted by DrStrangelove:
I believe in earlier versions of the game, neither of these issues were present, it only started with more recent versions, notably the Tarmac Terrors one.
B) has been with me ever since release with v-sync OFF.
DocStrangelove Jul 30, 2015 @ 9:47am 
Hm, I just tried turning it on again (hence the edit), and I still have the problem. Less pronounced, but still.

edit: And I said that because after the Tarmac Terrors update I had the feeling that I suddenly had massive framerate drops I didn't have before. And oddly enough, framerate counter and benchmark showed that nothing had actually changed, by numbers I had the same 55-70fps I had on launch. It only felt like big drops down to 30-40 even though the numbers say that nothing like that happened.
Last edited by DocStrangelove; Jul 30, 2015 @ 9:51am
could be that it is graphics-iq-settings related, though

Thanks again for the summary/reminder. Now I feel better about this thread and it is my turn so-to-say to stand corrected. About the replay-stutter-issue: I have always had this. Running without vsync, since my gpu is not really powerful enough to reach above 60fps_minimum with the settings I need having set, in order to make out where the road is headed.

The interesting part: it has been on and off. Never really vanishing for good, no matter what rally I was in. So yeah: vram overrun? some other background-shuffling going on? who knows - I do not! And even when I tested with no replays: might just be a little bit uneven frame-delivery that still made it feel not-so-smooth at times.

running hd5770/1Gib on a more-or-less freshly-built 5820k/X99, clean install of Win7-64-ultimate. with catalyst 14.12 "Omega".
Last edited by Simon said EAT DUST PLAYER_1 !; Jul 30, 2015 @ 10:12am
[F2C]MaDMaXX Jul 30, 2015 @ 12:43pm 
I too suffer the same problem, and like DrStrangelove, i do not believe the upcoming replay fix is the problem.

My game plays a lot better with VSync enabled, previously i was getting 80 something FPS, and whilst i feel the input lag a little (i play on keyboard :( ) i'm a lot faster with VSync on that when it was off.

I would love this problem to be solved, it doesn't really make sense, i wonder if the simulation engine is running out of sync with the graphics?
< >
Showing 1-15 of 48 comments
Per page: 1530 50