So, I am pretty new to coding anything on the Stream Deck. After 3-4 days with a lot of help from ChatGPT I managed to code in a rudimentary way the autopilot for the FSS 727 using a lot of trial and error. I realized the hard way that even if you can change a variable in the Behavior screen of the sim, it does not mean that variable will change when the plane triggers an event, etc. (Example, the lights for ARM or ENG of the Autopilot Altitude Hold)

Anyway, I am trying now to code buttons that will allow me to increase or decrease the EPR and the Airspeed bugs but I don't think they are triggering any events and even if I manage to change some of the variables associated, they don't move the bugs in the screen (meaning the animation, let alone the value).

According to ChatGPT, the problem is there is no B event or IE event or anything associated, just the Mouse Wheel Up or Down that writes into a variable. Even if I change this variable, nothing happens. The XML shows this, though, for what is worth:

 

<CLOCKWISE_CODE>(L:FSS_B727_CP_AIRSPEED_KNOB) 1 + (>L:FSS_B727_CP_AIRSPEED_KNOB)</CLOCKWISE_CODE>

<ANTICLOCKWISE_CODE>(L:FSS_B727_CP_AIRSPEED_KNOB) 1 - (>L:FSS_B727_CP_AIRSPEED_KNOB)</ANTICLOCKWISE_CODE>

 

or for EPR:

<CLOCKWISE_CODE>(L:FSS_B727_PCP_EPR_KNOB1) 1 + (>L:FSS_B727_PCP_EPR_KNOB1)</CLOCKWISE_CODE>

<ANTICLOCKWISE_CODE>(L:FSS_B727_PCP_EPR_KNOB1) 1 - (>L:FSS_B727_PCP_EPR_KNOB1)</ANTICLOCKWISE_CODE>

 

But again, changing these variables via script won't move the bug.

 

Any help?

Thanks

Never mind. Had to create a script which would feed the vár that  you can read. I never knew you could write back to it and make the bug actually move. I think I was focusing on the knob button too much, it was a bit misleading.

it worked for the airspeed, now need to check the EPR gauges

i don’t really get how sometimes an event will respond to a subset (INC, DEC, SET) or sometimes to the set (?), meaning the general action at the top of the hierarchy tree ? 

3 hours ago, pepetrueno said:

i don’t really get how sometimes an event will respond to a subset (INC, DEC, SET) or sometimes to the set (?), meaning the general action at the top of the hierarchy tree ? 

None of these assets follow any rules or guidelines, the aircraft developers just inplement whatever they want. In many cases they do this without caring about the specs that Asobo has laid down. There are at least a dozen ways to operate knobs -and even more to make them in-operable from the outside, so they only work with the mouse (like the spring-loaded GEN switch in the C208 for example)

- IEs never have "SET, DEC, INC". They only have a name
- BVars are the "bindings" of an IE, the two belong together. They can have any "do-word" attached that the developer deems appropriate. There are no rules.
- (L: (B: (IE: (A: etc. -> that is the syntax for READING from a variable
- (>L: (>B: (>IE: (>A: etc. -> that is the syntax for WRITING to a variable or event. 

- When using LVars in AAO, you must supply a unit when the variable is to be sent to the sim: (L:whatever, Number)
Example: (L:FSS_B727_PCP_EPR_KNOB1, Number) 1 + (>L:FSS_B727_PCP_EPR_KNOB1, Number)
Otherwise the LVar is only used internally in AAO

I would suggest staying away from ChatGPT. The topic of simulator behavior code is so esoteric that there is only a limited number of actual people who actually understand it. A chatbot on the other hand can only answer half way correctly to well known questions and facts. Statistically, 85% of chatbot answers are doubtful and 45% are outright wrong. Seems more like waste of time to me.

 

I found an AAO script package for the FFS 727 on fs.to. 

Axis and Ohs Scripts for FSS 727 - Utilities for MSFS | Flightsim.to