February 4, 20215 yr Hello everyone, I have installed the latest AAO version and the AAO StreamDeck plugin. At the moment I am using the Flight-Tracker-StreamDeck plugin, with which I am getting along quite well. I have always logged the Event IDs with FSUIPC7 and then entered them in the Flight-Tracker Plugin. I think I could do something similar with the AAO plugin. In a StreamDeck profile for AAO, provided by @guenseli, I have seen that it is possible to operate switches in MSFS 2020 whose Event Id cannot be logged by FSUIPC7. For example, in the TBM there is a switch for the tanks that can be toggled between man and auto. FSUIPC7 does not issue an Event Id for this. How can I find out the event with AAO? I assume that this can be found out via Manage RPN scripts. But how? It would be nice if someone could explain the procedure step by step using one or two examples. Unfortunately, I can't find any instructions for this relatively new plugin on the internet. Greetings Michael
February 4, 20215 yr Commercial Member 53 minutes ago, mikeB2210 said: Hello everyone, I have installed the latest AAO version and the AAO StreamDeck plugin. At the moment I am using the Flight-Tracker-StreamDeck plugin, with which I am getting along quite well. I have always logged the Event IDs with FSUIPC7 and then entered them in the Flight-Tracker Plugin. I think I could do something similar with the AAO plugin. In a StreamDeck profile for AAO, provided by @guenseli, I have seen that it is possible to operate switches in MSFS 2020 whose Event Id cannot be logged by FSUIPC7. For example, in the TBM there is a switch for the tanks that can be toggled between man and auto. FSUIPC7 does not issue an Event Id for this. How can I find out the event with AAO? I assume that this can be found out via Manage RPN scripts. But how? It would be nice if someone could explain the procedure step by step using one or two examples. Unfortunately, I can't find any instructions for this relatively new plugin on the internet. Greetings Michael Hello Michael, FSUIPC doesn't log any events because there are none. In MSFS, many controls are operated by accessing the variables that control their animation. For whatever weird reason that triggers the actual action in the sim. But that also means that there is nothing to log or to track - you would have to know the name of the variable before you can track it - which defeats the whole principle. I'm afraid there is no simple solution to this. The only way to get their actual names is the hard way: - Let AAO collect all possible LVars and HVars and try to construct the required variable name from the tags (that is what the simulator does internally) - Check online, if somebody has published H- or L- variable names for MSFS - Use Notepad++ to scan through all XML, JS, and HTML files of the sim and look for (>H: or (>L:. Looking at the file names you can find the correct one for the aircraft, then you have to thread your way up through the "UseTemplate" tree to find the actual values for the #..# tags (that is what guensli does). I am still working on a parser that reads all valid names from the simulator files reliably. Unfortunately there are so many errors in the files, that quite a few of them cannot be read as XML, althought they are supposed to be in that format. I have to work around all these oddities, so at the moment, Mark 1 eyeball is still the best option. Edited February 4, 20215 yr by Lorby_SI LORBY-SI
February 4, 20215 yr Author Hi Oliver, thanks for your answer - sounds I have to learn the hard way 🙂
February 4, 20215 yr Commercial Member 6 minutes ago, mikeB2210 said: hard way My own preferred tool is Notepad++ -> Search -> "Find in files", applied to the entire "Packages" folder of MSFS, using "*.xml, *.js, *.html" as filter. When I am looking for a specific variable, I usually first scan for the word itself - like "ice" or "heat" or "light". If I know that I am looking for a click event, searching for LEFT_SINGLE_CODE, CLOCKWISE, ANTI_CLOCKWISE yields good results too. Just be mindful that some characters are escaped in XML files. For example ">" is the ">" character. So instead of searching for "(>H:" like you normally would, you have to search for "(>H:" too. Edited February 4, 20215 yr by Lorby_SI LORBY-SI
Archived
This topic is now archived and is closed to further replies.