MagsMagsen

It doesn't make any sense from a physics perspective that tracking range is inferior to reliable detection range. STT = lots of energy and frequent returns on a specific target. I also doubt that any fighter fire control radars will ever stop the pilot from _attempting_ a track/lock on a detected target. It would be, tactically, immensely disadvantageous. Also, the fire control radar doesn't know everything. The pilot may have radio information/visual on a contact and may want to attempt a lock because they know the radar should be able to pick it up despite not having a scan echo yet. I'm very sceptical that fighter fire control radars won't allow the pilot to attempt a lock in _any_ point in space, despite not having a detected target. A detected return should not be a requirement for an _attempt_ to lock/track. Any such limitations would put the pilot at tactical disadvantage in many situations such as brief notches, where the pilot _knows_ the target is still there, and wants to force locking attempts in that volume of space.

People seem to confuse WMRP with WMR4SVR. They are not the same thing, right? Personally I only ever get a smooth experience with OpenXR Motion Smoothing on. Amazing stuff! With Motion Smoothing turned off I get a juddery experience, even at 60-70 fps. Does this mean it's alternating between 45 and 90 FPS? Or what does it mean? I agree with previous comments that OpenXR needs a setting for us to LOCK (limit) the framerate to 45 even when we have Motion Smoothing turned off.

I agree. Before joining Master Arms my DCS life was dull. Now I'm doing carrier quals, basic quals, talking to human ATC like a boss and droppin JDAMs, droppin JDAMs. Can't complain.