Closed MadKreator37 closed 11 months ago
BlueFinBima
commented
1 year ago @MadKreator37 looks like you are correct about Terrain following. 456, 522 and 523 are all now on device TFR and previously they were on device FLCTRL. The only other switch defined to TFR was already defined in the interface with the current device.
BlueFinBima
commented
1 year ago https://github.com/HeliosVirtualCockpit/HeliosInterfaces/commit/8aafd58e8950e2b61a03c21b159b4ed9742b825b is the mirror commit for the JSON Interface.
MadKreator37
commented
1 year ago Great! Will the profile need updated/ new bindings due to the new Device ID's?
BlueFinBima
commented
1 year ago @MadKreator37 No, the profile will just start working again when the changes to the interface are picked up. You can try this by using the JSON version of the interface mentioned above.
MadKreator37
commented
1 year ago Perfect, thank you very much!
MadKreator37
commented
1 year ago New interface works as expected with no profile modification necessary. A+
BlueFinBima
commented
11 months ago Delivered in 1.6.6040.3
[ x] I have read Getting Help
Describe the Helios Issue
TF Couple switch on CAS panel and Flyup Cover and Switch on Left Bulkhead, outputs not functioning. Possible something changed in module when Terrain Following radar was added. Verified bindings are correct in the profile.
Steps to Reproduce the problem
Steps to reproduce the behaviour: open profile start game move TF Couple switch in Helios- No Movement in DCS ( bindings are correct and input functions) move Flyup switch cover and switch in Helios- No movement in DCS (bindings are correct and inputs function)
Expected behavior
Switches in cockpit move when they are switched on/off in helios
Please complete the following information:
The problem happened while using
(place an 'x' between the square brackets for all that apply)
Additional context
Seems to be an interface issue. Tried re-binding in the profile with no luck,