Istari6 Posted October 11, 2023 Posted October 11, 2023 In learning the F-16's Cold Start, I'm confused on the following two questions. Hoping someone else here understands what's happening: 1. INS NORM Alignment - I see in Chuck's Guide and Wags' video that we're supposed to "confirm" the Lat and Long by pressing ENTR on each field within the first two minutes. I have not been doing that and the INS still proceeds to 10 and flashes RDY. So I've assumed that this confirmation step isn't important or was changed during Early Access. Bullseye seems to work fine, yet OFLY for Markpoints is screwed up. HUD does not show Nav STPT info (distance), but other functions work. So is it normal that the INS system counts down to 10 and suggests that it's fully aligned even without confirming the Lat/Long fields? I would have thought that if it's needed, it would stop at 70 (degraded) or otherwise indicate it's not 100%. 2. PNEU/ELECT Altitude - In one of the Cold Start guides (Wags video I think), he calibrates the altitude (to QNH) and does a test of PNEU vs ELECT to check difference before setting to ELEC for flight. But he does this right before taxiing, after all other tests are done and INS is calibrated. It seems strangely out of place doing this at the end, rather than as part of the standard cockpit setup while INS is aligning. Is there a particular reason in the F-16 why altimeter is done after INS alignment, or can it be done anytime as part of the normal cockpit flow?
AngryViper.101 Posted October 12, 2023 Posted October 12, 2023 INS Alignment * when starting from an airbase, cold start, the stored alignment works fine, and no need to hit ENTR on each field. * when in flight and using the in flight alignment I 'think' you must ENTR on each field, same as with normal alignment Also, recently I am making sure my HMCS is aligned. PNEU/ELECT I also want to know what other people think, I have been switching over to ELEC mode 'during' stored alignment ... and it seems 'okay' but not perfect. i7-11800H @ 2.30GH | 16Gb 3200MHz | GeForce RTX 3060 | Samsung 1TB SSD | KINGSTON 520GB SSD
AngryViper.101 Posted October 12, 2023 Posted October 12, 2023 (edited) For your information, please remember not to move around or load munitions during the alignment procedure. I even engage the parking brake to ensure that the aircraft remains stationary, unaffected by wind or other external factors. Edited October 12, 2023 by AngryViper.101 i7-11800H @ 2.30GH | 16Gb 3200MHz | GeForce RTX 3060 | Samsung 1TB SSD | KINGSTON 520GB SSD
Tholozor Posted October 12, 2023 Posted October 12, 2023 According to the -1, the altimeter check is performed just prior to taxi, but before the INS knob is set to NAV. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Istari6 Posted October 12, 2023 Author Posted October 12, 2023 Thanks all. I'm definitely not changing any loadouts once I start the INS NORM align process. Good to know that we can use STORED on a typical Cold Start. I'm coming from the F-14, where that option had to be set in the Mission Editor. Sounds like it defaults for the F-16 to have STORED data ready to go. Also helpful to know the -1 has the altimeter check and calibration done before INS knob is set to NAV. I was wondering if there was some reason why it had to wait for the end after INS calibration, but it sounds like it can be done during the general cockpit setup while waiting for INS alignment.
Recommended Posts