HUD lockup - Damage modeling or bug?

[Airflow]

In a practice mission, I had my HUD lock up on me. It did not lock up completely, though: it responded to AA/AG mode changes, but altitude and airspeed were fixed at incorrect values, lines didn't show right. At the same time, parts of the HUD behaved normally. MFDs kept updating, and responded to all buttons, except for returning to the main menu (TAC/SUPT) - I hoped to get a MFD HUD. Analog gauges worked well enough to land.

I did get hit with two bullets, and had a "MC 1 FAILURE". Is it designed to behave like that? I'd consider it damage, but expected computers to fail in a more "all or nothing" way. Something like a MFD or HUD turning off completely, or going non-responsive, rather than responding normally to most commands and not others.

Just checking to see if this is correct and expected behavior.
 

[Harker]

This is indeed part of the damage model. The Hornet has two Digital Data Computers or Mission Computers (MC), and they control different functions. MC1 controls the navigation functions, while MC2 controls the weapons delivery calculations, associated data processing etc. Each computer offers limited backup functionality for the other.

Since your MC1 failed, it's normal that navigation data became invalid, while other stuff worked. Also, the HUD system wasn't damaged, and thus was still working.

Sometimes it's possible to restore some of the lost functionality by using the MC1 OFF/MC2 OFF switches, located in the back of the left console. This will attempt to pass over the work to the remaining computer, if it's included in the latter's backup subroutines.

[bfr]

Oooo nice, I had no idea there was such a failover capability modelled and i've ended up in the same position as the OP before. I'll have to go and get shot up a bit to try it out!