MiiCh

a quick experiment i did yesterday with opentrack i programmed the input for oculus, and the output as mouse, i inverted the yaw and pitch axes and adjusted the sensitivity. the idea is a mouse that pulls the cursor in the opposite direction to cancel the dcs one. when entering dcs, already in the cockpit i activate it with the shortcut programmed in opentrack and when moving my head the cursor starts to move for a brief moment, until it stops, shaking. it works! but dcs adjusts a dead zone or reduces the sensitivity of the oculus tracking when it detects that the movement is minimal to increase the precision of the cursor. outside of dcs, on the desktop, without inverting the axes, the cursor follows our movements perfectly centered. DCS does something... The next step would be to configure a phone with Freepie to act as an external OpenTrack sensor that DCS can't see, and stick it to my glasses. But... the DCS cursor is not linear, it will be impossible to adjust OpenTrack to override it. I don't know, maybe one day when I'm really bored I'll try again. Disappointing

a quick experiment i did yesterday with opentrack i programmed the input for oculus, and the output as mouse, i inverted the yaw and pitch axes and adjusted the sensitivity. the idea is a mouse that pulls the cursor in the opposite direction to cancel the dcs one. when entering dcs, already in the cockpit i activate it with the shortcut programmed in opentrack and when moving my head the cursor starts to move for a brief moment, until it stops, shaking. it works! but dcs adjusts a dead zone or reduces the sensitivity of the oculus tracking when it detects that the movement is minimal to increase the precision of the cursor. outside of dcs, on the desktop, without inverting the axes, the cursor follows our movements perfectly centered. DCS does something... The next step would be to configure a phone with Freepie to act as an external OpenTrack sensor that DCS can't see, and stick it to my glasses. But... the DCS cursor is not linear, it will be impossible to adjust OpenTrack to override it. I don't know, maybe one day when I'm really bored I'll try again. Disappointing

When I read this thread, I had a question... what happens with the call parameters that we have in our shortcut? I mean things like --force_openxr or --force_oculus? I suppose that the launcher passes them to the final program, so I can see that --force_enable_vr works.

In the VR tab add the option 'HMD Cursor On/Off' or something like that. It is enabled by default but those who do not want it can easily disable it. Those who use it would continue without problems. I have already posted this in another thread. The option is included in the VR tab and does not affect head tracking.

In the VR tab add the option 'HMD Cursor On/Off' or something like that. It is activated by default but those who do not want it can easily deactivate it. I understand that there are many people who use the cursor together with the hotas to click, but there are controls that are better activated with the mouse (the wheel). I suppose it depends on which plane. Looking at the switch to activate it makes you lose the vision of the outside, and after that you have to correct the course. Working with the landing gear of my Polikarpov I16 is very fun. I know I can program a couple of buttons for that, but in the end you put everything in the hotas, that's what I try to avoid. So.... Why a clickable cockpit?

In principle, the utility of dissociating the HMD from the cursor movement seems simple to implement, but if it were this way I don't see why the developer refuses to do it, especially when there are so many people asking for it. There must be good reasons for not doing it. Otherwise, why are they ignoring us? Thank you very much for answering

+1

As far as I can see, this has been requested for a long time and there are several threads talking about it. I ask the developers to at least explain why they don't implement it. If we knew why, perhaps we could find a solution.

+1

+1