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.
Are you using Developer Mode or made changes in it?
no
Have you disabled/removed all your mods and addons?
no add-ons installed
Brief description of the issue:
Canāt press com buttons. No buttons on the com panel are accessible. I can change and activate frequencies, for example, putting in the ATIS frequency on COM 2, but I canāt turn them on. It works ok in the Cessna 172, but it does not work in the Grand Caravan. I have absolutely no add ons.
Provide Screenshot(s)/video(s) of the issue encountered:
Do you have the same issue if you follow the OPās steps to reproduce it?
Yes.
Provide extra information to complete the original description of the issue:
No indications in the 208 that any comm panel buttons are being selected. The C-172/Garmin works correctly, including allowing you to show indicators for monitoring the comm radio not selected for mic.
If relevant, provide additional screenshots/video:
Thanks for the info.
Not sure whatās going on. Iāve deleted and reinstalled the 208, and Iāve never had anything in my community folder. I have version 0.14.0 and 1.1.5 for the NXi, with no updates shown as available.
I tried it with all the MS/Asobo liveries removed and just using the default livery. Iāve never had any liveries that werenāt provided in one of the updates.
As noted, the NXi comm panel in the 172 Garmin version works fully as expected.
I really donāt want to try it after deleting the WUās, CUās, and any removeable parts of the sim updates to see if that has any effect on it.
So just no idea why itās having this issue.
Thanks
Confirming and addingā¦ I moved my Community folder to the desktop to ensure no conflicts. My audio panel and ADF are unclickable as well.
But I also found one other issue that may or may not be related. The CB/SW Panel light knob has click spots, and those work, but the knob has no sound and is not animated. I also noticed that the audio panel has no back lighting.
I can confirm that the MID-Panel and ADF does not work.
I noticed that the caravan was changed with SU12. Thus, to get a clean install, I also tried to uninstall, cleared caches, installed only the main-package, then the other liveries step-wise, but these ābuttonsā are not clickable.
Also If we open the dev-mode we can see lots of errors related to the " MID " Panel. Also sending events manualy seems change nothing.
If we compare that with the DA40, with a similar setting ( beside of the adf ) , then all works well and not such errors.
Images related to the DA40: I can setup NAV1 with events, no errors
Well, I canāt help but wonder if this is one of those unrelated package problems. Many of you probably recall how not installing one package that was geographically across the world sim-location wise impacted another airport across the world because someone wrote a code that relied on the missing packageās assets.
In other words, we may all need to get down to the same (Heaven Help Us) package configuration inside the Content Manager. Thatās a darn tall ask, and if it works, doesnāt unfortunately get us closer to what the offending (or missing) package might be. Assuming thatās the root cause in the first place.
Yep - thatās the one. I never fly this thing since I have the Kodiak, so I donāt keep up with complaints on it. I only fired it up today to confirm the com panel/ADF issues.
but I think that will only be the case , if we asssume the problem lies within a ācommonā library. I guess its probaly the problem lies within the changes made within the caravan. Therefore also these ānot found eventsā. But possible is of course, that this MID panel is more or less part of the garmin-lib and the issue is in that - but then: why it works well in the DA40 and why the adf is affected too ?
same for me ā¦ but I knew these sw/cb button bug exist since appr. a year or longer. The product āmaintenanceā of the common airplane packages seems not as good.
Adding a semi-useless comment here to say Iām seeing the same behavior. Really just trying to bump this thread. I recall this happening with the older C208 improvement mod, but I had removed it, and yet the issue remains.
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.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
