Lymark

Given there's no mention of NVG in the manual, nor any other keybind besides Visor/NVG toggle, I bet it's one of those missing basic features of the early access product.

I guess my advice is more useful for PVP environment then. Most PVP servers out there usually require less than 200nm of travel to the frontline(~15mins), and they have a pretty straightforward mission design as well as good SAM coverage/Combined Arms allowed. If long-haul flights are a common occurrence on the server that you play on, then I'd suggest planning your sortie before you even start your engine. Open up the F10 map, see where the actions are, avoid unknown/risky areas, and setup waypoints on friendly air defenses so you know where to bug out to when crap hits the fan. Maybe even place a couple of sam sites of your own If allowed. Having a good prep would definitely help not getting 'ganked' from behind, I can't remember the last time such a thing has happened to me even in a hardcore PVP server. #Edit: Basically what the comment above(falcon_120) said.

It's tricky, but you just gotta maintain your SA via TEWS, F10 map(If allowed), spam bogey dope, IFF/NCTR, and most importantly, good radar management. The few PVP servers that I've been playing on have avoided having the same airframe on both sides, so that also helps quite a bit. If you feel like you're losing SA, bug out and reset. Having a WSO helps a lot as well. Thus far, my main concern is the good flanker pilots who never turn on their radar and employ their ETs via IRST. Luckily, good flanker pilots are extinct in the wild, esp. in one of those 'fast-paced' PVP servers lol.

The part that said the Lua script can't be edited has a yellow symbol next to it.

According to the manual, altering the lua file is not possible at the moment.

I'm gonna take a wild guess here, but I feel like it has something to do with losing a lock while in TWS mode. I had 3 PVP sorties earlier and encountered this exact bug on every single flight when I was about to engage people, exclusively using TWS mode. So, I decided to stick with STT only and I was finally able to unload all my missiles and RTB for the 1st time without the bug.

Sorry for stealing OP's post, but I sorta have a related question.... How do you guys tell apart whether a contact is friendly or hostile? The manual states that a diamond indicates a low confidence AAI return and a circle means a high confidence return. But it doesn't explain whether the said return is friendly or foe. Am I supposed to ID them via other means(e.g. NTCR, F10 map, bogey dope) until certain feature(s) is implemented? Or, am I missing something about this AAI system?

@uboatsIt seems that target size no longer affects the pitbull distance anymore. In both of my SP&MP testing, SD-10 always pitbull at ~11nm regardless of the setting.

Has anyone figured out how to unstow gunner's forward gun sight?

Unlike Petrovich, the floating reticle(where you have to align it with pilot's reticle inner ring in order to achieve launch parameter) is extremely shaky when playing with a human gunner. In gunner's point of view, his reticle is dead-on the target, but It's jumping up and down probably for more than 5 degree on my HUD, even though I have the target right in the middle of the inner ring. It makes launching ATGM very difficult, and I can't tell If it's due to de-sync or operating errors. Any advice? Thanks!

Follow up question: Is there a volume knob though?

Just curious, does anyone know what ASM(SAM sub mode) stands for?

''Added movement and engine shutdown check during ground crew operations'' Does anyone know what it means? :joystick:

I notice 'Added radar notch' is in the newest changelog now, I wonder what has changed exactly? What can we expect from this new change? This post is confusing me, since we've got both parties saying that the radar can and cannot be notched, then we have foxwxl saying that It's working as intended due to the 10second memory mode, and now we have a new fix to this? :huh:

Just found out that in order to have the TDC elevation to scan correctly, we need to fly straight and level. If you pitch up, it will scan lower than indicated. Pitch down, it will be higher. In other words, the radar is doing an aircraft stabilization instead of ground stabilization, which possibly leads to the other ground stabilization bug too.