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.

scottike

Members
  • Joined

  • Last visited

  1. Yes, the tablet is available. I display an X-touch overlay on it and it can display web pages as well, even in career. No worries if you don’t have time, I just wanted to make sure I didn’t miss an easy fix.
  2. In career, the web page displays, but I can never get the atc options to populate.
  3. In free flight the webpage is visible, but not populated with options until I activate the atc tower icon in the toolbar. At that point the web page updates and displays the atc choices.
  4. Interesting. Do you have any suggestions on how to test if the ATC communication is just a “look-alike”? If it’s the original, how could I establish a bridge without launching the bridge panel on the toolbar?
  5. The ATC communications window exists and populates with options, now in SU4, just like in free-flight. That was why I was tempted to try to find a hack to get the bridge working. Maybe they'll open it up someday. If someone wants to "cheat" in the career, I fail to see the harm. It's not exactly an e-sport...
  6. I'm dipping my toes into the MSFS career, and apparently, that mode restricts what toolbar utilities it allows. Irritating. I have the AAO EFB running, but I can't seem to get the ATC bridge working. Any thoughts on workarounds?
  7. I have a single button on my joystick that is causing spurious inputs. It is interfering with assigning other inputs. The “ignore input” selection is a big help, but I need to remember to do it for every new assignment. Is there a way to permanently ignore this button?
  8. scottike started following AxisAndOhs Support
  9. The active AAO InGame Panel requirement was the problem. Thaks!
  10. Thanks, so here's the panel ID I am trying to toggle: \AppData\Roaming\Microsoft Flight Simulator\Packages\Community\bushtalkradio-client\html_ui\InGamePanels\BushtalkClient\CustomPanel.html (1 hit) Line 30: panel-id="BUSHTALK_CUSTOM_PANEL" Here's my script: 'BUSHTALK_CUSTOM_PANEL'·(>L:AAO_TOGGLE_PANEL,·String) However, the panel doesn't toggle when I activate the command. I'm using V4.10 b51. Is there an error in my command?
  11. Hi, I’m trying to toggle ingame toolbar panels, but the AAO_TOGGLE_PANEL command doesn’t show up in my lvars list. The other AAO panel lvars are listed. Is this still a valid script? Open and close other ingame panels You can toggle other ingame panels (ATC, Weather, GSX, GTN750 etc.) using the following RPN script code: 'PANEL_ATC'·(>L:AAO_TOGGLE_PANEL,·String) The panel ID at the beginning can be found in the panels' html file. Those are usually located inside their addon packages in the path "/html_ui/InGamePanels". Or use Notepad++ to search for "panel-id" in all *.html files in the /Packages folder of MSFS.
  12. Here's what I logged up until Linda stopped responding to button inputs: FSUIPC logging bit cleared: 2Global shift set...[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTSGlobal shift UNset...[C] Control: 66341 - 0 TOGGLE_ELECT_FUEL_PUMP2[C] Control: 66340 - 0 TOGGLE_ELECT_FUEL_PUMP1[C] Control: 66290 - 1 TOGGLE_ELECTRIC_VACUUM_PUMP[C] Control: 66516 - 0 FUEL_SELECTOR_2_OFF[C] Control: 66517 - 0 FUEL_SELECTOR_2_ALL[C] Control: 65955 - 0 FUEL_SELECTOR_OFF[C] Control: 65956 - 0 FUEL_SELECTOR_ALL[C] Control: 66301 - 0 TOGGLE_STARTER2[C] Control: 66301 - 0 TOGGLE_STARTER2[C] Control: 66364 - 0 TOGGLE_ALTERNATOR2[C] Control: 66300 - 0 TOGGLE_STARTER1[C] Control: 66300 - 0 TOGGLE_STARTER1[C] Control: 66363 - 0 TOGGLE_ALTERNATOR1Global shift set...[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTSGlobal shift UNset...Global shift set...[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTSThen after LUA engine reload:[G] Developer mode OFF[iNIT] Loading...Aircraft: RealAir Beech Duke Turbine N710DS WAircraft module detected: RealAir B60TAivlaSoft library loaded...FSX standard library loaded...IAO library loaded...RealityXP library loaded...A2A MAP library loaded...[C] Control: 65716 - 0 VOR1_SET[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTS[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTS[C] Control: 66058 - 0 PANEL_LIGHTS_SET[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66579 - 0 TOGGLE_CABIN_LIGHTSLoading a fallback joysticks config...Loading RealAir B60T joysticks config...Module: RealAir B60T Started...Ready to go, Captain!Global shift UNset...Global shift set...[C] Control: 65564 - 0 ATCGlobal shift UNset...Global shift set...[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATCGlobal shift UNset...[C] Control: 65752 - 0 PARKING_BRAKES FSUIPC logging bit set: 2WRITElua 735F, 1 bytes: 00 .WRITE0 7321, 60 bytes: 4C 47 3A 43 3A 32 00 00 00 00 00 00 00 00 00 00 LG:C:2..........00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 ............WRITE0 735F, 1 bytes: 01 .WRITElua 7321, 60 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................00 00 00 00 00 00 00 00 00 00 00 00 ............WRITElua 3400, 2 bytes: 00 04 .. FSUIPC logging bit cleared: 2 LVars watching list cleared... Offsets watching list cleared!It's interesting that I never issued these commands:[C] Control: 65716 - 0 VOR1_SET[C] Control: 66379 - 0 TOGGLE_NAV_LIGHTS[C] Control: 66239 - 0 TOGGLE_BEACON_LIGHTS[C] Control: 66240 - 0 TOGGLE_TAXI_LIGHTS[C] Control: 66058 - 0 PANEL_LIGHTS_SET[C] Control: 66377 - 0 TOGGLE_RECOGNITION_LIGHTS[C] Control: 66579 - 0 TOGGLE_CABIN_LIGHTSAnd then it did issue the commands I had requested after Linda stopped responding:Global shift UNset...Global shift set...[C] Control: 65564 - 0 ATCGlobal shift UNset...Global shift set...[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATC[C] Control: 65564 - 0 ATCGlobal shift UNset...[C] Control: 65752 - 0 PARKING_BRAKESI have seen no evidence of jittering buttons or commands. It there additional logging you would suggest?Thanks,Scott
  13. Could this also apply to SimConnect commands issued by FSUIPC? I have two axes that control the RealAir Duke cowl flaps based on what zone they are in. Perhaps I have set that up incorrectly and am sending repeat commands.
  14. Hi Artem,What rate of button triggers is too high? I have zoom functions mapped that I will press very quickly to zoom in and out. Or is the maximum rate faster than a person could be expected to generate (suggesting a faulty button instead)?Thanks,Scott
  15. I've recently installed LINDA 1.1 over FSUIPC 4.749e. After running properly for a few minutes, joystick button commands will cease to have any effect in FSX. When I reload the LUA engine via the LINDA gui, all the commands that did not reach FSX take effect. So, if I was trying to zoom out, then turn on the autopilot, these actions would occur upon LUA engine reload without any additional inputs from me (like they were stored in a buffer).Setup notes:I run a VRInsight M-panel using the FSP2 (not FSUIPC)A few button commands are still controlled by FSUIPC-my CH Yoke hat switch is not fully detected, so I use FSUIPC (see my other post)The CH Yoke is not using the CH Control Manager, just the standard Win 7 x64 HID driversIt's interesting to note that my POV hat functions continue to work through FSUIPC when the LINDA commands stop working.No error messages display in the LINDA console when this occurs.Has anyone else seen this behavior or have any ideas what to try?Thanks,Scott
  16. Yes, FSUIPC detects them reliably. Hat up is button 32, right is 34, down is 36, and left is 38. For now, I've worked around the issue by assigning the hat functions in FSUIPC directly and using LINDA for the rest.

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.