search

HeliosVirtualCockpit / Helios

Helios Distribution
https://github.com/HeliosVirtualCockpit/Helios/wiki
GNU General Public License v3.0
204 stars 35 forks source link

Auto map input bindings #274

Open Todd1215 opened 4 years ago

Todd1215 commented 4 years ago

It would be a huge time saver if there was a way to drag & drop a gauge unto a profile and depending on the interface have the input bindings automatically get mapped. For BMS all the input bindings come out of sharedmemory anyway.

BlueFinBima commented 4 years ago

@Todd1215 https://www.youtube.com/watch?v=lEhG-TtENWc

BlueFinBima commented 4 years ago

https://bluefinbima.github.io/Helios14/autobind.html This was provided by @damien022 's composite visual

derammo commented 4 years ago

auto binding as written does not address the problem. as we discussed before, it should bind differently for BMS and DCS. if we are certain there aren't any other interfaces we can support, I guess we can hard code puke both in the composite visuals instead of inventing the "externalized binding templates" I called for in the past.

In any case, we currently are just collecting requirements around the "templates we should have had."

There should not need to be code-based composite visuals. We should be able to build a UFC (or the consoles that whleechock said ertiyu is building) in Profile Editor as a panel with stuff on it and then export to a Panel Template. This template should also allow for automatic bindings against various interfaces. Clearly that includes its default aircraft like the current composite visuals auto bind for one specific DCS aircraft. But it should also bind if used in BMS if applicable.

I would argue it should also be possible for users to define a binding where you use the F18 UFC for another aircraft that we didn't model and save those binding sets. Also, the bindings can be different based on interface. For example, if in the future you are using a DCS-BIOS based interface or some sort of Capt Zeen hybrid thing to bring the Helios UFC into CZ's profile.

I am not saying I know exactly what the answer is. This issue is part of the requirements gathering I think. I will define a GitHub project to collect related stuff as requirements for the "templates we should have had."