coolts

It shouldn't be too difficult. Query CPU ID. Compare to known CPU list, and retrieve number of performance cores expected. Assign DCS threads to performance cores. Make tea.

That looks to me like its not differentiating performance cores and efficiency cores. 2024-04-04 07:42:54.403 INFO EDCORE (Main): logical cores with efficiency class 1: {0, 1} and... 2024-04-04 07:42:54.403 INFO EDCORE (Main): logical cores with performance class 1: {0, 1} A 12700k has 8 performance cores, (0-7) and 4 efficiency cores, (8-11) This looks to me like DCS.exe is assigning its threads to any old core it likes and its throwing logical cores in the mix. 2024-04-04 07:42:54.403 INFO EDCORE (Main): common cores: {4, 5, 6, 7, 10, 11, 14, 15} 2024-04-04 07:42:54.403 INFO EDCORE (Main): render cores: {8, 9, 12, 13, 0, 1, 2, 3} 2024-04-04 07:42:54.403 INFO EDCORE (Main): IO cores: {16, 17, 18, 19} These 3 main tasks need locking to cores 0-7 in your case, not 4-19

ED need to implement some code that checks the number of performance cores on the CPU then ties their processes to those at runtime. It would be nice if the 'game mode' in windows 11 did that for nominated apps. That would be a useful use of the words 'game' and 'mode' to me, unlike whatever it actually does.

Forget core parking. See my post here to fix till ED patch it with a simple desktop shortcut edit. It's been broken since MT was released however so in the mean time unless you want to die of old age waiting...

This is for ED to patch, not Meta. I'm no Zuk fan, but there is a workaround. Use the Quest as god intended, wirelessly. Honestly, you wont go back to having a cable dangling over your shoulder*. *(once you've spent a month faffing with bit rates, researching codecs and routers and wishing you'd bought a pimax).

It's on ED to fix their openxr implementation. With the move away from open beta to predictable, slower releases, there probably won't be a hotfix. What we lose in agility, we hopefully gain in stable patches going forward. In the meantime, ditch the cable or use the janky steam runtime.

See my post here for how to fix this until ED patch it.

Right, I've sorted it once and for all. If ED cant be bothered program for modern CPU's that have been out for 3 years, then we have to do it ourselves. My i9 has 16 cores. 8 of them proper cores and 8 of them comedy "efficient cores". They are labelled 0-15. 0-7 are the proper "performance cores". For some INSANE reason, DCS LOVES core 8. It will shuffle to core 8 every time and performance tanks, hence the 'untick core 8' trick. Create a desktop shortcut to the DCS MT executable. Using this site, selecting only cores 0-7 gives a HEX mask of "0x00000000000000FF" https://bitsum.com/tools/cpu-affinity-calculator/ We only need the last bit. "FF". Edit the shortcut and add /affinity FF So something like.. cmd.exe /c start "DCS" /affinity FF "c:\whereveryourexelives" Once DCS is running you can alt-tab and check CPU affinity in task manager. Only 0-7 are now ticked. FIXED!! Come on ED. Please sort this out. Its not rocket science.

Why am still having to disable core 8 in 2024? Bought a quest 3 and was faffing with bitrates and dlss to fix stuttering and thought "hang on a minute". Headset off, task manager, details, core affinity, uncheck core 8... Smooth. Come on ED, sort it out.

Now there's no beta, there are no hotfixes. Stable updates mean predictable dev cycles. Let's just use vr desktop till its fixed. My WiFi is crap so I bought a d-link vr bridge usb adaptor. It's decent.

Use airlink, virtual desktop with fast WiFi. Ditch the cables. Just set mine up. Loaded msfs and dcs and blown away. Miles better than G2 with its microscopic sweet spot. I can look around by using my eyes! No need to do the G2 head swivel just to check my mfds. G2 on ebay on Monday. I loved it, but its been annoying me for ages with the horrible fresnel lenses and steaming up every damn time. I've seen less steam out of a bloody kettle.

I've not checked pre planned waypoint TOT's. It's that a thing in DCS as it is in BMS? Using the F10 map is a PITA, especially in VR.

Playing DCS Liberation, all waypoint TOT's are given relative to Misson start. I can see this counter in the F10 map, but nowhere else in cockpit. What have I missed? Something obvious I'd wager.

Jesus H Christ. 6 pages on this and still no answer. Just a lot of horse whispering about what "works for me". Lets hope ED make boresighting a tickbox option. In VR it's a pain in the arse. From a hot start its fine so it's obviously not necessary in game.

I tried a few time last night and i cant get it right in VR. Aim is waaaaaaaaaaaaaaaay off. So i'm stuck with hot starts in VR. I'm sure this is something that will be sorted. The boresighted aim is always high and to the left, which would correspond to the sight being rendered in the correct (right) eye in VR and centrally in 2d. The game is boresighting assuming 2d so when you actually do it with right eye only, its parallaxing (collimating?) the opposite way. Probably .