Mors

Good day to you all, somewhat rehashing what I stated to DCS support here; the Ka50iii module appears to be breaking head tracking whilst in cockpit on my system. No other module seems to have the same issue, however, when it breaks in the Ka50 all other modules are affected and tracking only restarts after quitting to the main menu. System: 3080, i12700KF, 32GB Ram, dedicated 2Tb SSD After the purchase of the Ka50 module I started having this issue so did the following as I thought it was hardware/system related initially; • Clean system install (dedicated rig) all drives to zero • Clean DCS install • Clean module install • Slow check of all files What happens? Jump into a mission with the Ka50 and head tracking (any flavour but for this example let's use genuine TrackIR) works fine from the get-go. But, after a random duration between 10 to 40 minutes the head tracking will cease recognising inputs while in the cockpit and the view will fix in the forward position before slowly rotating until the view is directly behind. Why isn't it my hardware? It can't be the hardware. TrackIR still functions outside of the game, in the game TrackIR inputs are recognised in both the Controls Dialog screen (Axis Tune shows the inputs as working fully). TrackIR is still recognised in the ESCAPE menu screen (Choose coalition red/ blue etc), this is a screen where the view is external but head movements are mirrored on screen (you can look around the scenery). Also, TrackIR works perfectly when first entering the cockpit for a period of time. Additionally; • All my USBs are set not to sleep. • TrackIR app and DCS given priority. • I've deleted the Saved Games folder, more than once. What happens when it 'happens'? View will freeze, followed by a slow rotate until looking behind in the cockpit. No head movement inputs are recognised in the cockpit. Swapping to any other aircraft doesn't fix the issue, it persists across all modules. How do I fix it? Currently, quitting to the main menu will restore tracking across the modules/ aircraft (as far as I've tested). I can jump into a Kiowa and fly for an hour or so no problems, but as soon as I try the Ka50 the problem will reappear after a short period and head tracking will freeze up in the cockpit. Questions 1. Has anyone else encountered anything similar? 2. Is there a fix? 3. Is there any file that can be examined to reveal the root of the problem?

I can only speak from my own experience (and the many others with superior systems still facing issues). A 32GB ram, i12700KF, 3080Ti with the game installed on a dedicated 2tb SSD should be able to run VR seamlessly, with good graphics settings just as it does in MSFS or IL2. Sadly, the reality is it doesn't and no amount of 'get gooder' system wise seems to make much of a dent. You have to turn everything down until the landscape resembles minecraft and still it will lag, jitter and tear in my Q3. Just trying to inject a little realism. It works great in 2D and, with head tracking, will provide a far less frustrating and much more enjoyable experience.

In Quest 3 it still looks terrible and no system or headset, as far as I can tell, will serve a crisp, sharp, jitter free experience at any resolution with VR. Stick to 2D, it wasn't really designed with VR in mind.

Ka-50iii is, for me, triggering issues with headtracking. All versions are affected; OpenTrack, Beam Eye Tracker and TrackIR. Head tracking ceases to work after several minutes IN THE COCKPIT, but inputs are accepted and recognised in the controls dialog (axis tune) AND inputs are accepted at the ESC screen (choose coalition, choose red, choose blue etc.) If I move my head in either of the dialogs the movement is recognised and the relevant input displayed or the relevant head movement mirrored (in the case of the ESC dialog screen). This proves that it is not my hardware, or a setting, or a USB hub that is causing an issue but something in the Ka-50 module itself. The problem is not evident when flying other modules; Huey or Kiowa Warrior, ONLY when I jump into the Ka50 - however, once it's manifests itself it remains in either module whilst in the current mission. Quitting the mission, returning to the main menu and restarting the mission clears the error. Has anyone any advice or seen similar issues? DCS support itself wasn't too helpful, deflecting the problem onto local system settings which it clearly cannot be – it still all works IN-GAME but not IN-COCKPIT. Hoping I can get this fixed.