Garmin 530 & 430 - knobs and buttons

GunStrauss

I'm trying to setup an intuitive mapping of the GPS units to a trio of HC Alpha, Bravo and Flight Radio Panel, to avoid having an extra unit like the Octavi IFR-1 on my desk.

I have the TBM-850, Bonanza and Baron, so have not tested with any other Black Square planes.

It works pretty good, however, to make the mapping feel intuitive and be communicative, the knobs and push-buttons would need to move and make the correct click sounds.

The good news is that animations mostly works:

All bezel buttons, except the zoom-range buttons
Nav 1&2 and Com 1&2 volume knobs on the Bonanza and Baron
Nav 1&2 volume knobs on the TBM 850

The knobs and buttons that don't animate, but are not necessarily for a user-friendly mapping:

The zoom-range buttons. (They neither animate nor makes sounds when pressing on them with the mouse)
On the TBM 850 (using two 530's), neither COM 1 volume or COM 2 volume animate, neither when using the mouse. Moving the COM1 either with mouse or hardware mapping produces the click sound, COM2 makes no click sound. No animation on any.

The knobs and buttons that don't animate, but are necessarily for a user-friendly mapping:

The two main knobs, inner and outer.
The two main push-buttons

I hope the developers could take a look at this, improving cockpit interactions and make them consistent would be on the top of my wishlist for futher updates at least.

Black Square

As we discussed in another topic, I am aware of this limitation with external hardware, and there is a very specific reason for it.

The Asobo templates for the GNS units create a mutually exclusive condition, when combined with the default sound packages. I can either use much of the template, but replace the main knobs with ones that have sound, or I can use the templates in their entirety but have no sounds.

This could be solved by either replacing the entire sound package (they cannot be decompiled and edited), or replacing the entire template with my own version (difficult, possibly copyright infringing, and opens me up to bugs when the default implementation is changed such as by Working Title).

Future Black Square aircraft, like the Dukes, will not suffer from this issue, since they have their own dedicated sound packages.

I will continue to think about this problem and see if there are any easier solutions than the ones I listed above. While this doesn't always happen, inspiration often comes when I type out a message like this, because it gets my brain rolling. I hope that you understand the situation. I apologize that it makes your experience less than perfectly immersive. I've been happy to supply you with several other custom solutions, because I know just a few minutes of work on my end can make a customer's day. This is just a particularly difficult one to solve.

GunStrauss

Thanks for the thoughtful reply. Hope you find a solution, as you can see from my test, except for the main knobs, it seems a bit random what 'interacts' and not.

Btw. I mentioned that I did this mapping to avoid getting a Octavi IFR-1, but I belive that fully interactive GPS-units would also benefit customers of this unit very much.