Latest update to AAO has broken all my profiles from @guenseli  with missing text when a switch for a light or autopilot is turned on. On the G1000 profile, the altitude switches no longer work. I was on the previous 2.60 version with no issue. Reimporting the profiles do not fix it. There is a functionality flaw somewhere. 

Edited November 19, 20223 yr by B777ER

Any way I can get the previous version, 2.60? It was working flawlessly. 2.70 broke all my profiles and now I'm stuck. Like an word not allowed, I did not save an older copy. 

Edited November 19, 20223 yr by B777ER

2 hours ago, B777ER said:

Latest update to AAO has broken all my profiles from @guenseli  with missing text when a switch for a light or autopilot is turned on. On the G1000 profile, the altitude switches no longer work. I was on the previous 2.6x version with no issue. Reimporting the profiles do not fix it. There is a functionality flaw somewhere. 

To clarify, the profiles I am speaking of are for StreamDeck. Here are the 4 errors that v2.70 are giving with @guenseli  G1000 SD profile (0- Basic G1000). When clicking on them in the Edit RPN Scripts box, these 4 cause the red light to come on when clicking on them indicating an error. When hovering over the red light, the error message is, (>R:assiMultivar|2|0) for all 4 of them. This was working fine with AAO v2.60.

1. ALT DEC 100 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

2. ALT DEC 1000 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

3. ALT INC 100 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

4. ALT INC 1000 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

 

Further, any switch set up as a toggle, it lost the writing on it when the toggle is switched. 

 

Edited November 19, 20223 yr by B777ER

8 hours ago, B777ER said:

Latest update to AAO has broken all my profiles from @guenseli  with missing text when a switch for a light or autopilot is turned on. 

Further, any switch set up as a toggle, it lost the writing on it when the toggle is switched. 

I think that is the new version 6 of the Elgato software, I got that just yesterday. AAO does not control the positioning of the elements on the StreamDeck, the plugin does this on its own. Meaning, regardless of what version of AAO you are actually running, the graphics on the SD always look the same. 

It looks like something has changed in the Elgato depiciton process, at least regarding text elements. And that includes the Title itself, which is completely SD internal. The line spacing or the default font has changed, text at the end of the title is moved out of the frame.

Not sure what can be done about this (execpt for the authors to rework their profiles), I am still looking into it. Do you have any specific examples of buttons that I could use to check?

Edited November 19, 20223 yr by Lorby_SI

6 hours ago, B777ER said:

To clarify, the profiles I am speaking of are for StreamDeck. Here are the 4 errors that v2.70 are giving with @guenseli  G1000 SD profile (0- Basic G1000). When clicking on them in the Edit RPN Scripts box, these 4 cause the red light to come on when clicking on them indicating an error. When hovering over the red light, the error message is, (>R:assiMultivar|2|0) for all 4 of them. This was working fine with AAO v2.60.

1. ALT DEC 100 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

2. ALT DEC 1000 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

3. ALT INC 100 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

4. ALT INC 1000 - (A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

 

That is because these scripts are actually wrong. Since the last SU of MSFS, these indexed events (K:2:) can be handled through SimConnect directly, and that is what AAO 2.70 is doing now to be in line with the new SDK. That means, that any syntax error will show up in a big way.

K:2: events need TWO parameters to work, and in the above scripts it has only one. In this particular case, the K:2: sets the altitude in a specific SLOT of the autopilot. But the number of that slot is missing.

There are two solutions:
Either supply the slot index, in this case probably 0 (they go from 0 to 3, like, global, default, selected, managed or something - this is relevant for airliners mostly)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

or, use the non-indexed K-Event instead.

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:AP_ALT_VAR_SET_ENGLISH)

@guenseli knows about this, and he will be updating the scripts over time.

Here is the description of the slot index from the MSFS SDK:

 

Quote

alt_mode_slot_index

Set the default alt mode slot index (from 0 to 3). This is the index for the SimVar AUTOPILOT ALTITUDE LOCK VAR which the altitude hold mode will track when captured. You can change this using the ALTITUDE_SLOT_INDEX_SET event ID or retrieve it using the AUTOPILOT ALTITUDE SLOT INDEX SimVar.

When this parameter is set to 1, 2 or 3, the altitude capture will watch the altitude set at that index, unless overridden by changing the currently observed slot using the key event ALTITUDE_SLOT_INDEX_SET. If the currently observed slot has been changed when altitude is captured, the set altitude in the currently observed slot will be copied to the alt_mode_slot_index slot and the currently observed slot will also be changed to that slot.

