V35B KAP 150 Unit's Display Power State Tied to ADF Power State

Bug Reporting Hub Aircraft & Systems
, ,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

V35B

Brief description of the issue:

If the ADF is tuned off, it will turn off power to the display of the KAP 150 head unit.

Provide Screenshot(s)/video(s) of the issue encountered:

Untitled video - Create and share your videos with Clipchamp

Detailed steps to reproduce the issue encountered:

Power on aircraft and avions. Turn off the ADF. Click the KAP 150 test button and note nothing illuminates. Turn on the ADF and click the KAP 150 test button and note all annunciators illuminate.

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

1.6.0

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

3

Turning ADF off did not cause the other systems to lose power when tested, if there is anything else needed to reproduce this please let us know. Thanks!

4

I think the issue here isn’t that the autopilot doesn’t work with the ADF turned off.

The issue is that the AP head unit’s display on the KAP 150 unit itself will go dark with the ADF turned off.

It would appear that the autopilot will still function, but the display does not.

See this close-up video of the behavior:

Should I redefine the original bug report and/or reword the title of the thread?

EDIT: I reworded the title to reflect the issue more clearly.