Some H:Vars that don’t seem to work in the RTU
-
Programming my favorite devices and I cannot get the variable for ATC Standby or the LSKs on the RTU to work. ADF Test doesn’t seem to do anything, but that may be that there is nothing attached to it, like the Bar Light
-
NB: the CDU ADF button doesn’t react to presses of it variable either. It’s fine with the mouse in the cockpit, but it’s the only CDU button I cannot get to fire.
-
NB: the CDU ADF button doesn’t react to presses of it variable either. It’s fine with the mouse in the cockpit, but it’s the only CDU button I cannot get to fire.
@dadgametime do you have v1.1? There was a typo in the CDU ADF variable before, now fixed and shoukd match the manual.
For RTUs, try with a 1 instead of an L at the end.
All of these have been discussed before. The search function can be useful at times. -
I have 1.1. Yes. Thank you for checking. Also, I am aware of the typos and I’ve made the appropriate repairs there. I reported that earlier. It’s not working now in 1.1 with either spelling.
-
Yes, there are a few more typos in the manual. These are the events that work for me in MSFS 2024 Starship v1.1:
RTU
Line keys:(H:RTU_Line1_1)
...(H:RTU_Line5_1)
ATC STBY:(H:RTU_TransponderStandbyButton_1)
CDU
ADF:(H:CDU_AdfButton_1)
Line keys:
(H:CDU_Line1L_1)
...(H:CDU_Line5L_1)
(H:CDU_Line1R_1)
...(H:CDU_Line5R_1)
Number keys:
(H:CDU_0_1)
...(H:CDU_9_1)
(in all of the above set last digit to 2 for the right side instrument)
-
Yeah. I’m an idiot. It’s because if you refresh your variable in SpadNext someone entered everything from the manual with the typos to the library and despite entering them correctly, the library of typos come up, so it’s best just to double-check with SpadNext that you look at each variable. I went back and did the few that were causing issues by hand. Also, it appears that the AFD/ADF typo was fixed in the update which is why my buttons quit working. lol.