P.S. You're drastically reducing the life span of your video card letting it run wild at 105 fps, I would suggest force capping it at 60.
Noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo.
Sorry, but I have to chime in here. I have done a lot of research into FPS and how it plays into performance on iRacing specifically, as well as have abused quite a number of video cards in bitcoin and litecoin mining.
First of all, capping your fps is not going to have a significant impact on the lifespan of your video card. Gaming is nowhere near as intensive as massive parallel computing on video cards, and I've had cards run for over 6 months at 100% utilization 24 hours a day with a core temp at 80C. And they still worked after that, but error rates became unacceptable for the GPU computing applications, they would still run games with only a tiny number of artifacts showing up in the rendering.
If you're concerned about lifespan, keep an eye on temps making sure they're below 75C for the majority of cards, but dont cap your video card at your monitor refresh rate as a preventative measure, which leads me on to the next topic.
There are multiple factors involved in FPS and refresh rate. First is what is the maximum refresh rate a human can actually discern? Most studies put this up around 150Hz-250Hz as the absolute maximum. However, as you go up, there are diminishing returns. The difference between 60hz and 120hz is much greater than 120Hz and 180Hz.
For all practical purposes, 120Hz is about all you need for the smoothest of possible representation of objects moving with continuity. Optimal 3D Tvs are 240Hz so they can represent 120Hz for each eye.
That's only part of the story though, the other is input lag. At 60Hz, the reaction of your car on screen can be up to .01666... seconds behind what it is in the game engine. Thats almost 17ms of input lag added in by refresh rate alone, not counting all the processing and pixel response time that adds to input lag. Over 40ms of input lag is considered detrimental to performance. At 120hz, you cut that overhead in half.
As for frame rate, you don't want V-sync on, and you don't want to cap at your refresh rate. Both can lead to dropped frames as your video card has no buffer built up and if it gets even a little behind you'll see problems.
One could write a book on all the info around refresh rate, frame rate, input lag, etc. These are just cliff notes. If you want to take my word for it, my recommendations are below. If not, all the info is out there to do the research yourself.
I will tell you that when I switched from a ~80ms input lag setup to a < 20ms input lag setup for iRacing, my times dropped by over a half second on nearly every track. Those milliseconds add up when your response to car reactions on the limit is just a little bit behind in every corner.
Monitor: 80Hz+ CRT or 120Hz LCD with tested and verified low-to-no input lag (10ms or less). CRTs have always had nearly instant pixel response, so they were preferred. Recently true 0 input lag LCDs have become available.
Graphics: Aim for FPS to average around 2X your refresh rate to ensure maximum smoothness. Having extra frames "in the bank" allows your video card to always present you with the most recent frame without screen tearing or lag-inducing V-sync.
Settings: No frame cap, no triple buffering, no V-sync. Monitor set to direct, game, or instant mode (aka no post-processing of video signal).
