ice41

the current F16 INS in DCS will start alignment with SALT set to the barometric altimeter value, and SALT can be changed by the barometric pressure knob on the altimeter during alignment. I noticed that when an alignment completes and the knob is turned from ALIGN to NAV, the SALT will magically be synced to the actual altitude reported in the external view info bar regardless of the value used for alignment. The odd SALT value in the screenshot is most likely an effect of the inproper alignment procedure. wptmd7675 I took a look at your original trackfile. I did not see you confirming the LAT LNG and SALT values during the NORM alignment. You must use dobber up/down and ENTR to confirm each value at the beginning of a NORM alignment. see 2:15 in the norm align tutorial by Wags. Though unless you are doing a new alignment after shutdown, there's really no reason to use ALIGN NORM and should just go with the ALIGN STOR HDG

ED's Viper manual page 188 says "It is a three-position switch that overrides any mode except emergency jettison." in reference to the dogfight/missile override switch. If selective jettison is considered to be a master mode, then the current implemented behaviour is intentional.

Did you verify your coordinates? After a full shutdown at a different airport, my stored heading alignment has my original spawn point's coordinates and heading.

Do you do the full 8 minute INS alignment and enter in the correct GPS coordinates after you repair?

I've ran into this once before and thought it was bad luck. Just messed around to find why it happens. This only happens in A3 or A1. Bars and TWS/RWS doesn't seem to matter. When the scan is about to bounce off the right side azimuth line, slew the cursor to the left to drag the azimuth limit. Time the slew correctly and the radar gets stuck. When it gets stuck, a quick slew to the right can fix it. The radar seem to only get stuck on the right side. If I attempt the same thing on the left side, I can see the bars looping as I slew to the right but it never gets stuck when I stop slewing. My track also attached. radar_stuck.trk

The bomb fall line and the TGP location never matched for me until I realized the target box needs to be slewed with HUD as SOI, and then switch to TGP SOI to refine the Point/Area track. I don't have the map for the track so I'm wondering if this is what's happening? Start with TGP SOI and hit TMS down to CZ and recenter TGP on the target box. DMS Up for HUD SOI and slew around until a target comes up on the TGP, and then TGP SOI and switch to point/area track to track the target. The CCRP target won't be exactly on the target, but I found this to be close enough that the laser can correct the difference.

Cold is only activated if the last selected missile before entering DGFT is AIM9 so you can enter DGFT, exit, and enter DGFT again to get Cold AIM9 without taking your hands off the HOTAS

Create fast mission, JHMCS on and look to the left track and picture attached in case what I am seeing is different the oval for radar ACM Bore mode is always on since the latest open beta patch Previously the oval only appeared when using the ACM Bore mode, which I believe is how it should be. ACM_Bore_JHMCS_Oval.trk