- iRacing.com Announces iRacing 2.020,161
- Dave Kaemmer Comes Clean on Dirt13,052
- iRacing.com to create virtual McLaren MP4-12C GT312,063
- Release Notes for 2012 Season 311,408
- Scanning What’s in Store for iRacing with Tony Gardner10,522
- The iRacing.com Protest System – May, 201210,319
- Building the iRacing System 1018,983
- Improving the Sound of iRacing7,614
- iRacing.com to Build Digital Honda for New Super GT Series7,371
- Two New Cars and Two New Tracks Coming to iRacing Soon6,750
- Dave Kaemmer Comes Clean on Dirt 44
- iRacing.com Announces iRacing 2.0 41
- The iRacing.com Protest System - May, 2012 33
- Bathurst Coming to iRacing! 30
- iRacing Announces Added Features, Lower Prices 24
- Scanning What’s in Store for iRacing with Tony Gardner 22
- No Obstacles Here 18
- iRacing Simulation Gives NASCAR Hall of Fame Guests Authentic Driving Experience 17
- iRacing Poll on Possible Championship Points Structure Changes 17
- Improving the Sound of iRacing 15
-
iRacing.com
3065
-
Motorcycles
2471
-
NASCAR
2299
-
Formula Cars
2080
-
WRC
1830
-
IndyCar
1600
-
Touring Cars
1213
-
Other Racing
500
-
Sports Cars
310
V-Sunk
by Ray Bryden on November 15th, 2009
In the past, when I configured my video each time I upgraded my system, I made sure to check-off the box for V-Sync under the graphics options because the resulting effect on the sim was quite smooth and produced the best moving image quality with little or no stutters or “artifacts”.
So I have been quite happy with this and what I would describe as intermediate settings (no shadows) on an intermediate quality video card and CPU/motherboard. But although the graphics quality is more than sufficient for my needs I have plateaued in my driving skills, which I always blame on lack of available time to devote to practice and improvement.

My kingdom for an apex.
But after reading a couple of recent forum threads related to graphics settings (specifically V-sync) and input lag, I was curious if it would have any affect on my system and my limited control skills. The V-sync is a graphics setting which locks the graphics card into a pace which matches the refresh rate of the monitor, so the resulting stream of images progresses in a controlled pattern and the result is a quite smooth transition from frame to frame, which is pleasing to the eye. When the graphics are not V-sync’ed you can allow the graphics card to run unlimited, allowing it to generate as many frames as it can (but which are only displayed at the rate of the monitor refresh, so several frames are drawn by the card but not displayed), or you can cap the graphics card at a certain frames per second (fps) rate, defaulted at 83. Often, the result of capped or unlimited settings is a variable number of dropped frames, leaving the rate of change of the view to vary from frame to frame apparent to the viewer. As a result the scene flows in a much less smooth sequence and is generally less pleasing to the eye. Some even report eyestrain problems when running with V-sync off.
I decided to run a quick test to determine if V-sync settings played any role in my driving performance. When V-sync was on I noticed a barely perceptible lag between the time of my inputs (turning the wheel or applying pedals) and the resulting change in the inputs displayed on the screen. I figured the latency time was observable but not significant enough to play a role in my driving experience. So I took out the new Corvette C6.R – a car I am pretty unfamiliar with – to a test at Watkins Glen (Boot) – a track I am pretty unfamiliar with – and could only manage to set a time just under the 107% of the world record after about 12 laps with quite a few spins. Then I turned off the V-sync and limited the card to 83 fps, and noticed the lack of smoothness of the flow, but was able to mostly ignore it. I also noticed that the wheel appeared to have no noticeable lag between my inputs and the on-screen wheel response. I also found that my control was much better and though I was in hot-lap mode I made much fewer mistakes and got my personal best time down my almost a two and a half seconds (104.5% off the world record) on my eleventh lap. I repeated the test with V-sync on and spun quite a bit more and struggled to get within a second and a half of the V-sync off time after 12 laps. Scott Husted reported an almost identical experience in his tests with and without V-sync, and many others have confirmed the same thing.

