January 13Jan 13 I have been chasing a bug for a few days with little joy. I have an IniBuilds A350 MSFS 2024 Axis and Ohs 4.56 b19 MSFS2024 The problem I am having is that my apu keeps coming on - not the starter, just the apu master and opens the apu ecam page. I have traced this to axis and ohs, when I close an assigned axis or assign button dialog. The sim screen flickers and about a second later the apu is activated. This happens when I cancel or save, no difference. I have/had a script bound to a button my alpha, this only seems to be happening since I created the script, but I have since removed the script. the script 1·(>IE:AIRLINER_APU_MASTER_SWITCH)·(WAIT:3500)·1·(>IE:AIRLINER_APU_START) Any help really appreciated... DC
January 13Jan 13 Commercial Member Closing those dialogs, the script editor and some others, will completely reset and reload the entire aircraft configuration. Same as if you reload the aircraft, switch to a different aircraft, disconnect/reconnect or close/reopen the app. This is done to avoid unstable or undefined states regarding scripts and assignments. AxisAndOhs can't do anything on its own. My best guess is, that you have that IE assigned somewhere, and that it is triggered by the reload. Or some other event that causes the same thing. Edited January 13Jan 13 by Lorby_SI LORBY-SI
January 13Jan 13 Author Thanks, a little progress this evening (L:INI_APU_MASTER_SWITCH) the inibuild pdf states it is a bool (non reset) This seems to toggle on and off every time I close the dialog windows. I have tried other aircraft no issues just cannot seem to get this sorted, I know I have done something but I am darned if I can work this out. I did notice my apu light remains lit on my bravo, I cleared the bravo script but no luck.... DC
January 13Jan 13 Author It was the APU Off script 0 (>IE:AIRLINER_APU_MASTER_SWITCH) that was causing the problem Thanks again for your help it is appreciated.... DC
January 13Jan 13 Commercial Member 54 minutes ago, DavyC100 said: It was the APU Off script 0 (>IE:AIRLINER_APU_MASTER_SWITCH) that was causing the problem Thanks again for your help it is appreciated.... DC If IEs don't behave, try their bindings instead (the BVars) In this case possibly 1 (>B:AIRLINER_APU_MASTER_SWITCH_Off) or 0 (>B:AIRLINER_APU_MASTER_SWITCH_Set) Plus, the "opposite" value for the IE could also be -1 or 2. Depends on how the switch works. But I have seen many that are just toggles with no dedicated On/Off option. You would have to read the current value first and then only trigger the toggle when necessary. For example like this: (L:INI_APU_MASTER_SWITCH, Number) 1 == if{ 1 (>IE:AIRLINER_APU_MASTER_SWITCH) } (toggle only when the master switch is currently ON) Edited January 13Jan 13 by Lorby_SI LORBY-SI
Create an account or sign in to comment