sleighzy

This log is just from the launcher and not a complete boot into DCS. This log is also from the DCS in bin-mt and not bin. This post has also been solved and you're responding to something from 4 months ago. You should raise your own new post if you're having issues.

Humble apologies, I misread that as referring to the video on core parking, vs. your Process Lasso one I see as a link now. Needed more coffee.

Any reason why you're using OpenComposite? DCS is a native OpenXR game so shouldn't be used with that. And yes, Pimax should ideally be used with either the PimaxPlay OpenXR runtime or Mbucchia's Pimax runtime and not SteamVR.

Reinstalling DCS is hardly ever the option. Please provide the information that MAXsenna requested along with a screenshot of the exact error.

Can you please attach your DCS log file for when this occurs again. The log file will get overwritten each time you start DCS so make sure to grab it first.

@Furiz Can you also attach your DCS log file after replicating this issue.

Couple of things from your log file: You have core parking enabled. Use software like ParkControl https://bitsum.com/parkcontrol/ (or there is instructions here for doing via the registry: https://www.dannymoran.com/windows-cpu-core-parking) Secondly, the stutter log file contains the following which is spammed through the startup and not consistent with the other log, don't know if they were from different missions, or something else going on: 2025-09-30 22:12:54.792 INFO LUA-MISSIONGENERATOR (Main): loadMissionNodes: "missionNodes" 2025-09-30 22:12:54.793 INFO LUA-MISSIONGENERATOR (Main): loadMissionNodes: 1 : "1-SW-Gali-1" 2025-09-30 22:12:54.793 INFO LUA-MISSIONGENERATOR (Main): redTemplates: "Red Offensive - Large 1" 2025-09-30 22:12:54.793 INFO LUA-MISSIONGENERATOR (Main): redTemplates: "Red Defensive - Large 1" 2025-09-30 22:12:54.793 INFO LUA-MISSIONGENERATOR (Main): redTemplates: "Red Offensive - Large 2" Your log file shows two Razer Wolverine V2 Pro 2.4 being connected. Is that correct, 2 of them? EDIT: I'm assuming so as I notice now the UUIDs for them are one digit different. I'd recommend trying without all those peripherals connected, ie. the controllers and the Razer Tartarus V2 gamepad. Just strip it right back to basics. If you also have the world's most basic mouse try that as well. It may be that there is a bunch of I/O stuff happening. Might not be, but can at least rule it all out. Test over time to see if it does make a change then slowly reintroduce them again to see what happens. This is the full list of stuff connected, thought maybe a mouse would have shown up unless I overlooked it. 025-09-30 22:17:29.596 INFO INPUT (Main): created [Keyboard] 2025-09-30 22:17:29.597 INFO INPUT (Main): created [CH PRO THROTTLE USB ] with full id [CH PRO THROTTLE USB {2796EE60-F354-11ef-8001-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.629 INFO INPUT (Main): created [Razer Wolverine V2 Pro 2.4] with full id [Razer Wolverine V2 Pro 2.4 {B4B0A250-F43A-11ef-8001-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.630 INFO INPUT (Main): created [Razer Wolverine V2 Pro 2.4] with full id [Razer Wolverine V2 Pro 2.4 {B4B0A250-F43A-11ef-8002-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.630 INFO INPUT (Main): created [Joystick (Razer Tartarus V2)] with full id [Joystick (Razer Tartarus V2) {7ABE3B90-F352-11ef-800B-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.633 INFO INPUT (Main): created [CH FIGHTERSTICK USB ] with full id [CH FIGHTERSTICK USB {2796EE60-F354-11ef-8002-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.633 INFO INPUT (Main): created [T-Rudder] with full id [T-Rudder {AB553AC0-859B-11f0-8001-444553540000}], ForceFeedBack: no 2025-09-30 22:17:29.648 INFO INPUT (Main): created [TrackIR]

Can you drop your DCS log file in here in case there's anything in there. In case of a Windows issue open a command prompt as administrator, run the below two commands separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow

It doesn't actually disable them, quite the opposite. DCS determines which cores are what and puts them in specific pools. E-cores it uses for I/O stuff. The issue with parked cores is that Windows will put cores to sleep until workload is put on them and then wakes them up, does the stuff, and then can park them again afterwards when the load drops off. The problem with this is that it constantly parks and unparks (sleep/wakeup) as load comes on and off so you get stutters while that is happening. Unparking them means they're running at full power and don't go to sleep.

Not running as admin is the key, most definitely when using Winwing stuff. No clue as to why Winwing causes things to freak out when running as admin, it's still a mystery.

