Otto Groschenbügel

In the meantime, I re-installed AAO completely and it works now. And yes, this package is always present !! Thanks for your help !

After I upgraded to Axis and Oh's 3.20b43, the condition levers in the ATR don't move any more. (B:ENGINE_FUEL_Lever_Mixture_1_Set and 2) The axis sliders in AOA do move. In MSFS the AXISANDOHS FIP PANEL is activated and connected to AAO (no red border) I did "Read HVARS and BVARS from MSFSS" with MSFS closed. I just read in the forum that BVARS are now handled differently in 3.2. Is this the problem ? Or is there anything that I missed ? Thanks for your help!

Thanks for your hint! I had changed the WEBAPI ports. It works now! And also thanks for sharing your setting! 👨‍✈️👍

Something weird here: After installing 3.01 the Ingame Panel has a red border ALTHOUGH I run AOA in Admin Mode (the confirmation window opens when I start it). With the result that the condition levers don't work anymore. When I close the panel (not deactivate), the red border is still on the screen. I tried so far: Installed 3.00 again. Read LVARS and HVARS+BVARS after a new installation I'm a bit clueless now after trying this afternoon...

Ah, thanks for your help, its never too late to learn something new.

Thank you very much, this worked ! I wasn't aware of the inGame Panel, because I hadn't downloaded the latest PDF... Just one question, in the manual you write "BVars usually don't have fixed names in the behavior code, so they cannot be found "offline". You will have to use the Developer mode of MSFS to find out about these input events." Can you tell me where in I can find these events, once I have activated Developer Mode ? I searched all menus but didn't succeed.

I was aware that certain turboprops had problems with the condition levers. And I read somewhere that with one of the latest updates of MSFS, these problems had been solved. Unfortunately with the Analog King Air I bought lately, I can't get the condition levers to work with AAO. When I map them in MSFS with CONDITION LEVER 1 AXIS, they work. So I tried to find the event for them in AAO with "Watch Simulator Events". I got this one when I moved the Honeycomb Condition Lever: (K:AXIS_CONDITION_LEVER_1_SET) So I set up an Axis Assignment in AAO "With Select Event:" AXIS_CONDITION_LEVER_1_SET But the condition lever in the King Air doesn't move. Where is my thinking error ? Thanks for your help!

Yes, this would make sense ! Thanks for your reply

I have a question about the different procedures for battery start vs ext.power start: In the checklist for battery start first the right engine is started, for the ext. power start the left engine is started first. Is there a special reason for this ?

I am using AAO since I changed to MSFS last year (now V.281 b05). At the moment I use a Saitek Yoke, Honeycomb Throttles and CH rudder pedals together with an Elgato Streamdeck XL (without plugins, just with some programmed keys for the 737 MCP via AAO). In MSFS I have erased most control inputs except some keys for views. The problem ist that from time to time the yoke in the MSFS plane won't move. I then quit MSFS and start it again together with AAO. That's not very comfortable because of the long loading time of MSFS... Yesterday when flying the PMDG 737 this did not help at all. So I tried to figure out what the problem is. Changing USB ports for the yoke and restarting windows didn't help. Then I discovered that although the yoke doesn't move in MSFS, I can see in AAO the input from the Saitek Yoke moving as it should . So it looks like a problem with the connection between MSFS and AAO. Finally I figured out that I had to disconnect and connect AAO again. So no need to restart MSFS anymore. After that I could move the Yoke in the 737 again. But the Flaps lever didn't move any more. So again - disconnect and connect, this time everything worked except the left throttle. Again - right throttle missing. 😩 After the fourth try to disconnect and connect again all axis were moving in MSFS and the flight to Akureyi could begin... So I'm glad that I know how to solve the problem now but has anyone an idea what the reason for this strange behaviour could be ? Thanks for your help !

I have a small problem here with the automated insertion. When (in the programm) I choose a season manually, I can see that the relevant folder is created in my community folder. But when I enable automatic insertion, nothing happens, just the Model Assets and Islands and Boats appear and the manually created folder disappeared. I have already deinstalled everything, erased the documents/bijan folder and made a fresh installation but this didn't work either. Also tried to start the Bijan Season program with admin rights... Can anyone help ? Thanks in advance !

I also enjoy the new Caravan. Two minor things I don't like: The QNH setting on the altimeter is unreadable unless you press your nose against the panel ! And what I couldn't get the mixer/condition lever to work with the Honeycomb levers, no matter which variable I chose on Axis and Ohs. Any suggestions ??

I want to assign two keypresses to an unused axis on the Bravo Throttle Quadrant. When the lever is up, key "3" shall be pressed, when it's down, key "2" shall be pressed. I already assigned these two keys in MSFS to condition lever lean and rich, so when I press them on the keyboard, they work, the lever in the cockpit moves to the assigned position. So now I wanted to make two axis assignment, one for every button. I started with the "2", the assignment window looks like this: Select Axis, Event and Variable stay empty. Enter virtual key: 2 Device: Bravo Throttle Quadrant (.........) Move Joystick axis: RotationY Update Value: Continuously (also tried OnChange) Axis min: -16384 Axis max: 0 (the axis is calibrated from -16384 to 0, so that from the middle to the upper position, the value is 0) Assigned Combo: empty Unfortunately this does not work. Just to check, I also assigned "2" and "3" to buttons on the Bravo, this works. Even in this window I can write 22222 with the button, but not with the lever. I think I have an understanding error, can anyone please push me in the right direction ? THANKS in advance!

I 💖 the Analog Caravan, and after installing an anthracit cockpit mod all captions are much better readable ! Just two points I don't like: The altitude setting in the altimeter is difficult to read. I have to zoom in a lot to be able to read it (with 👓). Can this be changed with a future update please ? I use the Honeycomb Bravo with "Axis and Ohs" and it's not possible to use any of the mixture axis settings on the condition lever. I had no problem with the Kodiak which uses a similar 3 position lever. It would be fine if that could be changed in a further update. Have to close now, my Caravan is parket in Cusco and I want to make a flight above the Machu Pichu ruins...

I also changed from P3D to MSFS and didn't regret it ! I have a relative mediocre processor (i7-3770K) and a RTX 2060 but no stutters. I also had stutters but they were caused by one of the last windows updates that resetted the "number of cores used" setting in the configuration. After activating all cores again no more problems.