Echo38 Posted August 30, 2012 Posted August 30, 2012 Not entirely sure if this is a bug or normal operation, but it's really acting wacky. If I set the HUD to standby mode, and then either tap or hold the Master Mode button, then I can no longer return to normal HUD mode (except for air-to-air), even with the HUD MODE switch set to normal. To reproduce, flip the HUD MODE switch to STBY, then tap or hold the Master Mode button, then flip the HUD MODE switch back to NORM. If you do this, you will no longer be able to access HUD modes other than air-to-air and the standby. If you are in air-to-air and you tap the Master Mode to get to, say, CCIP mode or GUNS mode, you will enter instead STBY mode again--even if the HUD MODE switch is set to NORM and not STBY. Holding the Master Mode button does not remedy the problem, either.
Echo38 Posted August 30, 2012 Author Posted August 30, 2012 To clarify a bit, switching between NORM and STBY works properly as long as the Master Mode button has not been pressed while in STBY mode. The HUD "breaks" only if the Master Mode button was pressed (either short or long) while in STBY mode. I don't know if there are other actions (besides pressing Master Mode) which can break the HUD if they are performed while the HUD is in STBY mode, but there is at least this one. Can one (or more) of the testers reproduce, confirm, and report this bug?
Nate--IRL-- Posted August 31, 2012 Posted August 31, 2012 I see it, thanks. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Echo38 Posted September 16, 2012 Author Posted September 16, 2012 Other: STBY mode works even when the IFFCC switch is set to off. Again, not sure if it's supposed to work this way, but seems a bit suspect.
Nate--IRL-- Posted September 16, 2012 Posted September 16, 2012 That kinda makes sense in that the STBY mode is separate to the IFFCC - it is the Standby to be used when the IFFCC is disabled. Nate Ka-50 AutoPilot/stabilisation system description and operation by IvanK- Essential Reading
Echo38 Posted September 17, 2012 Author Posted September 17, 2012 Gotcha. I've also discovered that, regarding the issue described in the O.P., a workaround is to turn off the IFFCC and turn it back on again. So if it is a bug (I can't tell if it is or isn't), I'd say it's a minor one with a functional workaround.
Recommended Posts