Experience a unique and different type of sim racing channel where you will see everything from tips and tricks to driving tutorials and setups. If you love sim racing, this is the place for you!
I did this recently, and then went back to my old settings (IRsidekick is awesome for that) and the difference was surprising, I think if there was a way to do it blind, I might say it's placebo on the visuals, but the FFB difference is really what stood out. On the visual size one note, he hasn't released the camera settings yet, but if you're like me and got used to a lower FOV cockpit location, and not are at a higher FOV, just edit you camera in replay mode, use the X axis to resize just the cockpit and leave the FOV alone.
I love this iracing game, but last night was the final sraw 3 races in a row down the drain because of this crap . If you're settings work tonight ill continue to play if not iam deleting i racing and going back to ps5 gran turismo 7 . Such bullshit there's no guidance from iracing on how to set up their game 🙄 they must lose a lot of players over this nonsense.
I will be honest, I have a 13700K and 4090 and I found your graphics video a couple months ago to miss the mark on quite a few things. However, this is just the opposite. You absolutely, 1000% nailed it and it IS repeatable every single time. I've tested this close to a dozen times using RTSS frametime graph and the stuttering with anything iRacing related (primarily the UI is what gets power throttled) consistently and repeatably causes stuttering. I am a scientist and know how to test a hypothesis. Thank you for discovering this!
I used his video. Very very helpful. I ran the settings for a while and change back, to confirm it wasnt just a placebo, i am now back to his way. It's so much better.
Just came across these video guides and setups. I was wondering if how this is setup can transfer directly to the regular late models and not just the supers? I know quite a lot has changed in the last 3 years regarding physics, track updates, oval updates and vehicle updates. Would it be unfair to say that something like this should also get a refresh to incorporate what you've learned over the last 3 years to better help out people just now getting into needing to setup their own vehicles for races? Thanks for the effort put into these!
@@Crownleyian and the ryzen performance issues with windows 11 ?, it also seems that every time there’s an update it seems to break something else, show me a benchmark where windows 11 outperforms iracing on windows 10 and I’ll believe you, but I’ve built lots of machines even running windows 11 and there’s basically zero performance benefit
@@Panterluca and I’ve worked on multiple Windows 10 systems where the taskbar and system settings always glitch not to mention Microsoft SSO that never appears. I’m getting 220fps on Windows 11 and I’m not experiencing any issues.
Even though I tried everything, I couldn't fix the stuttering problem. The system is installed on powerful hardware such as 13900KS, 4090, 64 gb 6000 mhz ram and all my drivers are up to date. And I am using a 170 Hz 1440p triple monitor setup. I changed the display cables. I tried the game on Windows 10. I undervolted the processor. I tried it with Nvidia surround and without Nvidia surround. I have a regulator that stabilizes the electricity of my house at 220W. Even though I tested many times in many settings, I could not fix the stuttering problem. I saw that there was no stuttering only when I run the game on a single screen. In this case, there were two solutions that came to my mind. The first is to change my motherboard and processor and switch to AMD. The second is to use a single, large ultrawide monitor. what do you think? What do you recommend ? There are almost no resources on the stuttering problem. That's why I'm asking for help here. Thanks a lot.
i thought the dirt cars were great when first introduced. specifically the sprint cars and ump modifieds, their first dirt overhaul completely butchered dirt racing, and it hasn't felt right since.
Agreed about the wheelspin vs just snapping lose. I noticed that right away. I referred to it as "not losing the front end" anymore. Definitely an improvement. It's a head scratcher that they used the word "slightly" in the notes though...
The under volt did awesome for my frames and PC ran awesome. Until it rained. The rain killed the performance. Dropped to 38-40 FPS. No I didn’t have SSR on. But a dry track it runs amazing
Can someone explain to me, how the performance setting for the iRacing UI, which is minimized in the background, can affect the performance of the iRacing Simulator, which is already running without power throttling? If anything, I'd expect the performance of the Sim to regress, since the system now needs to take care of another (useless) task with high priority. The same goes for the Racelabs UI. I would assume the 4 different tasks in the list below to be related to the actual overlays. Again, the system now needs to handle an additional, irrelevant task with high(er) priority and the total performance should be worse. Please do some poper (repated) A/B testing to proof these points. Otherwise I'm putting them into the "snake oil" category.
You can put them in whatever category you want but I’ve A/B tested this a half dozen times with a 13700k / 4090 on a single screen and it absolutely causes my stuttering issue to be resolved. UPDATE: Just tested it 2 more times and 1000% power throttling of the UI causes stuttering on my system. Clearly visible in RTSS frametime and clearly repeatable.
At 32:50, how would you approach fixing something like that? This is the issue I have at every track. Too much LF wear, not enough RR usage. I can generally work my way towards evening out the front wear, but haven't found a way to wear the RR more. It's driving me insane, I feel like I'm not understanding something regarding weights.
Hey 👋 Tommy sorry for bothering you with this I have been busy this whole summer and have not been on iRacing a whole lot but why are all of my Xfinity series open sets failing especially the one for Atlanta that is only as old as the last time we raced Atlanta new Atlanta thank you sir. Have a great day.
Do you have intel 13th or 14th generation as CPU ? Intel told that the CPU could have issues, too much voltage. It can create crash on games, sluttering and a lot of other symptoms. Intel provided a BIOS update on 15th August to solve this issue. But if your CPU is already damaged, it won't help at all.
Changing cars in iracing change the force feedback effect of course, that is why the auto FFB button is there, it adapts all the ffb inputs to the wheel. sending the right amount of signal to your wheel. independently that the brand i think.
Further to my comment on part one that I just made a few minutes ago, I have a question. I was wondering whether or not you had tested the different shaders by starting with all of them off and just turning, say, heat haze on alone. If that’s the case, it might explain the increased variance when all shaders are off. Quite frankly, iRacing’s devs take a lot of shortcuts. And it would not surprise me at all if they’ve done some optimization with shaders on that don’t exist when all shaders are off. So even having one shader turned on could make things smoother simply because the shader code is functioning regardless of which shader you’re talking about. If you have at least one on, whatever optimizations they’ve done for when shaders are on are in play, and so things are smoother when shaders are active. Turn them all off and it goes to crap. I’m really, really hoping their next render is actually decent. What we still have now has way too many roots in the old DX9 code and is one of the reasons it really doesn’t run all that great. The update to DX11 didn’t really help as much as they were hoping it would, and I think it was probably because of how much legacy code and/or legacy code thinking was still in place. Now that they’ve got some new devs onboard and are working on a new renderer there is some hope again. Benchmarking now with a single screen and the lowest resolution possible really shows how much the current renderer is tied to CPU performance. This takes the GPU out of the equation as much as possible and really shows how bottlenecked the renderer is by its single-threaded nature. Been using iRacing since 2009, and even back then I was amazed at how poorly the renderer performed. It has been a sore point for the sim throughout its entire life. Finally going to a multithreaded renderer might be a huge gift, whenever it finally gets released, which will probably still be years from now. Hehe
Compressed textures are for low graphics memory systems to help everything fit in memory. That’s not applicable to a 4090. iRacing can’t even come close to using up a 4090’s RAM. Compressing textures when that’s the case is pointless. Shadows aren’t geometry. Antialiasing smooths out geometry. Shadows are generated in a manner that does not involve MSAA, so naturally MSAA is not going to affect the quality of shadow edges. It works fine for what it is actually used for. It isn’t used for shadows. It is used on the polygon edges of all the objects. If you want to see what the difference is in the easiest way possible, load up that same track you had loaded for your shadow MSAA discussion and look at the light posts behind the grandstands. Those objects alias like crazy, and you should readily see the difference between the different levels of MSAA with those. Those are objects made up of polygons. That’s what MSAA operates on, polygons, specifically their edges. This costs fillrate, which means it will be a greater cost to performance on slower cards that are starved for fillrate while trying to render higher resolutions. Basically it is increasing resolution for specific portions of polygons, and it should be obvious that rendering a higher resolution takes more horsepower. FXAA and SMAA are shader programs that smear the pixels. They suck and should be off. They take the finished image and smear it, they just smear it in different ways. If you want *actual* antialiasing then you want to use the MSAA setting and that will actually do antialiasing on the geometry during rendering, rather than smearing Vaseline on the camera. A handful of the different effects are accomplished via shaders. Shader programs, due to their nature and how they’re processed, tend to share costs. Multiple shaders can run at the same time while not changing the overall cost very much, and this is why you may or may not see very much change in overall performance when turning one shader effect on or off. The shader effects are all listed on the lower right of that settings page. Motion blur, antialiasing, SSR, sharpening, distortion, DOF effect, heat haze, HDR, SSAO, replay render modes. All those are done with shader programs. They do have different costs for each one, but with how shaders run it isn’t actually a simple addition or subtraction of a given amount of performance. They share processing resources to some extent, and so turning one or two off or on isn’t going to change the cost by a given amount. This will vary from card to card because different cards have a different number of cores that can process shader programs. The cost for a given scenario on a 4090 isn’t going to be the same for that same scenario on a 3070 because they have a different number of hardware units for running shader programs. Shaders start costing more when you start running low on available units to run the programs, so a 3070 is going to start choking on shaders sooner than a 4090 will. And benchmarking on that 3070 is going to return very different results when comparing shaders on/off because of that.
There is another trick to help CPU latency and stutter, the paid version of Process Lasso. I have been using the free version for years, but iRacing blocks CPU affinity changes as part of the anti cheat. But, you can use CPU Sets to get around this in Process Lasso. Only catch is that it is, that setting is only in the paid version. But, a lifetime license is only $40, so not a huge issue. I set the iRacing DX11 exacutable that runs when you are racing to a CPU set that locks out core 0 and 1. In the case of my 5800x that is the first core and it's virtual thread. Since DX and windows live there, that core gets a real pounding when iRacing also wants to be there. This helps a lot since iRacing will run on some other core and core 0 is pretty much left to all other things in the background. In the past, getting any game off core 0 has been a huge help in getting rid of stutter. iRacing is just a bigger pain than most games in this regard.
Don’t have iracing yet but I raced real micros for 3 years. They’re absolutely badass to drive. The incredibly short wheelbase makes them very twitchy and easy to spin in the slick. Hope they add Sweet Springs, it would be fun to drive a track I actually raced at.
Hi as stuttering can really have different faces, it would be good is you say what exactly was happening to you. Were you getting microstutters that damagw feeling of smooth gameplay? It doesnt matter 60 120 or 165 FPS - with microstutters it all time feeles slow, feels like 30FPS. iRacing for me is really stuttering game, its stuttering engine in my opinion. Can you compare to AC1 or Automobilista2 and say is your iRacing anywhere close with smoothness to those titles?
Do you need to change the power throttling option every time you turn your pc on in task manager? Seems after a reboot my racelabs and iracing ui switch back to power throttling enabled
Hey @tommy ! I dont understand that in your ‘’ part one video’’ you say its better to use dynamic obj ‘’ in main & mirror’’ because your gpu usage gets higher = better fps but in this video you say to turn it off? 5800x3d + 4070 ti super… 2k monitor 40’’ msi 155hz so i cap my fps at 150