I'm sensing a lack of grip.
This was quite an eye-opener for me. I didn’t think the lag was that bad to begin with, but once it was reduced I noticed that I had much better control over the car and was able to catch potential spins with much more ease and confidence compared to when V-sync was enabled. I am going to follow-up with a more fair and extensive test to try to better characterize the latency and attempt to quantify how my graphics settings affect it and whether it plays a role in the validity of my past performance excuses.
But in the end it comes down to driver preference and some cannot bear to shut off the V-sync setting due to the loss of smoothness. Some will not have any change in the input latency with changes of this nature as it is very system-specific. However, at this point I highly recommend trying to drive without it enabled to see if it improves your sense of control, whether or not you can notice the input lag.
My only trouble is I have to find some new excuses for being so far off the pace, because it surely can’t be due to my skills. Ahem.









David Phillips
Chris Hall
Jameson Spies
Jason Lofing
David Ifeguni
Katier Scott
Dylan Sharman
Nathan Aljoe
Austin Hartenfels
Jordan Hightower
Scott Kelly
Kenneth O'Keefe
Chris Owens
George Wood
Fabrizio Cuttin
November 18th, 2009 at 2:28 amI’m really more comfortable with vsync tuned on, but I will try more extensively turning it off: I’m curious about it.
peeH
November 21st, 2009 at 1:24 amThey shouldn’t stop pooling the inputs and stop ticking the physics while the graphics engine wait for the v-sync. They need to better parallelise their game engine.
W
November 21st, 2009 at 7:29 amI think you made the wrong approach to this, you should have tested on a track you are VERY familiar with and a car you are VERY familiar with. Off-course you are likely to pickup time when you continue to make laps on a track as you become more and more familiar with it.
mofle
December 22nd, 2009 at 10:45 amSo much of this i psychological – do a double-blind test if you actually want to do a relevant test
That being said, iRacing does feel a lot different at 150fps vs. 60fps, vsynced or not – and racing games don’t really suffer from tearing in the way that e.g. shooters do.
Alison Hine
December 30th, 2009 at 5:54 pmI ran with Vsync on ever since getting into the beta in June 08 because with it turned off I was getting a bizarre texture squirming that made me dizzy. The top part of the screen would be from one frame, the bottom from an earlier frame, so the whole sense motion was distorted in a very unsettling way.
Vsync cured this. I also set Frames Rendered Ahead in the nVidia Control Panel to 0 to eliminate display and controller lag.
That was with an nVidia 8800GT. Over the winter I got a 9800GTX+ OC, but I kept Vsync on and just cranked up my graphics details. Ah, full shadows! Wonderful!
But I wasn’t racing very much and when I was, I felt frustrated. In retrospect, I think this was because I never felt connected to the car; I was always reacting to things that had already happened instead of what was going on right now, and my inputs took a little time to get to the car’s physics.
Then Todd Bettenhausen convinced me to turn off Vsync. Suddenly my experience with iRacing was transformed! I felt totally connected to the car. Its responses to my inputs were instant, precise. On road courses I immediately gained a couple of seconds in lap times.
At first I was running with frame rate uncapped. Frame rate was mostly between 150 and 250 FPS. I read that this overworks the video card, so I capped the frame rate at the default 82 FPS. The immediacy went away; I felt disconnected again. So I removed the frame rate cap.
At a few corners on some tracks (Road America, for example) the frame flow got choppy and/or the screen squirming came back, so I turned off shadows. It seems that as long as the frame rate is running above 150 or so, everything is quite smooth and there’s no squirming.
I tried the steering wheel test: I turned on the on-screen wheel and got in the car. I turned my G25′s wheel back and forth rapidly. With Vsyc off, the wheel on the screen moves in perfect synchronization with the actual wheel.
Then I turned on Vsync and restarted the sim. With Vsync on, there is a very, very noticeable delay. The on-screen wheel’s motion lags the real wheel by a significant amount.
I suspect that the video card and driver have an impact on this. Perhaps some (ATI?) cards don’t exhibit the same behavior. Perhaps there are other settings in iRacing or in the video card control panel that will minimize the delay with Vsync turned on. (Todd tells me that now he is running with Vsync on, but he’s turned off AA and AF in iRacing and instead turned them on in the CP – and that this gives him very minimal lag.)
But as far as I’m concerned, based on my own experience, zero lag trumps everything else. I need that instant response to my control inputs, and I need that instant feedback through the wheel and on the screen. I don’t care if I’m overworking my video card. If it cooks itself I’ll get a new one.
No more V-sunk for me!
Alison
Ray Bryden
December 30th, 2009 at 7:22 pmAlison,
Thanks for your comments. Yes, that was exactly my experience too. I didn’t believe I had a lag problem until it was eliminated by turning off V-sync and I think that could have saved me from a lot of spins.
I have a new 5850 card now, but before I install it I am going to tinker with settings and see if I can learn a little more about what has the greatest effect on lag.
Szymon
February 13th, 2010 at 8:18 amI’ve discovered that although there is no possibility to set limit above 84 fps in game menu, you can actually set it manually in .\My Documents\iRacing\renderer.ini file:
LimitFrameRate=1
DesiredFPSLimit=169
Those two lines should practically eliminate lag and make constant fps which is I believe better solution than just vsync off with variable framerate.
169 fps is the max limit fps you can set, everything above will be cut down to 169, but you can set any frame rate below, maybe 150FPS which is 2,5x of standard LCD refresh rate would be better for you so I will be thankful for your feedback.
Justin Weisel
March 8th, 2010 at 8:39 pmI’ve never used v-sync. Not for iRacing, and not for any games or other sims I play. For this exact reason. I just feel like I have more control over the situation and my response time is better.
Luis Babboni
April 21st, 2010 at 7:30 pmEven with FPSs limited at 60, the “under water” sight I ahve cause the VSync in off is simply not tolerable to me
I have an AMD Athlon X2 with 2.9 each core and an ATI 4850 of 512MB
Lise Reul
November 8th, 2010 at 6:45 pmThis post appears to recieve a large ammount of visitors. How do you advertise it? It offers a nice unique spin on things. I guess having something authentic or substantial to give info on is the most important factor.
Etha Haifley
November 13th, 2010 at 1:11 pmWhile it’s good to be able to understand , avoid using that unless you really need to.
vlookup example
December 14th, 2010 at 1:18 amThanks for taking the time to discuss this, I feel strongly about it and really like understanding extra on this topic. If possible, as you acquire expertise, would you mind updating your blog with additional information? It’s very useful for me.
Remco Hitman
May 14th, 2011 at 11:25 pmThe trick is to limit the framerate to a multiple of your monitor’s refreshrate.
V-sync serverely increases input polling interval, which is what causes the lag. Running iRacing uncapped is the best way to combat input lag, but can introduce off-putting image faults when refreshrate and framerate are running very out of sync.
I’m running a 200cm projector image myself and image tearing is a huge problem on such a large image. I used v-sync for years until a freind showed me just how much input lag is introduced! Intolerable!
Make sure you install a framerate limit which is a multiple of the refreshrate, and verify that your system is able to maintain this rate most of the time.
Most screens use 60Hz nowadays, so 120fps is a good place to start.
Using 60fps would be about as bad as using v-sync! More is better in this case and, if you can, use 180fps. There is less of a chance that refresh and framerate are out of sync because at 180fps the frames last a lot shorter. I am using 180fps myself. It produces virtually no noticable tearing while, like Alison and Ray, I feel much more connected to the car.
The best of both worlds!
GLA, easy T1, antiwise rules etc etc…
Miracle On 34th Street
February 24th, 2012 at 5:55 amVery good blog! Do you have any hints for aspiring writers? I’m planning to start my own site soon but I’m a little lost on everything. Would you recommend starting with a free platform like WordPress or go for a paid option? There are so many options out there that I’m completely overwhelmed .. Any tips? Cheers!