Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

crap_landing_dave

Members
  • Joined

  • Last visited

  1. Hi, unfortunately I'm not a stream deck user so I can't comment on this. I saw that the AAO topics seemed a lot more active in the PMDG forum itself so maybe you'll get some help there, or if Lorby drops into this thread hopefully.
  2. My primary focus for AAO is mapping to a warthog (seat belts/smoke/xpdr/ext lights/chrono et/trims/gear/flight control axes) As always with AAO, the rotorbrake events are easy to see. Many of the switch actions I get from here seem restricted to toggle or plus/minus type of events rather than setting a state. From memory this is quite common with some PMDG aircraft. One example, beacon: Beacon toggle script command: 11401·(>K:ROTOR_BRAKE) Watching simulator events when physically clicking beacon shows 11401 but then something I have not worked out with 11403 and 11404. I'm sure many will know what I'm failing to spot there. Either way, sending 11401 is enough to toggle the state of this switch. Part 1 figured out. Now I want a switch to only turn on or turn off the beacon, so I'm going to have to read its state somehow. My thought was to read LVars to verify on/off status of switches. From the P3D days, these were slightly strange collection Lvars, of which the beacon was L_switch_114_a. To find the same in MSFS 777, you need to go to: \Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER\Behaviors\PMDG773ER_VC.xml Ok finally in here we search for beacon and see that the variable is still indeed 114_a. I grab this bit from line 6240: <ANIM_CODE> (L:switch_114_a, number) </ANIM_CODE> and I use AAO to observe (L:switch_114_a, number) and see that it is going between 0 and 100.0 for beaon off and on. So now to put these together in a script. This is good enough for me - script for beacon turn on: (L:switch_114_a,·number)·0·==·if{11401·(>K:ROTOR_BRAKE)} Script for beacon off: (L:switch_114_a,·number)·0·!=·if{11401·(>K:ROTOR_BRAKE)} You can repeat the same process for many other switches.
  3. Thanks. This does look like the exact same issue. I'm not sure if I want to go through the solution steps every time. Just thinking out loud here but presumably there's a way to find out exactly what command gets executed for those Airbus lights. If I can get those I can enter them in FSUIpC.ini where I have a shift mode working properly with a memory offset.
  4. Hi, I'm really impressed with the Linda tools. I only installed yesterday and have found it has perfect access to all the things I couldn't find on the airbus easily through FSUIPC. I'm using P3D 2.5, FSUIPC 4.944a, Linda 2.6.4 and the Airbus module 4.3 v2 Here's my issue. I assign buttons according to a 3-position mode switch on the Cessna yoke which is recognized as button 23, 24, 25 UNSHIFTED: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 1: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 2: Button 23: Unshifted Button 24: Shifted 1 Button 25: Shifted 2 I have no repeats and no release settings On a chosen button I have these settings for my modes as a test of external lights: Unshifted, button 16 = Landing Lights toggle Shifted 1, button 16 = Beacon Toggle Shifted 2, button 16 = Taxi Light Toggle If I restart the Lua engine in unshifted mode(button 23) and hit button 16, the landing lights work OK. If I move to mode 1, I get this in the console window, and the beacon lights work as expected: LUA.0: SHIFT MODE = 0 LUA.0: local shift 1 LUA.0: SHIFT LIM 06A30BD30 Mode = 1 I then proceed to move to mode 2, and I get this in the console window: LUA.0: SHIFT MODE = 1 LUA.0: local shift 2 LUA.0: SHIFT LIM 06A30BD30 Mode = 2 However button 16 still activates the beacon lights (taxi lights expected) Rocking the switch back to Mode 1 again gives me this: LUA.0: local shift 1 LUA.0: SHIFT LIM 06A30BD30 Mode = 1 LUA.0: SHIFT MODE = 2 Beacons still active here (correct) and finally back to unshifted gives: LUA.0: local shift 0 LUA.0: SHIFT LIM 06A30BD30 Mode = 0 LUA.0: SHIFT MODE = 1 and beacons again (landing lights expected) So unshifted seems to work initially, but as soon as I move to mode 1, I can't seem to get out of it. Can you see where I might be going wrong? Sorry for the long post. I was hoping as much info as possible would help.
  5. And me. Just wanted to affirm and offer thanks for the solution.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.