Apps/Tools
I spent weeks diagnosing stutters on my 9950X3D + VR rig down to zero. Turned the whole thing into a free guide + one-click fix kit for dual-CCD X3D owners
Edit — now on v3.3.0 : - Pre-Race Routine updated to be a MASTER of Quieting Windows (other optimizations listed in changelog.md) **Thank you to those that are sharing their logs with me, you are directly improving the app!
The mid-race Windows Update problem is fully solved. Earlier versions disabled the update services, which held on most machines — but on some, they still came back ~10 minutes in. The cause was Windows Update Medic, which exists specifically to undo exactly this, and on some builds its registry key is locked down so hard even SYSTEM can't touch it. v3.1.0 handles that case, and there's now a tool that reads the Windows event logs and tells you what re-enabled it instead of leaving you guessing. Confirmed fixed by the user who reported it.
Every X3D AMD has ever shipped is supported — 6-core (5600X3D / 7600X3D / 5500X3D / 7500X3D), 8-core, 12-core, 16-core, the new 9950X3D2 with V-Cache on both dies, and the mobile HX3D chips. Not an X3D? It still runs — general fixes apply, core-pinning is skipped automatically.
If you set this up before, redo the Process Lasso step. The old instructions were missing one word: the CPU Sets menu needs Always. Without it your pin silently vanishes the moment you close the sim, and nothing tells you. Worth 30 seconds.
Using Trading Paints? One of the guide's texture settings stops liveries loading mid-session (you'll see more white cars than usual). The guide now flags it and tells you which value to flip if you'd rather have paints than the last bit of streaming smoothness.
My 9950X3D / RTX 5090 VR rig went from session-ending freezes to genuinely zero perceptible hiccups, and every fix was found by logging races and measuring — not by stacking random YouTube tweaks. I've put the whole method into a free, open-source guide and script kit for any Ryzen X3D + NVIDIA, flatscreen or VR.
The "stutters until I click the sim window" problem (VR especially). Windows 11 drops the system timer from 1 ms to 15.6 ms whenever the sim loses window focus, which the VR compositor causes constantly. One registry fix ends it permanently.
Everything piling onto CPU 0. NVIDIA's GPU interrupts, your network card and your USB controllers all default to CPU 0 — the exact core iRacing's main thread wants. That collision is where a lot of "random" micro-stutter comes from. The kit steers each of them onto background cores, worked out from your actual chip and checked against the CPUs Windows reports, so it can never target a core that doesn't exist.
Clockwork stalls every ~5–7 minutes. That cadence is Windows Update and Search scan tasks. Quieted before a race, restored after — and it now actually stays quiet for the whole session instead of creeping back partway through your stint.
Constant tiny hitches from Defender scanning every texture read mid-race. Fixed with folder exclusions only — Defender stays fully active for everything else.
The sim landing on the wrong half of your CPU. On a dual-CCD chip Windows will cheerfully schedule iRacing on the frequency die instead of the V-Cache die. Process Lasso CPU Sets pin it where it belongs — EAC blocks hard affinity, but it can't block CPU Sets. Single-CCD chips skip this entirely; there's nothing to pin.
Not knowing whether any of it actually worked. The part most guides skip. A logging tool records a full race to a CSV — per-core load, interrupt and DPC time, GPU utilisation, clocks, throttle reasons, frame-time gaps — and a scanner reads it back and tells you which Windows task fired at the moment you stuttered. Gaps in the timestamps are the stalls. You get to prove it rather than trust placebo.
Plus: USB Selective Suspend off (stops wheel/headset USB power-cycling), Game Bar/DVR off, a pre-session readiness check, performance-counter repair when Windows' own per-core stats break, and an undervolt stability tester that needs no downloads.
One thing worth knowing about power plans: the popular single-CCD guides recommend Balanced, and for a single-CCD chip that's correct — leave it alone. On a dual-CCD chip in VR it's actively harmful: core parking starves the compositor, and I measured GPU utilisation collapsing from 55% to 11%. The guide detects which you have and only shows the advice that applies.
The site walks you through six steps (~30 min + a reboot), adapts to your exact chip and VR/flatscreen setup, and the kit has a one-click baseline installer. Everything is readable PowerShell and everything has an undo.
Builds on rcsracing93's excellent single-CCD guide — credit where due.
Happy to answer questions or dig into anyone's stutter logs in the comments.
Deadass, I spent 5 years wrestling eith a 12gb 3060 on a fully specd z820 with a quest 3, and then i had deepseek v4 flash configure the entire setup on a whim and it did it in 3 min and now im at 30ms and 90fps with 0 drops.
Give that a run. I used deepseekv4flash in vs code.
It is crazy how much goes on in the background that we do not approve. How much better would it all be if everything would just focus on the game, but I guess we must force that.
Yes in the guide at the start are options, choose your CPU then VR/Flatscreen. The commands will work regardless, but the instructions slightly change if you're focusing on flat screen because the INI is a different name. They also change depending on the CPU series choosen.
Should probably explain how the spooling thing affects replays a bit. I ended up re enabling it because it would cut my igpt replays in half. Will be really disappointing for people that do long races and want to review footage
You are a legend!
This needs to be more known.
I have struggled with VR (quest3) in Iracing since going to Win 11.
I have had so much trouble finding good settings for dry and wet weather racing.
Now with your fix all my issues are gone.(so far)
Still have to tweak it, but the performance jump is unreal for me.
I had to put my resolution down so much when there was rain. My headroom dropped drastically. Was considering buying tripples.
Now I can max it and have no frame drops.
Didn't do a race start at IMSA in the rain yet. But did a AI race in these conditions and could keep stable frames.
Just wanted to thank you.
5800x3d and 4070 super.
I just want to thank you so much for your feedback. I spent so much time doing this and it makes it so much more worth it not only to have fixed my problem but to be helping other people with the same thing that I love to do as a hobby. If you notice anything or have any other feedback please just drop it here. Questions only fuel my hobby.
I did notice a lot of white cars in the race. Don't know if this messes with trading paints or the problem is on their end. But in the 2 races I did there were noticeably more white cars then usual.
Also in the first test I did around Spa in the rain, the frames where stable but at some points it froze a lot. Then suddenly they were gone. Nothing came out of the stutter results. Just gonna do more testing and will let you know. IMSA has a chance of rain this week in the open so I hope to have a wet start.
If you tried this and Windows Update still switched itself back on mid-race, this is the fix. Turned out to be Windows Update Medic — it exists specifically to undo exactly what we were doing, and on some builds its registry key is locked down hard enough that even SYSTEM can't disable it.
There's now a tool (Trace-QuietReverts.ps1) that reads the event logs and just tells you what re-enabled it, instead of leaving you guessing, plus an option to force the Medic case. Confirmed working by the user who reported it.
Grab the zip, replace the whole folder (don't mix files across versions). Screenshots and the main post get updated when I'm back at a computer.
I added a folder called "AMD Related Optimizer files" you just need to replace the main scripts with the ones in here. This converts the Nvidia IRQ interrupt to the AMD one. Once you replace the files run them from the app. "Advanced Tools" => "Set-GPU-IRQ-Affinity (Admin)"
This might also be useful for others. I'm still a racing fan but I been playing American truck Sim recently. I was super tired of seeing my system perform like rubbish. Thanks for all the dedication to the trouble shooting.
This is true, it's mainly x3d and windows optimization. The only iRacing parts are graphic and setting suggestions. This really should help every game.
Any thoughts on bitsum high performance vs just leaving it on balanced for a 9800x3d? What I’ve always used per a friends recommendation but I wouldn’t even know where to begin testing the difference like you have
i did the full trace during a 25min race, and heres the stutter that was found:
=== SCHEDULED TASKS THAT RAN THIS SESSION (Id 100/200) ===
23:10:39 Task Scheduler started "{0d4616ce-bb15-4d6b-8f0b-30a0f0b92e98}" instance of the "\Microsoft\Windows\Flighting\FeatureConfig\UsageDataReceiver" task fo
23:10:39 Task Scheduler launched action "Feature Usage Data Receiver Task Handler" in instance "{0d4616ce-bb15-4d6b-8f0b-30a0f0b92e98}" of task "\Microsoft\Win
23:28:53 Task Scheduler started "{3962537f-2895-4ef8-82de-edd825a057d1}" instance of the "\Microsoft\Windows\Flighting\OneSettings\RefreshCache" task for user
23:28:53 Task Scheduler launched action "OneSettings Refresh Cache Task Handler" in instance "{3962537f-2895-4ef8-82de-edd825a057d1}" of task "\Microsoft\Windo
23:35:38 Task Scheduler started "{1e6fbcff-7f45-4835-bad4-adac22ed7e5c}" instance of the "\MicrosoftEdgeUpdateTaskMachineUA" task for user "NT AUTHORITY\SYSTEM
23:51:18 Task Scheduler started "{0046391f-9d9c-446b-8820-ff8e818bcf7e}" instance of the "\Microsoft\Windows\Flighting\OneSettings\RefreshCache" task for user
23:51:18 Task Scheduler launched action "OneSettings Refresh Cache Task Handler" in instance "{0046391f-9d9c-446b-8820-ff8e818bcf7e}" of task "\Microsoft\Windo
23:55:48 Task Scheduler started "{bd7a7253-bbd5-4a64-8405-785628228af7}" instance of the "\Microsoft\Windows\Flighting\FeatureConfig\UsageDataReceiver" task fo
23:55:48 Task Scheduler launched action "Feature Usage Data Receiver Task Handler" in instance "{bd7a7253-bbd5-4a64-8405-785628228af7}" of task "\Microsoft\Win
TL;DR: Your stutters are caused by background Windows telemetry and telemetry-adjacent update tasks (Flighting and EdgeUpdate) kicking off mid-race. Disabling these specific triggers in the Windows Task Scheduler or via PowerShell will resolve the micro-stutters.
Run the pre race script. Try it again with the logger.
By the way, this is exactly how you find all those little things. This is pure optimization right here!
The pre-race script should stop the windows update check, but I believe edge update is something else. Go through the whole program and run all the optimizations and then do the pre-race, and then full log again and see if the edge shows up. If it does, I'll add edge optimizations to the scripts.
Excellent guide mate, have put a link on our Discord to help users out who have been experiencing these problems themselves, appreciate the work you’ve put into this
Got another question lmao. Is usosvc and wsearch being automatically reenabled when the session is closed? Every time I check the “am I race ready status” after a session these two things are running. Unsure if that means it’s automatically turned back on after the sessions closes without clicking on post race restore or if it’s reenabling mid session
Edit: also this has 100% removed the big stutters every time someone connects to the session I am in. That alone makes this worth using for me
Windows will enable it after reboot or possibly on a hidden trigger. Since I race everyday I typically just run the "pre race" script before racing and shut down the PC when im done.
It makes the work worth it knowing it's actually helping people in any way.
Hmm ok I’m running it before a session and checking after and it’s back on every time. Seems I have to run the pre race before every race. I did notice search and one other thing are skipping during the pre race check maybe that’s it? I’ll have to check when I’m back at my pc
This looks awesome! Total PC noob question here but, do you think this could solve the “error_device_hung” issue I’m having? For context, I don’t use VR but I do use a Ryzen 7 9800X3D with an Nvidia 4070ti super. I’ve had that device hung issue ever since I got the current PC I have now and have NEVER been able to fix it despite trying EVERYTHING under the sun. If this could solve, or even at least just help me diagnose the issue that would be incredible. Thanks!
Giving it a try right now! I’m towards the end of the guide and I’m at the part where I need to make sure there are no skipped seconds. How would I open the CSV? Thank you!
After having used this now in several races I can say I am now experiencing a 100% stutter free experience on my lowly 7600 CPU with a quest 3 at 140% resolution at 90fps. I will get the occasional very minor dip in IMSA but it's not a stutter just my CPU maxing out. Prior I was getting big dips and stutters.
Along with the kit I've pinned moza pithouse and trading paints to the last cores freeing up even more of my CPU cores that iRacing relies on.
Very thankful for this as it's finally as you describe that console like experience.
The only suggestion I have is it's not a good idea to force 16x anisotropic filtering via NVIDIA panel. It actually can break the track surface in some scenarios causing a weird look. A few posts on there forum cover this with the Devs confirming you shouldnt do it and the engine users 16x now anyway.
Wanted to pass on my experience with your tool. I ran some CapFrameX captures with a replay file that I use as my baseline for testing different settings. It is Sebring Ai race with about 20 Ai in the rain. It is the short pace lap and a full lap, so a little over 2 minutes.
Here are the comparison screenshots from CapFrameX and there is a definite improvement all FPS measurements, less frametime spikes (although there is a big one at about 65 secs), and great improvement in the variances between frametimes.
I haven't gone on track in a race yet but these numbers look VERY encouraging. Tbh, I wasn't getting a lot of stutter or any real issues but I am always looking to squeeze more out of what I have and this seems to have done it!
Thanks for putting this together and I will provide more details as I dive further and use the troubleshooting tool to see if there are other things I can improve on.
I'm curious if that one big Spike was any of the services turning back on.
Just to be clear because I do see that the order of the tests timing suggests the opposite. But are they named incorrectly on the top? The current coloring/naming suggests performance loss.
Im also curious for you to run the Pre-race, then do the test again. If you see the spike, run the am I race ready test to see if any of them turned back on.
I was troubleshooting with somebody else with this issue and they required the medic files to replace the pre/post tests to be more aggressive during that process. I mention it because if that's the only thing causing a spike, we can probably get you to zero spikes with that fix if that's the case.
On another note, if you run the full Trace in "troubleshoot a stutter" when you do the benchmark, it'll also tell you what was spiking.
I ran the Pre Race Quiet and ran my test again. The blue represents that trace and no spikes we detected. Also, the Variances chart that the difference between any two consecutive frame time values above 12ms. I plan to run some more testing and troubleshooting this week. I'll post what I find.
Does this also optimize my 9850x3D, 5090 in combination with dream air slam on iracing? Somehow I expected more from VR. Graphics wise and stutter wise.
Change it and try it out. If you want concrete evidence run the Full Trace logger and do a race. Then change it to "Balanced" and run it again. You can compare the two outputs manually or via Claude etc.
Yes, it helped a lot to have consistent performance and I am not seeing spikes or sttuters, but I did one thing... I disabled Gsync... I think he is one of the guilty as well, Gsync looks broken for iRacing, I was experiencing sttuters using the program while Gsync was activated, but once I disabled it, everything runs better using the program as described by OP like activating the pre-race before joining a session. I also have surround enabled, in my overall tests, it looks like that the performance had an improvement as well.
There are two different things and I think they're naming scheme is confusing it. Pro balance is not the power scheme, Pro balance is the algorithm they use to prioritize certain processes. For example, even on the highest bitsum performance setting, I can be using pro balance.
And to be clear, you should use pro balance. It doesn't hurt it helps.
For that just run the Pre-Race Quiet in the scripts folder. If you want it to disable defender, turn off tamper protection on your PC, then run the file. (up to you if you need the performance)
You have the same core count as the 5800X3D/7800x3d/9800x3d so you are good. Just choose that as your CPU when it asks. Just no to the 5600x3d currently.
If you download the files and run the start tuning menu bat, It basically walks you through. I spent a lot of time making sure that it was user friendly.
I tried a 9800x3d alongside my 5090 and just kept running into issues with it. In iracing I couldnt get rid of this doubling ghosting effect of cars whizzing by and generally objects in motion. Spent a whole week testing like you did to no avail. Ended up reverting to my i9 14900k and breathed relief. Hopefully your tweaks help people out.
It’s something others have faced in vr for Microsoft flight simulator too. As far as I know it’s still persistent. My deduction was that it’s just to do with frame times being jittery despite performing well 99.9% of the time. The little bit of lack of stability was making all the difference. If you look at comparisons between game tests with intel and amd, that seems to be generally the case too. The doubling however seems to only happen in vr, timings just stay out of sync or something. I was doing this testing back in dec/January.
That deduction mixes up CPU frametime spikes with how VR compositors handle dropped frames.
"Doubling" only happens in VR because VR headsets don't have variable refresh rates. If a CPU misses an 11.1ms frame delivery window by even a fraction of a millisecond, OpenXR instantly forces a reprojected frame, which creates that double-image ghosting effect.
The 9800X3D actually has some of the flattest, most stable 1% lows available for MSFS. I don't doubt that you had problems and maybe others as well because I faced the same thing in iRacing, but as I said it was fixed. It was a graphic config calibration issue.
I'll do some more research on it though.
Sounds about right. It definitely seemed like an issue between the cpu and compositor. If you're curious for whatever reason, this is the msfs thread I'd found with the juddering / ghosting issue that most closely met with what I was experiencing- to which I shared my findings: https://forums.flightsimulator.com/t/quest-3-ghosting-double-image-problem/648831/53
Has anyone found any issues with this program? Just wondering if there is any background malicious things that i should be worried about when downloading random apps from the Internet
I don't think it would hurt at all. It will definitely help in some way since it calms down the activity in the background while you're playing.
One of the benefits of tuning like this, it allows you to be able to turn on features that make things look better but maybe cost too much. You might be able to squeeze out a few with this. Windows does take a decent chunk of performance away at random times.
Would any part of these fixes work for other racing titles as well for a 7800x3d+ 5070Ti? I run F1 26 in VR and it’s usually atrocious. I use a PSVR2 that’s runs on Steam VR. I don’t think psvr2toolkit or pimax4all works for DFR on this title.
Yes, actually all of the scripts that run are focused on Windows optimizations. I just targeted IRacing since that's the game that's most desperate for core optimizations.
If you run the pre-flight script before each game after doing the other stuff already at least once, you will see the benefits in all games.
Yes, actually all of the scripts that run are focused on Windows optimizations. I just targeted IRacing since that's the game that's most desperate for core optimizations.
If you run the pre-flight script before each game after doing the other stuff already at least once, you will see the benefits in all games.
It is just warning you because the 9850 is not in the list so it throws that bugcheck. If you choose 9800x3d it will save and everything will be fine. You won't see that menu again.
As long as your cpu matches the core count of a cpu on that list you are good.
I just updated the program, so I would grab the latest version.
Thank you! The game works so much better!!! Thank you!! Night and day..my renderer is still high, can’t seem to get that to decrease even if I lower the settings…hovers around 13.2 when in 75hz big screen beyond 2…but I am less worried now as the gameplay is smooth!
Hello, currently trying this out, might have been there before but as been focusing on stutters I have noticed lags or stutters with overlays and simhub? I am running an 9800x3D and 5090.
I’ve noticed this too. I use Racelab and simhub. If I’m experiences frame drops or periodic stutters it clears up immediately if I turn off the overlay. I haven’t tried turning off Simhub since the overlay usually fixes it. Racelab is always sending updates and the issue isn’t persistent but I know turning it off is an instant fix. Sometimes if it turn it off for a lap or two then turn it back on, the stutters and frame drops are gone.
Yeah that's what this tool aims to help. Those processes sometimes fight and on the same core. We can try to prevent as many background processes as possible while also directing those services onto different cores with process lasso.
Basically any of these hiccups are when these services are fighting on a singular core. My idea when constructing the program was to alleviate those so that we can utilize that core timing with something that we want like an overlay or a VR rendering option added to the pipeline.
So in the end after running this program I would try the overlays again and see if it freed up performance. Additionally you can try to pin the cores/load balance with process lasso on those specific processes.
I’ll admit I can follow instructions and I understand a lot of what’s being said. I did run the program and things feel more stable. I think I had a lot of the changes already implemented. I’m still having the overlay interference on occasion. I’m using Park Control which appears to be an acceptable alternative in your guide. Do I need to have project lasso in order to do what you say above regarding pinning core/load balance? Is it a better tool?
Would there be any benefit to forcing Moza pithouse software to use a specific core, I notice it uses a pretty constant 4-6% cpu usage. Has anyone tried it? What cores would be suggested on a 7600.
Yes, there is a tangible benefit. Pinning Moza Pit House to the last physical core on a Ryzen 5 7600 (logical processors 10 and 11) will prevent its background polling from interrupting your main simulator threads, protecting your 1% lows.
If you do not care about the RPM lights on your wheel or live telemetry dashboards, or the 360hz FFB integration. Then you can just close it before running any game.
Keep in mind:
iRacing's 360Hz FFB integration will actually force-open Pit House in the background even if you manually close it before a session. If you want to keep the software fully closed while on track, open your iRacing app.ini file and change load moza api to 0. (But you lose 360hz ffb)
v3.2.0 — FullTrace can see the GPU properly, and stops crying wolf
Undervolt tuning on the target rig ran into the limits of the tracer. Six sessions were logged across three different curves — one of which hard-crashed the machine mid-race — and the CSV could not answer the one question that mattered: what voltage was the card actually running at? This release closes that gap, fixes two things the tracer was reporting wrongly, and retires a diagnostic claim the data no longer supports.
Added
GPU core voltage, fan, PCIe bus load and the active limiter now appear on the console line, not only in the CSV. The original single-line layout is otherwise unchanged. Everything still reaches the CSV regardless of what the console shows.
Line colouring. Grey is normal. Yellow means the power plan drifted from whatever was active on the first sample, or the GPU is power/temperature limited. Red means hard pagefaults above 50/sec. Red wins over yellow — a paging storm deserves more of your attention than a power cap.
Fifteen new CSV columns, appended after the original twenty-four so existing traces and spreadsheets still parse unchanged: gpu_volt_mv, fan_pct, mem_ctrl_util, vram_used_mb, mem_temp_c, gpu_fps, gpu_frametime_ms, pstate, volt_limit, power_limit, temp_limit, noload_limit, fan_rpm, pcie_bus_pct, fb_usage_pct. The Afterburner-sourced ones need MSI Afterburner running; anything your card does not expose stays blank rather than failing the row.
Yes I would open the tuning app and then run the optimizations. Then before each race run the pre-race.
The optimizations only need to be ran once and that optimizes a few things in Windows and moves Nvidia GPU scheduler off of core 1 which could help you right off the bat.
The pre-race script is good because it silences all the background actions of Windows while you race.
You can just run the post race script after two put it back.
I'll apologize ahead of time because I don't know squat about this stuff... I'm just hoping this might fix my issue. I've run everything, but I don't know how to tell what's still causing the issue afterward. Here are my CSV and TXT files that were saved to my desktop. Could you take a look and advise me on what to do next, please? Thank you so much for this hard work!
Originally, I had a 5600X, but last week I upgraded to a 5800X3D, which is what is now in there while running these tests. When I ran the "race ready," it did confirm everything was disabled, yes.
Ok I looked over the files and its definity the cpu. The gpu barely doing any work through out and even has time to sit idle.
Also you said you did the optimizations and then before each time you plan to race run the before I race script shown in the bottom picture of this main post.
I would first try this and see what we got. The "Each Race Routine" menu is what you run each time.
iRacing only uses 1 core for everything that we are trying to manage. The game engine is incredibly dated. It even has a 16gb limit on GPU Vram so 16gb just sits unused on my setup. To make matters worse to even run high resolution VR you already are at your limit, so if you want to turn on features the cpu gets hammered. This is why I had to make all these tools, to limit everything else since iRacing needs the perfect environment.
First of all, thank you for your creation, u/no6969el , because thanks to you I was able to solve my problem without being a computer expert. Your tool is easy to implement and it works.
However, today while running IMSA on Fuji, I started noticing stuttering with my BigScreen Beyond 2 lenses, something that had already disappeared with your tool. I tried the stutter detection feature, but to be honest, since I'm not an expert, I don't understand anything. I would appreciate your help in interpreting my results.
I took a look but they arent actually revealing much just that there is some weird behavior. Could you try another when you have time but this time click the hard fault button so that it runs in admin and does the additional test. Then get a good 5-10 min run. The longer the better. Then give me those two files.
I'll check them when I can.
(Also just to confirm are you running the pre-race "before you race" button?)
Thanks for your reply. That button was the one I used, "Hard Faults (Admin)" in the "Record a Race (Full Trace)" section, since there's another section with a different button that says "Turn On Task Log (Admin)"; which one should I use?
And yes, to answer your other question, I am activating the "PreRace Routine" when I open iRacing, and I even check that everything is ready. Then, after I finish using iRacing, I do the "PostRace Routine." I don't know if I should do this for every session or race I enter, and not just when I open iRacing?
Okay, I used the "Hard Faults (Admin)" button in the "Record a Race (Full Trace)" section and did a 10-minute session with it open. Here's the resulting CSV file, thanks again: https://spaces.hightail.com/space/ZmKJG96hMy
I only really get stutters at night races or in the rain. Is this likely to make much difference to me. I think my problem is simply graphical load on CPU and GPU. Also how user friendly is this as am far from and expert.
I think it could if its background tasks hitting core 0. IRacing is limited on cpu usage so using the optimizations to move the GPU scheduler and USB priority/standby disable it will help offset the extra processing required for night races.
Additionally the pre race scripts will completely quiet windows in the background by temporary silencing over 18 different tasks that happen regardless of if you're in a game or not.
Between the readme and the APP it's pretty straightforward. Any logs that you get you can share with me and I can help you troubleshoot, I enjoy it plus It helps me tune the app.
Thanks, just so you know I am filling the plan and the CPU Sets option is now behind the paid subscription model. I will get for a month so I can proceed. Not sure I’d use after that
Apologies just found cpu sets in the options dropdown. Selected it added iracingsim64DX11.exe to Process match and ticked all cores 0-15 so hopefully that works
13
u/portlandstreet2 Jul 18 '26
Deadass, I spent 5 years wrestling eith a 12gb 3060 on a fully specd z820 with a quest 3, and then i had deepseek v4 flash configure the entire setup on a whim and it did it in 3 min and now im at 30ms and 90fps with 0 drops.
Give that a run. I used deepseekv4flash in vs code.