Searching the web for an example here.  Can't find anything.

I'm trying to set up the Condition Lever on the C208.  Gave up on trying to find an axis that works.  I have three keyboard commands assigned to "Cutoff", "Lo Idle", and "Hi Idle" which move the stick just fine.   Reading the manual,  it appears it is possible to use the "Enter virtual event" from an assigned axis to send a sequence of keystrokes to the sim.  The keystrokes I want to send are F1, F2, F3.   I tried hitting those keys in succession as the manual indicates but nothing is happening.   If I could just see an example of someone who has done something similar I would be most grateful.

The condition lever is controlled by a BVar that you enter into the variable box. I can post the specifics later

The C208 Condition lever should be this:

"Enter Variable" =  B:FUEL_1_Condition_Lever_Set
Axis Min = 0
Axis Max = 2
Rounding = int

This lever isn't really an axis, it only has three positions. But set up like this you can operate it with your hardware.

Edited July 25, 20232 yr by Lorby_SI

Thank you very much!

Well, no joy!

I pasted the BVar command into the variable field and the lever does not move.

 

Searching all the BVars I find "B:FUEL_1_condition_lever" and tried that one too.  Still no joy.

What is going on here??

19 minutes ago, snomhf said:

What is going on here??

Sorry, no idea. The BVar works for me, same setup as in your first screenshot. Do not copy&paste things directly from a website, there may be hidden characters at the end. Better to type them or to paste them into Notepad++ first, then from there in AAO.

Make sure to move the physical control through the full range. As I wrote above, the lever in the VC has only 3 positions, fully down, middle, fully up. You cannot set the lever in between those. 

The BVar must be written with the _Set ending, or it won't work. BVars don't have "fixed" names like LVars, HVars and AVars. Using it without the ending is for reading the value, adding _Set, Toggle, _Inc, etc.etc. is for writing.

And in most cases AAO can't find them, you have to use the MSFS developer mode (Tools->Behaviors, then click back in the sim and hover your mouse of the control you wish to investigate. Pressing Ctrl&G will bring up the behavior code, and around the MouseRect elements there should be the variables/events/scripts that one needs to operate the switch from the outside). Would be nice if all aircraft developers would publish what they did in their code, and what BVars, HVars and LVars have to be operated exactly how. But that is a rare thing.

Is that the default C208 or has it been modded?

Make sure that the lorbysi-content-hooks package is present and active in your community folder.

Edited July 25, 20232 yr by Lorby_SI

As for your initial question: if you are planning to use keyboard events, it is better to use scripts. That way you can be sure that your input is going to the app where you want it to:

(FOCUS:flightsimulator) (SPLIT:100) (VKD:29- 157-162) (VKD:56-184-164) (VKD:20-148-84) (SPLIT:100) (VKU:20-148-84) (VKU:29-157-162) (VKU:56- 184-164)

The "VK" codes are the scan codes from your keyboard. You get with the "Insert VKey" button on the RPN script editor. 

Edited July 25, 20232 yr by Lorby_SI

Yes, stock C208, no mods

Yes, lorbys-content-hooks shows in the community folder.  I guess it is "active".  How might I tell?

Good point about not pasting.   Typed it in carefully but no joy.

Yes,  I am moving through the end points and watching the Assigned Axis marker move the whole range.

Oh well.  Thanks for trying to help.  Not the first time I've been blacklisted.  Good educational stuff at least.  I don't have my SDK degree yet for sure.

1 minute ago, snomhf said:

Not the first time I've been blacklisted. 

Try running AAO "As Administrator". I can see in your screenshots that the two LEDs for the WebAPI are dark, and I'm pretty sure that in this condition BVars won't work at all.

 

Hell yeah!!

Ok, you've answered a question I had when I first installed AAO.   I went round and round about how to set it up and I ended up setting MSFS as administrator and put AAO in the exe.xml file thinking it would inherit admin privileges (thinking too much like a Unix programmer).  That obviously does not work.   I've gone back to starting AAO from the startup folder so it starts when Windows does since Windows will not allow an elevated program get run from another program.   That pretty much nullifies starting AAO when the sim starts.  Disappointing but whatever.

Thank you so much for working with me on this.  This has been a great learning experience!

Edited July 25, 20232 yr by snomhf

You can do it the other way round, make AAO start the sim. Automatically too. Options are in the Application menu.

The "other way round" is actually the RIGHT way I have found.   I never let AAO start the sim because I had the sim set for administrator and just assumed MS would not allow an admined program to be started from another program (thought that was a Windows rule).  However it works!  <Scratching me head>   After all,  you can't place an admined program in the windows startup folder and you can't run one from exe.xml.  I know that from experience.  

So, how do you defy the Sherrif like that?

35 minutes ago, snomhf said:

, how do you defy the Sherrif like that?

When you set the properties of both exes to "always start as admin" it should work with the exe.xml too.

As for AAO - it is only the App that needs the admin privilege, and it can of course start any other program in this elevated state. Nothing to it.

Edited July 26, 20232 yr by Lorby_SI