some1

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.

The runway heading is 93 degrees true, and that's what the GPS is showing. Your other cockpit instruments and maps show 87 which is magnetic runway heading. The real GNS430 can be switched between true and magnetic north, don't know if you can do that with the one in DCS.

I think it's just some people less susceptible to visual stutter. A headset is like a monitor with fixed refresh rate (vsync on). If it is set to 90Hz, then it cannot display 85 fps, 67 fps, or any other number generated by the game below 90. If it doesn't get a new frame every 1/90th of a second, it will display the previous frame for the next refresh cycle, another 1/90th second. So it's dropping from 90 to 45 and back to 90 fps, the result is visible stutter. Some people claim that locking the game to 45 fps fixes it, but then you're looking at low framerate all the time. Maybe that removes the stutter, but it isn't very smooth either.

Sparrow may not want to launch even if we are within all launch parameters and shoot cue is on, usually if the target is manoeuvring. In the attached track the first missile launched without issues, but for the second one I had to press the launch button 4 times before it decided to leave the rail. BTW the Razbam F-15 manual claims the dot needs to be inside ASE for the triangle shoot cue to appear, but that doesn't seem to be the requirement in game. No launch situation: f15LA.trk

Are you sure you did not mix the units? Your fibre is probably 300Mbs, not 300MBs, and your router is probably 5GHz Wifi, not 5Gb transfer. And for these parameters Cat6 cable is more than enough.

Yep, gyrocompass is what you find on a ship, aircraft have gyromagnetic compass.

I don't think there's an easy way to change that in the F-15E, maybe if you set the magvar to zero in the INS? If that's even possible. Most of western aviation works on magnetic bearings, ATC reliance on true north everywhere is one of DCS quirks. The only system capable of sensing true north in an aircraft is the INS, and most smaller aircraft don't have one, even smaller airliners. Satellite systems can't tell aircraft heading, they can only derive aircraft ground track from position changes, but that's not the aircraft heading if there's any wind involved. Heading data is fed into the GPS system, not the other way round. So the magnetic compass is not going away any time soon, although the information presented to the pilot may change in the future.

Nvidia frame generation requires DX12, given that DCS is still DX11 and is being converted to Vulkan, I doubt we'll see that in DCS any time soon.

4090 and 7800X3D.

They can't because real western pilots rarely have to deal with true bearings. Their charts use magnetic north, runways are referenced by magnetic north, VOR and TACAN use magnetic north etc. At least most of the time. DCS map is skewed by its Russian origins, where use of true north in aviation is more frequent. Same with using QFE instead of QNH by ATC.