dlmorgan999

Ignore this: I just grabbed 2.33 and I'm good. I should have looked first! I'm currently running 2.32 b34. It works great, but today I went to install a new Stream Deck profile which included scripts. When I try to import them, this is what I see on the "Select scripts to import" screen: LorbyAxisAndOhs.CheckableItem I tried several different script files, including one I've already imported, and they all do this. Is this a known issue?

That makes sense. Thanks for all your help!

Ok - thanks. The idea of adding it to the AAO database sounds interesting. I'll check that out.

This works great. Now to dissect it and see if I can completely understand everything it's doing. 😉

There is an event for the AS530 called AS530_CDI_Push. It's defined in the Mobiflight events file as AS530_CDI_Push#(>K:TOGGLE_GPS_DRIVES_NAV1), but it's not in the AAO event list (either by searching, or by manually looking at the HTML-Variables list). Any ideas?

I'll also mention that while I'm not a developer by profession, I do work in IT and can program reasonably well. But I'm brand new to RPN scripting and am very much in learning mode right now. So any examples I get are very helpful.

I've downloaded a few of those but haven't installed them yet. I'll have a look.

Thanks for the detailed response! I am using the AAO SD plugin (it's one of the main reasons I bought AAO - it's a very useful plugin 🙂). I'll modify my script per your suggestions.

I've done a bunch of reading of the documentation, and searched the forum, but haven't yet been able to find an answer. Is it possible to create a local variable (local to AAO) and then display that value on a Stream Deck? The particular thing I'm trying to do right now is to convert the GPS ETE simvar (which is in seconds) to a formatted hour/minute/second string. I created this script, but I haven't yet been able to see the ETE local variable in the watcher, so I don't know if I'm doing this right, or if it's even possible. %((A:GPS·ETE,seconds)·3600·/·int·)%!02d!·:·%((A:GPS·ETE,seconds)·3600·%·60·/·int·flr·60·%)%!02d!·:·%((A:GPS·ETE,seconds)·60·%·int·flr·60·%)%!02d!% (>L:ETE, String)

Ok - sounds good. Thanks for the alternate method to edit them.

I just purchased AAO for a number of uses. Since I had some Saitek panels from years ago, I decided to bring them out and give them a try. I'm currently playing with the BIP. It works as programmed (meaning the LEDs change as programmed for the default script), but I'm having issues making updates. After I've opened the editor by going to Hardware --> Saitek BIP Configuration, I selected Saitek BIP scripts-BIP default update script. It loads up just fine, and I can make a change (as a simple test, I just tried changing the LED colors). I then click Update and I see "Script updated", but if I then close the config screen and load the script again, the changes aren't there (and I don't see them on the BIP either). I noticed that after the updated message goes away, there is no longer a value selected in the Select script dropdown, but all the values from the script I just edited are still there. I also noticed that if I select a script from the dropdown, and then select a different one, the form isn't properly getting updated with the correct values (it works fine for the first load). Am I doing something wrong? If not, are you able to reproduce this?

I'm puzzled by this comment. On the Reality XP page, they list "GNS 430 WAAS XP GPS", and the same thing for the 530.

One thing I really like about the EZCA integration with TrackIR is that they let you enable/disable TrackIR on a per view basis. Being able to disable it for instrument views (radio stack, GPS, PFD/MFD, etc.) makes it much easier to make adjustments to the avionics. :smile:

I had TrackIR long before I had EZCA (which I just bought a couple of weeks ago). In my opinion, TrackIR is a must-have for flight simulation. It makes for a much more immersive experience. EZCA integrates nicely with TrackIR, and perhaps I'm imagining things, but it seems like TrackIR is smoother after the integration. I know it's a good chunk of money, but I personally wouldn't fly without it.

Ok - thanks. I suspected it was a false alarm. I'm planning to buy and install this plane tonight so I wanted to check just to be safe.