flybywiresim / aircraft

The A32NX & A380X Project are community driven open source projects to create free Airbus aircraft in Microsoft Flight Simulator that are as close to reality as possible.
https://flybywiresim.com
GNU General Public License v3.0
5.16k stars 1.12k forks source link

blue light anti ice #8496

Open Waltervizzi opened 9 months ago

Waltervizzi commented 9 months ago

Aircraft Version

Development

Build info

last version

Describe the bug

I found in the latest updates that unfortunately the blue light of the anti-icers when activated via an external device with Spad Next the light does not turn on but the anti-ices work. instead if they are activated via the plane the blue light turns on how could I solve it? thanks

Expected behavior

the light blu of anti ice dont turn on when use with external panel with spad next. turn on only when push inside aircraft

Steps to reproduce

external panel with spad next

References (optional)

No response

Additional info (optional)

No response

Discord Username (optional)

No response

tracernz commented 9 months ago

This was done as a workaround for GSX abusing the aircraft anti-ice system to perform external de-icing. We should probably wrap this in a B event that people can use for external hardware that toggles the button properly.

Fragtality commented 9 months ago

Would these B event Solution also work for other Middleware? E.g. FSUIPC and Mobiflight. Would not know how to use B-Vars with either. What speaks again 2-3 L-Vars for each Button? (Fail Indication, Switch pushed and maybe a separate Var for the On Indication if Switch pushed can't be used to determine the On Indication)

tracernz commented 9 months ago

Mobiflight are working on support, and AAO and SPAD already support them. No idea about FSUIPC; I can remember using it back in FS2002/2004 times.

-e- FSUIPC supports them from v7.4.0.

Fragtality commented 9 months ago

Oh did not know that before, was never clearly stated in the changelog of FSUIPC 😅

But according to John's Explanations it seems their Usage is not very "straight forward" at the least.

What speaks again custom L-Vars or K-Vars/-Events - as already used with other Cockpit Controls in the FBW API (Where no single B-Var is used yet to my Knowledge)?

I don't want to "bash" here or anything like that, I just want to honestly understand the Reasoning behind that. :) My Motivation on that Matter is around my StreamDeck Plugin for which there is also a FBW Profile ofc. Where I would need to rewrite/change some Stuff in the Plugin to make 1-3 Buttons work on just one Profile. Sure that would be a general Improvement going forward - but I simply don't have Time for that in the Moment because of my other Contributions :/