TheAviationFox Posted 20 hours ago Report Posted 20 hours ago Have you tried looking up the variables through MSFS "developer mode"? If not, start the MSFS developer mode, then open menu "Tools" and select "Behaviors" from the list. You can get a glimpse of the code behind a switch by hovering the mouse over a button or lever in the cockpit and then pressing "CTRL+G". Try this with the autobrake switch and find out what LVAR will actually move it and the LVAR that will activate each mode.
Cuantreau Posted 20 hours ago Report Posted 20 hours ago 4 minutes ago, TheAviationFox said: Have you tried looking up the variables through MSFS "developer mode"? If not, start the MSFS developer mode, then open menu "Tools" and select "Behaviors" from the list. You can get a glimpse of the code behind a switch by hovering the mouse over a button or lever in the cockpit and then pressing "CTRL+G". Try this with the autobrake switch and find out what LVAR will actually move it and the LVAR that will activate each mode. Yes, that's exactly what I've done, the values are the same, as I explained, so I don't get why the disarm amber light is not working with the preset configured.
John Dowson Posted 20 hours ago Report Posted 20 hours ago 39 minutes ago, Cuantreau said: I couldn't see it because the console is giving me constant repetitive event "BLEED_AIR_SOURCE_CONTROL_SET and MASTER_BATTERY_SET", so I can't read anything else, maybe I'm not doing it right but that is what it throws at me. You can use the ini parameter DontLogThese to ignore those, best used in your profile section. See the Advanced User guide for details on this ini parameter. 39 minutes ago, Cuantreau said: Within msfs behavior I could verify that the current value from switching the AB rotary switch with the mouse, is the same as switching it with physical rotary switch assigned with fsuipc presets. So AB disconnect amber light should work as expected but it doesn't, strange. Yes, strange, However there is an issue with some external controls in that they don't work in the same manner as the internal one. This has been reported to Asobo (a long time ago), but I guess it has not yet been fully addressed. Is there another lvar that holds/controls the light state? If so, you could try using that.... John
John Dowson Posted 20 hours ago Report Posted 20 hours ago 15 minutes ago, John Dowson said: However there is an issue with some external controls in that they don't work in the same manner as the internal one. This has been reported to Asobo (a long time ago), but I guess it has not yet been fully addressed. ...but this shouldn't apply when using presets/calc code as that is executed via the Gauge API, so I don't understand this either...
Cuantreau Posted 19 hours ago Report Posted 19 hours ago Yes, it's strange, it should be working with presets.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now