skywalker22

With this new @mbucchia's app, clarity is the main one. I can see now so clearly every where I look, it's outstanding. Even better then Reverb G2.

This is the path: C:\Program Files\OpenXR-Meta-Foveated @mbucchia can you also fix that on your website? thx

1. Hardware optimization: Wow, on a default setting of Meta foveated rendering app, I have constantly 45fps, which means smooth moving picture. GPU temp is not over 55degC at a use of up to 200W - MSI 4090 Suprim X). Oculus settings are 90Hz and 4704x2384. 2. App's features: what I was even more impressed, is the Clarity in the very center where my eyes are pointing, much, much better then before; my reference point are the top and bottom numbers for acquisition Cursor on the FCR). Now I can see both clearly, before I just couldn't. ps: I only change Turbo mode to 0. Thank you @mbucchia.

show us ur track

As said, that a normal behavior. I am sure you have trimmers bind to buttons (so digital inputs), in F-16 trimmers are analog potentiometers where you can trim way more precisely. Hint: use auto pilot for "fixing" roll thing, for Pitch (keep same pitch) or Attitude (fly horizontally), while keeping the left switch in the middle Attitude Hold.

New nice video, where is these possible to see even better:

A bit off topic... does anyone else have issues with Pro headset, when Win11 waking up from Sleep mode? Headset is not being recognized. I have to or restart headset, or just unplug and plug back in the Quest Link cable. I have my headset constantly connected with a USB-C cable (I also tried to connect into USB 2.0 port, same result). I also asked on the meta help forum, but I actually didn't get any solutiuon. Would just like to know if I am the only one with this kind of an issue.

Will this be a part of OpenXR Toolkit?

Track please, since I can land very simple, with no issue what so ever. If you have any, try to use rudder a bit, that's why it's there.

OpenXR is no magic app! With exploiting it's options you basically make the image worse on areas which are not so much effected by your eyes. So now the question is, if this bothers you or not? It did bother me, so I had to turn more or less all those options down, and there was practically no advantage compared to steamVR. Thats the truth. I still use OpenXR, since it is now natively supported by DCS, but it's just there, I don't use any of it's options any longer. Specially now when I went to Quest Pro.

Is it not working as it used to do. System target should be a hollow square, which never appears. And while in TMS, TMS right short should designate all into system targets which does not, although you can then with another presses on TMS Right, cycle between "system targets", which are still more like Track targets (full squares). f16-rcr_tws_track_to_sytem.trk

Sorry, I know what you mean now. In both RWS and TWS contacts act like in TWS. In RWS all the contacts which are seen from onboard FCR should be uncorrelated - which are not not. I would say is a bug, the FCR has again some bugs, like in TWS, TMS RIGHT on the stick to transition all track targets to system targets is not working. Will open a new topic for it.

That's all fine. Green and red contacts are from from Data link (AWACS or other doners), yellow are contacts from your onboard FCR.

Maybe it is turning (it is banked), and that's why there is no good signal from it. We did tests in the past, and there are glitches of awacs in DCS. Do not know how this is IRL.

How do you do these graphs @gortex?

check this out. f16-stuttering.trk

You can only lock to contacts which are "visible" with yout onboard FCR (fire control radar). Datalink contacts are from AWACS and/or, as @razo+r explained, contacts from other aircrafts

When missiles are involved: How will you hold 400+knots in a 1-circle fight? No one will go 2-circle against F-16, at least not anyone who knows what's all about. So we better start talking 1-circle fight and speeds up to 300knots (maybe a tad over), but most of the time speed between 200 and 300 knots. And now we are where? No where near what F-16 prefers, right? So no wonder why F/A-18 is out rating F-16, and without the paddles, since speeds are so low, that there are practically no Gs.

Awesome. Thx guys.

Hi, welcome I must say that, DCS required way more controls then MSFS. So a (proper) HOTAS is unfortunately a must. There is plenty written about all what there is available, check here. I started with Thrustmaster T16000M + TWCS throttle. I still have this same throttle among VKB`s Gunfighter mk3 joystick. About your issue, check the Options/Controls section, and click on Axis Assign button down bellow. Look for your Roll and Pitch, right mouse click on each and select Tune Combo Axis (you also have a button down bellow). In there you can check how each axis responds/works, and you can adjust accordingly if needed. I hope it helps a bit.

You should get a better hardware, that's not good enough

I was also wondering where those stutters come from. I thought that it might be connected with an aircraft (F-16, didn't try F/A-18), since there is no stutters with Mirage or Mig-21, which I also tried.

Turn ON the electronic signals, switch on your left - RF (Radio Frequency) Switch, by putting it up to Norm position, for radar to start working. About radar antenna, did you assign the controls for Antenna Elevation knobs, up and down? But before all that, turn on Fire Control Radar on the right console:

You mean purchasing Sinai? I think it is surely worth it, every penny. One of the best made maps for DCS. And will only get better, based on all what report here.

Read my post from an hour ago. Yes, it seems it does help. I have no more stutters as before, there are still some small stutters, depending from which angle I look down on the city and for how long as well. But its at least flyable now.