Antonius

Thanks, repair did the job. I wonder if the installer errorously finished early before, because I still needed additional 8 gigs to download in the repair process.

Logging out and in again didn't work sadly. I also tried disabling and re-enabling the game on the module manager, but that didn't do anything either.

I finished downloading Syria map a few days ago, but I'm unable to play on it, because despite the module manager confirming that I have it installed, the rest of the game thinks I don't have it. "Instant Action", "Create Fast Mission", "Missions" and "Mission Editor" don't have the option to pick the Syria map and all of the multiplayer servers running on the Syria map still claim that I require the map, despite having downloaded it already. Any way to fix the problem without having to delete and download it again? I'm currently in a place with terrible network.

Yeah, I pretty much use PAL as well. The next best thing is to not lose lock in the first place. One thing you could do is dive so that the radar elevation is above...3 degrees I think, that way the Main Lobe Clutter filter will automatically disable itself. That way the bandit shouldn't be able to notch you, unless he's flying close to the ground. As for datalink contact altitude, the number you see left of the contact icon on the TID is the rough altitude of the contact. For example, number '2' shows that the contact is flying close to 20000 plus-minus 5000 feet, therefore in the range from 15000 to 25000 ft. So '3' is altitude in range of 35000 to 25000 ft, '1' is 15000 to 5000 ft and '0' is below 5000 ft.

Uhh....why though? With modern jets, you can't even see the pilot's skin color 99,9% of the time. Not even with pilot body enabled, Because they have their whole body covered. Not even in external view 98% of the time, assuming they take their visor off when the canopy is open, otherwise the visor completely covers their face. Rest of the time, you won't be seeing any skin on your pilot model, so the whole point is rather pointless. I get that you may want to feel represented, but you're basically asking them to make a seperate pilot model just so you could stare at it during external view right after you spawn for 3 seconds and...that's it. A waste of resources by any definition. You should ask someone likeminded to mod it in or mod it yourself instead. I can understand having more diverse voices in ATC and radio chatter though. Unlike pilot model skin color, that is something that we hear on a constant basis. But they should finish the early access planes first.

That could be because the contact you're trying to lock on is not currently reflected by your own radar, but a datalink contact sent from another donor. Basically, it's not a radar contact, otherwise you could just click on it for an instant lock. That could be because the enemy is not inside your radar scan area, since you're using 2B sweep. This is why I prefer 4B with a 80 degree horizontal arc. Also, you say that it happens right after you engage a target, so I take it that the new target you're trying to lock is quite close. The closer you are to a target, the smaller is your radar scan area. Instead, since there's "nothing there" for your radar, it starts searching for possible contacts in a tight arc while still using the 2B sweep. It will lock into the first contact it finds no matter the range, but it won't find the enemy plane in the first place if it's still outside the 2B sweep cone. This is why I often use the Situational Awareness page to check the altitude of datalink contacts, it allows me to set the correct radar elevation when trying to get a lock. It's especially useful when the contact is really close, because the radar is almost useless at that range without the ACM on. You can use the "step" button in SA to lock the SA slew to a target, so that you can always see the contact's altitude at a glance.

I changed my head position there to use the helicopter tail as a reference for the stretching, but the image in the default position still is stretched....or so I remember. I normally use VR, so my head moves around constantly. My head moves in Su-25T as well, but the image in that plane has always been normal. I took that image in the desktop mode(non-VR), to see if it is a VR problem. Wasn't a VR problem.

The image in the mirrors is horizontally stretched out for some reason. The stretching decreases the field of view for the mirrors, pretty much making them useless, since the mirrors are small to begin with. Other planes don't seem to have this problem, only the F/A-18.