some1

Display port 2.1 is not a requirement for 4k high fps gameplay, because most high FPS monitors on the market support DSC compression, so even DP 1.4 can do 4k 240Hz.

The Elapsed Timer hand is missing, and the timer button on the bezel has no function, should be stop/reset/start. The seconds hand should be used by the timer and not the main clock. You can also check how it's done in other USAF aircraft in DCS, F-86, F-5, F-14 and F-16 have it modelled correctly.

The HSI should have two long lubber lines that extend from the top and from the bottom touching to the compass card. They should be visible from any angle. In DCS the marks are tiny, the same length as the short marks at 45 degrees. In fact the top mark is so small, it's invisible from the default seating position, making it impossible to tell what is your current heading precisely.

I wouldn't read too much into it. Sure, ED may have the final word and decide not to release two modules in a single patch, but none of the modules you've listed are ready for release. F-4 is not delayed because F-15, it's delayed because development took more time than HB initially estimated and now they tentatively declare "this winter". A-6 module is not even on the roadmap for 2024.

That's magnetic declination (aka magnetic variation). Compass deviation is from the interference from metal aircraft structure and other equipment surrounding the compass. It's unique to the aircraft, not mission date.

It's less about the cable itself and more about how much power can your motherboard or hub provide on the USB port.

Thanks. TACAN equipped aircraft should be able to receive DME readout by tuning to the channel corresponding to the ILS frequency (for example 40X for 110.30). Not every airport has DME combined with ILS, but most civilian airports do.

Bump. The game still does not support ILS DME, which means most ILS approaches on all new maps are badly coded and don't match real world charts, as most approaches in real world use ILS/DME. For example:

For flying at night i suggest reducing the brightness to 3/4th of the max, or half way. That will considerably reduce the halo effect from local dimming. Your eyes will adapt quickly.

VRR is not easy. To my knowledge, all headsets use backlight strobing to reduce persistence and improve the perception of fluid motion. And it's hard to get the VRR working together with strobing. Few monitors on the market offer such option, and they're not perfect implementations either.

IIRC you can use OpenXR toolkit to limit fps to any value you want. But regardless of that setting, what the game shows is not what the headset displays. The headset works at fixed refresh rate no matter what, it will simply skip or prolong display of each frame to match the refresh cycle.

Nah, it's equally bad in 2D, and not only with trackir, it doesn't even work properly with ED's own mouselook implementation. The mouselook automatically moves the camera further from center position simulating the pilot leaning in his seat. That also triggers the new helmet view. Which is even more preplexing that somebody on the team would claim: "YES, that's what I wanted". I've always though it's just a low priority bug, now I've learned that it's as intended, lol. On the CP/G station the head flickers in and out of view with the stock mouselook, it's not even consistently on or off: Look slightly further aft and it disappears again.

The gunsight again does not point to the correct place in the sky, this time the bullets fly in front of the target (too much lead). Tested all 3 gunsight options, they all seem the same. DCS 2.9 Target is flying a constant 3g turn, no evasive manoeuvres. GunsJF2.trk

Sure, I understand it is not really a high priority and ffb joysticks are hard to come by Some other developers provide a special option to toggle FFB, or detect if FFB is enabled in DCS options. Then disable stick repositioning.

Trimming the MB-339 changes the FFB stick forces, which is correct. But it also keeps moving the virtual stick in the cockpit just like with non-ffb joystick. The two trim implementations add up. This is not correct. With FFB enabled only the forces on the stick should change, but the virtual stick should not reposition by itself in the game, as long as the physical stick is firmly held in place. Basically the virtual stick position should be always synced to physical FFB stick.

To better illustrate the issue. How it should work: beacon at bearing 25, CDI centered when course set to 25. How it looks in MB-339: beacon at 25, CDI centered when set to 37 (25 + magnetic declination of the map)

In 2.9 that does does not work. This is what this thread is about.

That's what I said. Scs left activates WACQ.

If you lock a target with VACQ or HACQ, then after loosing lock the radar is back in ACM VACQ or HACQ respectively. But if you lock a target with WACQ or BST mode, then loosing radar lock kicks you out of ACM back to RWS. Seems inconsistent. ACM lock.trk

Pressing sensor control switch aft has no effect in ACM boresight. The only way to activate vertical scan now is to switch to ACM WACQ first. ACM vs.trk

It is still a problem in 2.9. Conditions in the attached track: 25k ft altitude, target is above me, closure rate is 300-400 kts. I fire four missiles between 7nm and 3nm and the radar is loosing lock every single time. https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104575/aim-7-sparrow/ It says: "The versatile Sparrow has all-weather, all-altitude operational capability and can attack high-performance aircraft and missiles from any direction." While in DCS Hornet it's effectively a front-aspect only weapon. And pray that the target won't make a turn. HornetSparrow.trk

Fixed, thanks!

On a Quest Pro, the dots look way, way oversized. And that's with resolution cranked to the max and PD 1.2 in DCS. Also the ejected crew falling on parachutes are given exactly the same size dots as the whole aircraft. Very confusing. 20 nm, I don't even need a radar to spot targets: 10 nm, dots are the size of a building. 5 nm, like holes in the sky. 4nm targets.... what targets? At this distance the dots turn off in an instant, and we're back to regular DCS spotting. 1.5nm, well, now you can see them again. Sort of. If you don't blink.

They are the same bases and use the same detent mechanism. Both send buttons when moving from idle to cutoff position, it's easy to assign them to shut down or start the engine. The only reason you see people complaining now, is because F-15E has a unique startup procedure that requires the pilot to pull finger lifts without moving the throttle, and winwing won't register that, as the fingerlifts are purely mechanical locks. But AFAIK it's the same with other throttle on the market.

Make sure you activate wired link and not air link in the headset. Also you can perform USB diagnostics test in the Oculus desktop app, under Devices tab.