October 26Oct 26 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) AAL??? Mark "Crabby" Crabtree
October 27Oct 27 this code reproduces the dev mode code. interestingly I had to add the standard autopilot off event for the autopilot to actually disengage1·(>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)
October 27Oct 27 Author 4 hours ago, theegg52 said:this code reproduces the dev mode code. interestingly I had to add the standard autopilot off event for the autopilot to actually disengage1·(>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)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? AAL??? Mark "Crabby" Crabtree
October 27Oct 27 Commercial Member Are there no "MSFS IEs" / Input Events for this plane? If there are, you will see them in the behavior inspector too, and in AAO on the event selection dialog in the tab "MSFS IEs" LORBY-SI
October 27Oct 27 I can't get the autopilot button disengage button to work as well.Please help.I managed to set A/T , TOGA button , but can't set A/P disengage :-(
October 27Oct 27 And can someone explain what is 0.5 ? I can only set round numbers ? Gear handle positionWrite a detent position. Gear lock and aircraft logic apply.Read / Write0 = UP; 0.5 = OFF; 1 = DOWN
October 27Oct 27 Commercial Member 47 minutes ago, Raam1234 said:And can someone explain what is 0.5 ? I can only set round numbers ?No idea. What is this, where did you get this spec? Is it a variable, an event, from the simulators SDK, custom to the aircraft??And what do you mean by "set round numbers"? "Set" where?Edit: if this is supposed to be the simulator variable A:GEAR HANDLE POSITION, that would have to be either assigned to an Axis or scripted0 (>A:GEAR HANDLE POSITION, Percent over 100)0.5 (>A:GEAR HANDLE POSITION, Percent over 100)1.0 (>A:GEAR HANDLE POSITION, Percent over 100)At least in theory, I can't test it. I won't be getting the 757, sorry. Edited October 27Oct 27 by Lorby_SI LORBY-SI
October 27Oct 27 54 minutes ago, Lorby_SI said:No idea. What is this, where did you get this spec? Is it a variable, an event, from the simulators SDK, custom to the aircraft??And what do you mean by "set round numbers"? "Set" where?Edit: if this is supposed to be the simulator variable A:GEAR HANDLE POSITION, that would have to be either assigned to an Axis or scripted0 (>A:GEAR HANDLE POSITION, Percent over 100)0.5 (>A:GEAR HANDLE POSITION, Percent over 100)1.0 (>A:GEAR HANDLE POSITION, Percent over 100)At least in theory, I can't test it. I won't be getting the 757, sorry.It's BlueBird simvarshttps://support.bluebirdsim.com/docs/simvars
October 28Oct 28 Author 10 hours ago, Lorby_SI said:Are there no "MSFS IEs" / Input Events for this plane? If there are, you will see them in the behavior inspector too, and in AAO on the event selection dialog in the tab "MSFS IEs"I'll check this. I prefer to work with the sim event ID. AAL??? Mark "Crabby" Crabtree
October 28Oct 28 19 hours ago, theegg52 said:this code reproduces the dev mode code. interestingly I had to add the standard autopilot off event for the autopilot to actually disengage1·(>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)How do I impement it into my Lorby to work ? I mean where do I enter this code ?Ususally I use the + for add a new button then search for the LVAR
October 28Oct 28 Commercial Member 10 hours ago, Raam1234 said:It's BlueBird simvarshttps://support.bluebirdsim.com/docs/simvarsThe website says that they are LVars. Not a fan, personally, LVars shouldn't be used this way. As the developer rightfully says on that page "Use at your own risk". The correct way would be for them to implement InputEvents.Anyway, in the example that you posted, the three scripts would look like this:0 (>L:B757_GEAR_HANDLE_POS, Number)0.5 (>L:B757_GEAR_HANDLE_POS, Number)1.0 (>L:B757_GEAR_HANDLE_POS, Number)Small scripts like these you can enter directly into the button assignment. Switch the green button to MAN, select "RPN" and then copy&paste the code into the textbox. For larger scripts, take a look at the chapter "Scripting" in the AAO manual. LORBY-SI
October 28Oct 28 Commercial Member 4 hours ago, Crabby said:I'll check this. I prefer to work with the sim event ID.InputEvents and BVars are the official method for external controls. The aircraft developers implement them specifically for each model. Or they are supposed to. Don't disregard them just because the EJets got them wrong.I have yet to find even one aircraft where the default simulator (K:) events are even used properly. They somehow never caught on in the MSFS world, everybody was working around them from the start. Edited October 28Oct 28 by Lorby_SI LORBY-SI
October 28Oct 28 I managed to configure it all except for the autopilot button disengae :-(I'd really appreciate some hand here.Thank you !
October 28Oct 28 Author 6 hours ago, Raam1234 said:I managed to configure it all except for the autopilot button disengae :-(I'd really appreciate some hand here.Thank you !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) AAL??? Mark "Crabby" Crabtree
October 28Oct 28 Author 7 hours ago, Lorby_SI said:InputEvents and BVars are the official method for external controls. The aircraft developers implement them specifically for each model. Or they are supposed to. Don't disregard them just because the EJets got them wrong.I have yet to find even one aircraft where the default simulator (K:) events are even used properly. They somehow never caught on in the MSFS world, everybody was working around them from the start.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. AAL??? Mark "Crabby" Crabtree
Create an account or sign in to comment