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.

Crabby

Members
  • Joined

  • Last visited

  1. Yep. It seems that the only developer doing that is PMDG. They are sticklers for following the SDK and programming controllers using the PMDG SDK is a breeze.
  2. Are you talking about the bar on the MCP or the button on the yokes (I use the captain side). I don't program the bar, but the code that was give above works for the button. The only thing it does not seem to do is activate the disconnect sound. Just copy and paste this code in a script and assign it: 1·(>O:YOKE_CONTROLS:BTN_YOKE_AUTOPILOT_DISENGAGE_PILOT_COMP:btn_yoke_autopilot_disengage_pilot_ButtonLocked,·bool) 1·(>L:btn_yoke_autopilot_disengage_pilot,·bool) 1·0·>·if{·0·(>L:btn_yoke_autopilot_disengage_pilot_HELD,·bool)·} (E:SIMULATION·TIME,·second)·(>O:YOKE_CONTROLS:BTN_YOKE_AUTOPILOT_DISENGAGE_PILOT_COMP:btn_yoke_autopilot_disengage_pilot_PressTime,·second) 1·(>K:AUTOPILOT_OFF) (WAIT:100) 0·(>O:YOKE_CONTROLS:BTN_YOKE_AUTOPILOT_DISENGAGE_PILOT_COMP:btn_yoke_autopilot_disengage_pilot_ButtonLocked,·bool) 0·(>L:btn_yoke_autopilot_disengage_pilot,·bool) 0·(>L:btn_yoke_autopilot_disengage_pilot_HELD,·bool)
  3. I'll check this. I prefer to work with the sim event ID.
  4. I was using the standard autopilot off too, but the autopilot off alarm did not sound and there was no need for a second press. Does your code above cause the alarm/notification to sound?
  5. This is what developer mode shows for mouse interact on the button on the yoke: (M:Event) 'LeftSingle' scmp 0 == if{ 1 (>O:btn_yoke_autopilot_disengage_pilot_ButtonLocked, bool) 1 (>L:btn_yoke_autopilot_disengage_pilot, bool) 1 0 > if{ 0 (>L:btn_yoke_autopilot_disengage_pilot_HELD, bool) } (E:SIMULATION TIME, second) (>O:btn_yoke_autopilot_disengage_pilot_PressTime, second) } (M:Event) 'LeftRelease' scmp 0 == if{ 0 (>O:btn_yoke_autopilot_disengage_pilot_ButtonLocked, bool) 0 (>L:btn_yoke_autopilot_disengage_pilot, bool) 0 (>L:btn_yoke_autopilot_disengage_pilot_HELD, bool) } I am trying to get it into a script. This has worked for other buttons in the plane. This case is the APP button. Apparently you have to sed a 1 to push in and a 0 for it to return to the out position. 1·(>L:B757_MCP_APP_BUTTON_PRESS,·Number)·(WAIT:100)·0·(>L:B757_MCP_APP_BUTTON_PRESS,·Number)
  6. I think your controller suggest fixed my issue. AAO was recognizing my headset as a controller. Blacklisted that and all worked well.
  7. I hit the Plus button. Select the Long click option. CTD. This is with the BB757
  8. Setting up Blue Bird 757. Two things happening. I save my current assignments to a template after every new assignment. After the AAO CTD the template does not appear in the last save condition. Last CTD I lost all work that I did this morning, about 7 new assignments. AAO has a CTD when I select LONG Press for an assignment. It has happened every time since I last updated to the mentioned version for MSFS 2024
  9. Yea. Being able to reduce the AP speed only was exactly what I saw. Nothing has worked for increasing.
  10. Ok. Went into developer mode and I learned an important lesson: I wish I was as smart as you guys. Here is what I currently have for a speed knob script: (L:FSS_EXX_FGC_ROT_POS_SPD,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_SPD,·Number) I have set this to my HC Bravo as a dual input with the right knob spinning to the right, button 12 and the assigned combo to button 16 (the IAS notch). I set the decrease script the same way except button 13 on the right hand knob. Speed does not move in either case. I have verified that this combo works with other scripts on other planes so it is not hardware. I also tried binding directly in the sim and I could not get that to work either. I took pictures of the mousereact from developer mode and my settings, but I guess the forum does not allow image upload.
  11. Oh yes. The dreaded extra zero. Old eyes. I still cannot get this to work creating changes in even 100's or 1000's. Not my script work. I got it from .to, but definitely not working "correctly" on my side. This is what I have for increase ALT: (L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number) It "works" but it will add some one hundred increments too. So it will go from let's say 0 to 1000 to 2000 then 2700 then 3700 then 15900 all the way to 39900 then 40000 etc. For speed: (L:FSS_EXX_FGC_ROT_POS_SPD,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_SPD,·Number). Does not move the speed at all. In either the "+" or "-" version of the script.
  12. Latest release and I am on AAO 4.60 b09
  13. I am not seeing any difference in the two scripts (one for 100 and one for 1000)
  14. Does anyone have scripts for the latest version of the Ejets? The ones on .to don't seem to be working any longer. Specifically, the ones for increase and decrease the altitude. This is the script (from .to that use to work). I have found no modification to make it work L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number) Not even sure what the 0.028 is for. They used it in all rotary knob scripts. The altitude version "works" but it does not land on either 1000s or 100s consistently.
  15. Is this still an issue today?

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.