Previously, this was working fine for the Fuel Pump in the SWS Kodiak.

(VARSEQ:2~1~0~1|L:1:SWS_FUEL_Switch_Pump_1, Number)

Since release 4.57 b21 the behavior appears to have changed to 2 1 2 1 etc.

The debug window provides no further information upon each execution other than (VARSEQ:2~1~0~1|L:1:SWS_FUEL_Switch_Pump_1, Number).

I believe I have the syntax correct as it worked previously.

If the following are sent individually, they work fine.

2 (>L:1:SWS_FUEL_Switch_Pump_1, Number)

1 (>L:1:SWS_FUEL_Switch_Pump_1, Number)

0 (>L:1:SWS_FUEL_Switch_Pump_1, Number)

1 (>L:1:SWS_FUEL_Switch_Pump_1, Number)

Also getting the same behavior with iseq as below:

2 1 0 1 (L:1:SWS_FUEL_Switch_Pump_1, Number) (L:Pmp_idx) 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:Pmp_idx)

Output from debug window

2 1 0 1 (L:1:SWS_FUEL_Switch_Pump_1, Number) (L:Pmp_idx) 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:Pmp_idx)

2 1 0 1 0 3 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:Pmp_idx)

2 (>L:1:SWS_FUEL_Switch_Pump_1, Number) 0 (>L:Pmp_idx)

Next run

2 1 0 1 (L:1:SWS_FUEL_Switch_Pump_1, Number) (L:Pmp_idx) 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:Pmp_idx)

2 1 0 1 0 0 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:Pmp_idx)

1 (>L:1:SWS_FUEL_Switch_Pump_1, Number) 3 (>L:Pmp_idx)

Any thoughts as to what may be happening?

Edited Saturday at 01:19 PM2 days by HardCat55
Title Change

1 hour ago, HardCat55 said:

(VARSEQ:2~1~0~1|L:1:SWS_FUEL_Switch_Pump_1, Number)

Since release 4.57 b21 the behavior appears to have changed to 2 1 2 1 etc.

Not for me. I am testig your script right now, and the sequence is as expected. I doublechecked with (VARSEQ:2~1~0~1|L:test) and the (L:test) goes 0-1-2-1-0-1-2 etc. (using "Scripting->Watch simulator variables" to observe the value of the LVar)

Please note that there has been an update to the Kodiak, and that according to other users, the SWS LVars and their functionality have changed. I wouldn't rule out the possibility that there is a discrepancy between writing to the var and reading from it.

Also, the 4.57 is already obsolete. All shops should have the 4.58 by now.

Edited Saturday at 11:51 AM2 days by Lorby_SI

1 hour ago, HardCat55 said:

Fuel Pump in the SWS Kodiak

Which version of the aircraft is that and in what simulator?

I am looking at my SWS Kodiak in MSFS2024 and the variable for the AUX FUEL PUMP switch is called (L:SWS_FUEL_Switch_Pump_1, Number). It is not instanced, "(L:1:" doesn't work for me

??

Edit: same story in MSFS 2020 with the latest SWS (I think). The variable is not indexed, and a script like "(VARSEQ:2~1~0~1|L:SWS_FUEL_Switch_Pump_1,·Number)" is working fine for me.

Edited Saturday at 12:09 PM2 days by Lorby_SI

I have updated AAO to 4.58 b02.

I am using MSFS2024, and the Kodiak is version 2.2.0 from the manifest.json file.

This is an excerpt from the mouserect behaviors in devmode for the pump that I see.

quit

:2

(L:1:SWS_FUEL_Switch_Pump_1) 0 == if{

1 if{

1 (>L:1:SWS_FUEL_Switch_Pump_1)

}

}

No change at this point.

(VARSEQ:2~1~0~1|L:SWS_FUEL_Switch_Pump_1,·Number) does not work for me, the opposite from you.

I am going to completely remove the Kodiak and do a fresh download and install.

Will report back.

Edited Saturday at 12:52 PM2 days by HardCat55
Add a line of comment.

After a fresh install of the Kodiak behavior is the same. I had also made sure there were no liveries installed that may cause interference.

Interestingly, the downloaded install file had the same date as the one I had, but the file size was different. (larger)

The mouserect behavior code is the same as I had reported above.

Not sure where to go from here.

Have been using the Test button in the Script Editor for testing, and calling the script from my Stream Deck.

I purchased the Kodiak directly from SimWorksStudio.

My version is "Installer_SWS_Kodiak_Wheels_MSFS_20260608.exe" directly from their website. As stated previously the manifest.json file shows 2.2.0 which is the MSFS2024 version. Perhaps that is the difference.

Is their anything special I need to do to drop back to 4.56 ?

Appreciate your help with this, I do not suspect a problem with AAO either but it is worth checking.

I will be away from my computer the rest of the day but will investigate more tomorrow.

Thanks.

32 minutes ago, HardCat55 said:

After a fresh install of the Kodiak behavior is the same. I had also made sure there were no liveries installed that may cause interference.

Interestingly, the downloaded install file had the same date as the one I had, but the file size was different. (larger)

The mouserect behavior code is the same as I had reported above.

Not sure where to go from here.

OK, now I'm getting somewhere. I bought the MSFS 2024 version of the Kodiak (I didn't know that there was one). Now I am seeing the same behavior code, and I have the same problem with the script.

The cause is not VARSEQ or ISEQ, something must have changed about the L:1 variables, potentially in the sim itself. To be investigated...

Try using Z: instead of L:1: (according to the MSFS 2024 SDK documentation they are the same)

(VARSEQ:2~1~0~1|Z:SWS_FUEL_Switch_Pump_1,·Number)

Edited Saturday at 01:54 PM2 days by Lorby_SI

That was it! Works perfectly now!

I wonder how many out there don't know this one?

If it is sim side, it has happened since SU5 because as I stated earlier it was working up until recently.

Thank You...

2 minutes ago, HardCat55 said:

If it is sim side, it has happened since SU5 because as I stated earlier it was working up until recently.

No, the problem is in AAO itself, and it is definitely about the L:1: variables. Something has changed regarding the initial identification and parsing of those vars. Curiously enough they work properly in some situations, but not in others. Which makes it really difficult to find the problem. But if the Z: is indeed the workaround solution, I will publish a note to that effect.

Edited Saturday at 02:11 PM2 days by Lorby_SI