LazyBoot

Iirc, it should be the same process from either seat. Just do the command to take command of the display twice.

They are literally only showing it with VR hands in the video.

Someone did find a workaround...

There's already about thread about that... https://forum.dcs.world/topic/333485-altitude-button-does-not-engage/

There hasn't been an update yet... But soon™

That does make it sound like my theory is correct then, and it should really be in the ON position on a cold start.

Having taken a quick look at the IRL manual, the before engine start checklist only says to check/verify that the generator is set to ON. Which might suggest that it's really supposed to be left in the ON state.

Considering the limit is there for physical reasons, the limit will always be relative to sea level. But it was clearly enough of an issue since later versions of the lantirn pods have a much higher limits (for example the version the DCS Tomcat has)

I assume that's a placeholder SRS decided to use while waiting for for correct way to get added

Trying to go as fast as possible can often cause you to pitch out of the limits for the doppler system.

Are you trying to push the speed to the absolute limit? @LuseKofte

F-15 will also do that, as long as the newly selected steerpoint is a target point.

No, the current tpod does not have that feature. It should probably be available in one of the other pods that'll be coming later though.

while it's clearly still WIP, the IFF screen on the UFC did get included in the latest openbeta (though it does seem to be cosmetic only) and I'm also seeing that it doesn't seem to allow 0s on any digit for M3 currently.

I did have the decimal point in there, because that's how the jet itself fills out the scratchpad with the old frequency.

Radios won't accept frequencies entered with all 0s as decimals, which means you can't put back the old frequency that gets placed in your scratchpad if it was a whole number (like "253.000"). Anything ending in ".0" ".00" or ".000" just results in the error-flashing. And this applies to both radios.

Maybe it could be an idea to include an example of specifying a runway heading on the airbase points (F10 map markers) (and if there are any other missing options)

HRM mode will have a blind-spot in front due to how synthetic aperture scanning works. (It requires sideways motion relative to the radar to get the extra resolution you get from SAR scans) Use the normal ground mapping mode if you need to see in front of you.

You need to put the A at the end, not at the start. So like 1A, 2A, 3.A and so on

Are you letting go of the finger lifts after you've passed the detent?

you need to go through the ground crew menu

left ctrl + left shift + escape (repeat to move through the different modes, including hidden)

You do if you want to be able to see it in multiplayer.

The controls overlay (ctrl+enter) will also show a line where the ab zone starts.

Looking a bit more closely at it... It gets depressed if switching to the engineer seat (and probably happens with the gunner as well). So it's the AI that presses it and doesn't release it!