ropob

The SR unit is not normally manned, and apart from my specifying weapons hold and condition green, they are active rather than static units. It should appear similarly to the other radar (the track radar) in the second last figure in the lower right, under the 323-99 text. The visible track radar need not move until a target is to be tracked, so it should be as cold as the search radar, which would typically be moving while scanning, and so generate some heat.

I created a short mission to try and locate SA-2 and SA-10 sam sites using the mission editor's provided template. I used the nevada map and placed both systems in green circular fields (image 0_). I can locate them both with the radar map (image 1_ below with markpoints over the two radars), but when tgp is cued, the SN66M search radar is effectively invisible at 20nm (image 2_), whereas every other vehicle in the template group is visible. At closer ranges the SN66M is barely visible (image 3_). Upon exiting the mission, the SN66M suddenly brightens up, so I suspect it may be related to the IR representation. Attached is the trackfile and mission file. F15E_TGP_NEVADA.trk f15e_missing_sa10_SR_nev.miz

I experienced this issue on the TTI Syria server (2022-May-20, 03:00 UTC). My second sortie, after rearming would not allow me to fire my 2 HARMs, except by jettisoning them. Unfortunately, the track file is very large, about 135MB, due to the activity on the server and the sortie duration. I include a google drive link to the file, as I can't upload it directly. https://drive.google.com/file/d/19EvhaeMqVyYEzwQo8dVzOa8yoa3EoPEi/view?usp=sharing

A friend (the pilot-commander) and myself (co-pilot) were using the Mi-24 in multiplayer. I selected the weapons and they appeared loaded to both of us, but only I could use the pylon mounted weapons. The Aux Stores Lights switch would not light up to indicate the pylons had weapons. The mounted 30mm gun worked fine for both of us, and the weapon loadouts were from the presets available. The Mi-24 was both hot and cold started. When the pilot-commander selected the weapons, they appeared loaded to both of us and both of us could use them. When we swapped roles, only I (pilot-commander) could use the weapons I had loaded. The weapons were visible in external view, but not present until I selected the same loadout.

Hello, I was closing on two AI F4s on TTI Syria in TWS using 4 bar scan at 40deg azimuth, using the . They began to diverge, so adjusted the settings to 2 bar 60deg azimuth. I double pressed the elevation scan bar, so I cycled through the settings until I had the desired settings. As they diverged I used the RAID/FLIR FOV option to look at their tracks, on and off to check the radar settings and their directions. Through some combination of changes to the Elevation scan bar/ azimuth scan and use of the RAID/FLIR FOV function, the Elevation scan bar/ azimuth scan values escaped their limits. See the image below for an example. The AZ/EL page had the yellow border overlapping the green border box, and the contacts disappeared from radar. Undesignating and RSET did nothing to fix the out of bounds values. The AI F4 suggested I file a bug report with his AIM-9 to my face. I have been able to reproduce the issue in the attached track file. In the file, it took far more cycling of Elevation scan bar/ azimuth scan and use of AID/FLIR FOV to reproduce the bug than on the original instance, hence the erratic use of those settings. Kind regards, Ropob. Fa18_scanbar_azi_bug.trk