When this config parameter is set to 0, the altitude capture will always use whatever the currently observed slot is set to and will not change slots or write to any slots on capture.

 

 

Edited November 19, 20223 yr by Lorby_SI

1 hour ago, Lorby_SI said:

I think that is the new version 6 of the Elgato software, I got that just yesterday. AAO does not control the positioning of the elements on the StreamDeck, the plugin does this on its own. Meaning, regardless of what version of AAO you are actually running, the graphics on the SD always look the same. 

It looks like something has changed in the Elgato depiciton process, at least regarding text elements. And that includes the Title itself, which is completely SD internal. The line spacing or the default font has changed, text at the end of the title is moved out of the frame.

Not sure what can be done about this (execpt for the authors to rework their profiles), I am still looking into it. Do you have any specific examples of buttons that I could use to check?

OK, quoting myself here regarding the "missing text on SD actions"

This is definitely an issue with the new Elgato StreamDeck software version 6.0.0.17703. When an action is switched to the alternative picture, that picture has its own "Title" property now - which is empty of course, because it didn't exist before... That is something that the authors of the profiles will have to sort out on their end. I'm not sure that I can help with this. 

Edited November 19, 20223 yr by Lorby_SI

3 hours ago, Lorby_SI said:

OK, quoting myself here regarding the "missing text on SD actions"

This is definitely an issue with the new Elgato StreamDeck software version 6.0.0.17703. When an action is switched to the alternative picture, that picture has its own "Title" property now - which is empty of course, because it didn't exist before... That is something that the authors of the profiles will have to sort out on their end. I'm not sure that I can help with this. 

I have no idea how you keep up on all this stuff, but I love your product because of it!

4 hours ago, Lorby_SI said:

OK, quoting myself here regarding the "missing text on SD actions"

This is definitely an issue with the new Elgato StreamDeck software version 6.0.0.17703. When an action is switched to the alternative picture, that picture has its own "Title" property now - which is empty of course, because it didn't exist before... That is something that the authors of the profiles will have to sort out on their end. I'm not sure that I can help with this. 

You are spot on with this one. SD updated and I started getting it. These are easily fixed, just a little time consuming. If you want an example, the Kodiak SWS profile from him, the aircraft light switches are doing it. The G1000 from him as well, the Autopilot buttons are doing it as well. Seems everything listed as a "toggle" is doing it.  I did the G1000 from him and the Kodiak one already. 

 

 

 

5 hours ago, Lorby_SI said:

That is because these scripts are actually wrong. Since the last SU of MSFS, these indexed events (K:2:) can be handled through SimConnect directly, and that is what AAO 2.70 is doing now to be in line with the new SDK. That means, that any syntax error will show up in a big way.

K:2: events need TWO parameters to work, and in the above scripts it has only one. In this particular case, the K:2: sets the altitude in a specific SLOT of the autopilot. But the number of that slot is missing.

There are two solutions:
Either supply the slot index, in this case probably 0 (they go from 0 to 3, like, global, default, selected, managed or something - this is relevant for airliners mostly)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

0·(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:2:AP_ALT_VAR_SET_ENGLISH)

or, use the non-indexed K-Event instead.

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·-·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·-·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·100·+·(>K:AP_ALT_VAR_SET_ENGLISH)

(A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·feet)·1000·+·(>K:AP_ALT_VAR_SET_ENGLISH)

@guenseli knows about this, and he will be updating the scripts over time.

Here is the description of the slot index from the MSFS SDK:

 

 

I pointed Guenseli to this thread to have a look. I am going to try and replace the scripts with what you listed though in the meantime. Many thanks for giving me the correct values to put into the script editor. 

Edited November 19, 20223 yr by B777ER

thanks for pointing me to it.

 

I have meanwhile created a complete new package:

Standard Avionics Suite for StreamDeck XL » Microsoft Flight Simulator

4 hours ago, guenseli said:

thanks for pointing me to it.

 

I have meanwhile created a complete new package:

Standard Avionics Suite for StreamDeck XL » Microsoft Flight Simulator

Elgato has created a lot of break/fix work for you, love your stuff, donation sent. I'm holding off on updating Stream Deck until you have time to catch-up.

Danke,

Mike