majapahit

Check your Windows Settings / Mixed Reality / maybe you switched your headset mic off

Have Mig21B in trial, just looked default keys bindings give 4x ARU, of which 2x ARU orange it's just there, it's DCS (error)

Never mind, lxsapper in this thread already said DCS F14B pilot/RIO separation interferes with functions list. Got your files, great sample.

Well done. If only you tried this on the Tomcat 14B gazillion commands pilot/RIO etc, bought it, only take off and trapping, never got to the radar or weapons, too many commands.

you have to read and know TARGET_SCRIPT_EDITOR_basics.pdf compare a sample script file with to content of this PDF and figure it out, looks horribly complex, but it's just a bad scripting language :)

There is no default LSHIFT+V I think. What exactly is your 'auto set the baro'? That rotating the baro knob right?

If someone says "set the baro" I just mentoin how I dial in field baro, but you're maybe referring to AP BARO? Whatever. Of course this is about having problems with his BARO/RDR altimeter switch for HUD, and mine works no problem.

I use Baro set and Radar Alt warning straight to TMWH ENG OPER buttons (Up off Dwn). Spawn > RadarAltwarning to 1 tick above Off (else Radar Alt don't work) > set Baro alt to airport < good to go.

3080ti, here too they say it will sell for 350 USD and use 99 Watts

Don't use the GUI editor, or only use GUI editor for exporting script, which is a horrible way, you have to learn the TARGET scripting, and call a TARGET script file thru the TARGET GUI, amazingly the TARGET scripteditor cannot use command line calls, is why. Attached my - cleaned - DX setup files, you can edit DX120_DCS.tmc, so to not pass specific DX but to pass TARGET Commands (I do that for F18 autopilot macro on the TMWH 3-way autopilot toggle) CLEANED DX120 DCS TMWH.ZIP

By default in any mapkey .tmc file, any button not defined simply passes thru. Then again find/use the "120 DX" definitions target template and all button/switch position will be triggered in the default DCS controls definitions which improves your TMWH a lot.

have you renamed/backup your saved games settings folder, DCS rebuild a new one and see if this disappears. could be old version key definitions file/corrupted. your bindings revert to defaults.

Someone mentioned Vive foam fits

no problem here

This is too obvious and confirmed. This is not just a bug, this is design versus other companies specs. It's the same level of problem in SATAL where FCS F15 is the killer toy plane - that I refuse to fly but will get you easy wins - but it's even more complicated because red team / F16 / F14 is done by out of house coders. I am too busy rally driving now.

No track, go on Growling Sidewinder when busy (often). Watch for an E2 signal (half way Vaziani), have 4 blue in between and four red coming in, F14, F16, J11. U need ground cover when F14's are high, all red use TWS with mostly IR's now, there's the rare newbie but most are not, get yourself from BVR <20nm to low alt range ACM <10nm so there is merge, and try to do your locks. I imagine it even could be DCS coding is trying to follow high fidelity realism from the technical side of what the F18 radar might be, but that's the wrong way around when the operational brief should be 'it should lock and keep locked as seems realistic' and no F18 squad would be flying with a radar that does not lock the right targets that's right around u. Don't follow the - hypothetical - tech, target the results/specs that can be expected from a multi million USD USAF jet that needs to fight ruskies, F16, F14 and J11. In DCS mind you, where the opponents are different companies who can do whatever they want.

It's the problem in PVP MP. I am sure F16 and F14 don't have these problems. These now have the way superior radar and the upper hand in MP, they can TWS u from 25nm and fire while you steer your F18 through a valley and they will keep you locked especially with a working E2 assisting them. The other way around - nope, nothing, no such thing, no lock, lost lock, continuously lose locks, friendly locks in the way all the time 15-45nm, can't lock after merge when at visual limit, only can lock with helmet close visual, it's retarded.

For the 'Reverb hurts my nose' problem and nothing sticking to the nose rubber, I now use these white circular cotton wool makeup removal pads that your wife or sister uses, these fit right in, perhaps use two, soft, no more nose problem.

It's bloody horrible I stopped flying it. Dirt Rally 2.0 is a lot more fun.

With a VR goggle the MPCD is always in view

I used to switch half flaps for corner rate, but DCS changed (prob fixed) the ECS and that aint workin anymore.

FFB Settings in controls setup?

Think last update optimized VR from worse, back to steady and 45FPS (45-60), was quite horrible last few weeks in MP servers.

woops, think that was with different goggles.

prob helps if you run a lower end system