Not sure what those sources are, may be from years ago, but definitely do not run as admin. It can cause issues reading/writing files, and is frequently the cause of mass stuttering and pauses when used with Winwing MFDs. Yeah I think years ago it was spread that this was the way to run DCS as it gave higher priority / power management to the game thread and helped with performance. Don’t know if that was just bs but it isn’t needed and shouldn’t be done now.

Does this occur on Single Player as well, or only multiplayer? Does this only occur when moving your mouse? In the case of the mouse drop the polling rate of your mouse to below 500. You also have Winwing MFDs. Can you ensure that you aren't running DCS as administrator. You can confirm this by right-clicking on both your DCS shortcut, and your DCS.exe file, and after selecting Properties check under the Compatibility tab to ensure that "Run as administrator" is not ticked. You're also running DCS from the bin-mt directory. Run it from bin instead. They're both multithreaded and bin-mt will be removed in the future. You also appear to have kneeboard files with errors, mods? Remove / fix those as well. 2025-09-30 14:50:43.264 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/1.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/1.lua"]:17: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.264 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-02.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-02.lua"]:18: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.265 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-03.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-03.lua"]:12: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.266 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-04.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-04.lua"]:19: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.266 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-05.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-05.lua"]:20: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.267 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-06.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-06.lua"]:16: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.267 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-07.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-07.lua"]:12: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.268 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-08.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-08.lua"]:19: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.269 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-09.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-09.lua"]:9: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.269 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-10.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-10.lua"]:9: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.270 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-11.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-11.lua"]:9: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.270 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-12.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-12.lua"]:9: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.271 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-13.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-13.lua"]:9: attempt to index global 'mdc' (a nil value). 2025-09-30 14:50:43.271 ERROR Lua::Config (Main): load error C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-14.lua:[string "C:\Users\uluka\Saved Games\DCS\KNEEBOARD/2-14.lua"]:9: attempt to index global 'mdc' (a nil value). Have you also additionally tried without all your other peripherals plugged in, i.e. just running vanilla without head-tracking, mfds, etc. to rule out any issues with those?

Put all the mods back in in one go. It hasn’t been confirmed that it was even a mod that did this, which it shouldn’t. If it breaks with the mods then take them back out to confirm. Like I said, there’s other stuff in Saved Games including auth stuff.

This only (or typically) occurs when moving the mouse? Might be experiencing the mouse polling issue that some users still get with updates.... Recommend ruling it out at least by dropping the polling rate in your mouse software to below 1000, try 500 and even 250 or 125 to see if it changes anything.

Drop your DCS log file here.

Some auth data is stored in Saved Games.

This post is over 6 years old, and the last response over 4 years old. If you are experiencing issues then raise a post of your own and attach your DCS log file.

Delete your C:\Users\username\Saved Games\DCS\launcher.sqlite3 file and then start DCS again. Failing that rename your Saved Games\DCS folder to DCS.old (so you can copy back your bindings from Config\Input). Deleting the launcher.sqlite3 should fix it though.

Did you try with the VPN, which one did you use in the end, same problem? Can you drop a log when using the VPN.

Another user experienced same issue with SteamVR and Quest Pro, I passed on this info re: SteamVR beta you posted, totally fixed it.

DLSS Swapper is good for updating the DLSS dll version. You can set both the preset and also remove DLSS from the HUD/MFDs to remove ghosting from those by adding the below to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn't already exist). DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Can you please attach the actual log files from the bad run. The link you posted isn't even https and doesn't appear to be valid. For the ones from today we're after a log file and not a track file.

Try deleting the Saved Games\DCS\launcher.sqlite3 file first. If it still errors then rename Saved Games\DCS to DCS.old. Rename not delete so that you can copy back your bindings from the Config\Input folder.

Attach your current DCS log file in case something shows up. Attach another log after replicating the issue as the logs get overwritten each time.

Mostly looks fine. There are a couple of blips, but I'm assuming that the dcs log file and the CSV file are for two different runs? Was curious if showed up in log for matching timestamps. I've attached a couple of screenshots from blips. The blips coincide with high App CPU timings as well. I noticed you're running Through The Inferno for this, so possibly it's just loading a bunch of stuff in, or scripts, at the time which are triggering this. I see you're running both Quad-Views-Foveated and the OpenXR Toolkit. Do you have Turbo mode enabled in either of those? Turbo mode will throw off frame timings (it'd skew the numbers in this csv report as well). Quad-Views-Foveated has it on by default...except for SteamVR which you're currently using. Overall though looked ok. How's the "feel" in general when you play? I wouldn't get too hung up on a blip (.1% frametime if this is what it's based on) if the game is smooth and you're just chasing a number which is an outlier (especially if due to to something like TTI). EDIT: I don't use fpsVR so can't comment as to what it displays to you, or how it calculates it's numbers.