April 27, 20224 yr I have tried importing H: & L: vars into AAOs for the HypeGroup H145 Helicopter but it doesn’t find many H: vars. I know within Spad.Next there is a facility to manually add them and I have used it successfully within that application. I am considering moving some of my functions into AAOs as I own both applications but have been unable to find H: vars that work successfully with SN within AAOs. Is there a way within AAOs to manually add these H: vars? Thanks
April 27, 20224 yr Commercial Member Check the "Scripting" menu, there you will find options to add variables manually in a dialog or by uploading a file (description is in the AAO manual). And you can always wrap anything that you know the name of into an RPN script and trigger the script with your button "1 (>H:whatevervarname, Number)" (=there is actually no need to import/enter variables into the AAO database at all, just use scripts). Be mindful that many MSFS aircraft use BVars now. The process to trigger those is a lot more involved (see AAO manual, near the end there is a chapter about how to map your own LVars to BVars) Edited April 27, 20224 yr by Lorby_SI LORBY-SI
April 27, 20224 yr Author Worked a great imported 383 H: vars with ease. Shame the file import won’t allow a description on import as it does for manual import
April 28, 20224 yr Commercial Member 11 hours ago, thomaj019 said: Shame This decision was made because it makes the interface more robust. Free text fields like descriptions tend to break the import file formats all the time, because people are not aware of or not careful enough about escaping critical characters. That goes for CSV, TSV and XML alike. Main goal here was safest possible operations when importing a file that the app has no control over. Edited April 28, 20224 yr by Lorby_SI LORBY-SI
Archived
This topic is now archived and is closed to further replies.