Skrzatek

@RogueSpecterGaming I am sure they are not tracking, as F-16 is out of the early access, so it's radar simulation is treated as complete.

@skywalker22 Well, this radar for sure knows what the ground is. Easiest solution would be at least adding some if-elses, that would act as antenna elevation. Harder solution is to code real raycasting into both a2a and a2g modes, with using 3d main lobe and side lobes model. This would provide realistic terrain image in a-g mode and realistic ground clutter and false contacts in a-g mode.

From my post: "Antenna elevation doesn't affect the image (but antenna azimuth does), and the radar scans the entire area in front of the aircraft and directly below it simultaneously." Current F-16's "A-G radar" scans the whole ground, no matter what is the antenna elevation (it can even point up into sky). Scanning terrain while in high pitch angles is related to this behaviour.

@RogueSpecterGaming No, I am thinking that the phrase "Air to Ground Radar" should mean that there is a radar in the air that is emitting radio waves to the ground, not a fancy looking F10 map plotted on MFD.

@skywalker22 I already knew before that "Air to Air" part was poorly simulated, now I was only wondering about A-G.

So if I understand correctly, the only true word in F-16's "Air to Ground Radar" is "ground"?

@skywalker22 Unfortunately, this video is not the answer to my question and provides too little explanation (more from an user point of view, not technical).

Hey, I'm wondering how the F-16 radar uses its antenna in A-G mode. Antenna elevation doesn't affect the image (but antenna azimuth does), and the radar scans the entire area in front of the aircraft and directly below it simultaneously.

Sorry for late respond, I've been struggling with my overall pc performance. Yes, it is working as it should. But I've been able to notice INS drift after 20 seconds. (I believe it was INS drift, I mean I noticed that shkval was drifting from the target each time I hit "uncage" button.) By the way: is shkval screen limited to display certain amount of fps now? I think it has less amount of fps than the outside world view, but it may be only me and my poor pc.

HUD altimeter* relies on the radio beam that is pointed down, so at high bank angles it would not process the data or even not receive it. Same way as the HUD speed indicator that relies on doppler system that is also pointed down. * it is important that altitude must have a russian letter "р" that indicates feed from radioaltimeter. If there is no letter, it shows the barometric altitude, so there are no limits to the bank angle.

Hi, I have a problem. After the update I cannot slew shkval to selected target either created in the PVI-800 or in the datalink panel. It moves to the correct bearing, but does not move in the vertical axis like it was in the BS2. All targets are in correct position according to ABRIS chart.

Hi, you probably figured it out, but I will explain it anyway (in case of someone with the same problem as you will be reading this thread in the future). I must admit, that I have nautical education, so forgive me if I won't use "proper aviation terms". So first of all basic terms: - Heading is an angle between the North and the direction your nose is pointing. (Remember that there are few different Norths related to your heading). - Track is your "course over-ground". You must remember that your aircraft is constantly flying in the fluid. It means that you can point your nose at one direction, but the wind will push you to the side. So the Track is just an angle between the North and the direction you are moving. In ABRIS "BRG" is the Bearing towards the next steerpoint. You must be aware if the next steerpoint is a waypoint from your flightplan or a target you've just entered or something else that has been selected by you on the chart. DTA is Desired Track Angle. It is an angle from one steerpoint towards the another (one you've just passed and second you want to reach). So it is a Track you want to reach in order to move straight towards the next steerpoint. Under your chart there is a scale that shows you your XTE (Cross Track Error) - the deviation from your Track measured in kilometers (ofc if you use metric system in your Ka-50). And the MOST IMPORTANT THING - ABRIS is not fully connected with the PVI-800. If you create a flightplan in the ABRIS, you still have to create waypoints in the PVI-800 in order to fly by autopilot. If you create waypoints in the PVI-800, they will not appear on the ABRIS, so you must create a flightplan if you want to see them on the chart. But funny thing - if you create a navtarget in the PVI-800, it will be displayed on the ABRIS. "The airports are not counted for the PVI-800 right ?" I don't know what you meant by that. You can enter positions of two airports in the PVI-800.

How will you model the SPO-15 Beryoza? I read that its documentation is still classified (but not sure if it's true).

Unfortunately I cannot provide a track. Plane was on a free trial and didn't think about saving one. All my actions are described and it was happening when I frequently used flaps during multiple touch and go landings (in most cases 2 attempts were enough to brake them). I can also provide information that it happened both after autostart and manual one, so all switches (according to checklist) were in the correct positions. Maybe the pump shouldn't be used so often with such short intervals?

Yes, I always return the lever to neutral, but only in the air. On final I didn't return the lever to neutral after extending flaps to 55 degrees (I extended them fully down after passing the marker). Then I retracted them on the ground and after few seconds I switched the lever to 20 degrees position for takeoff.