I continue to have problems with this software. I have purchased the new honda jet.So ,with aao,heading works, vs works, altitude even with 100 or 1000 to the side of the box does nothing at all. Aileron and elevator work. Throttle does not work at all.Nada. So i tried removing the default sim assignments and tried using aoo.nothing. I tried using "select simulator event" no luck.I tried using "select simulator axis" and again nothing. I mean AOO sees the throttle  as a matter of fact I see the numbers going up and down below the "move joystick axis box" but it does nothing in the sim. If I choose throttle1 from the "simulator axis" and push the throttle  all the way forward ..the engine goes to 50% or so and comes back down to 0% right away.  I checked the manual  but I'm not any wiser ?

It is not possible to control everything from the outside, and the aircraft developers in MSFS are keen on implementing their own logic, bypassing the SDK and the default events, thus preventing any structured, pre-coded approach.

The controller assignments in the sim and what "the software" can do over the SimConnect API are not the same things. They should be, but they aren't. The sim logic naturally has direct access to the internals, while the API can only do what Asobo has implemented into it. This used to be the same in the old sims, but it is not in MSFS.

Combined with the fact that the aircraft developers don't care/ forget about external controller apps and/or don't publish instructions of how to access the knobs and levers, we as the end users are stuck in a vicious cycle of constantly trying to figure out how the heavens things work in every new plane. That is not how it should be, iMHO the developers should feel compelled to publish specs about how to operate things, at least for payware. Or go all the way and add a bit of behavior code to make that easier (likre Aerosoft did)

As for the HondaJet: none of the SDK throttle axis or events work. None of their LVars related to throttles do anything useful. I have no idea how we are supposed to control them, plus, the behavior files are encrypted and I can't look any deeper. From the looks of it, there is a behavior update script running in the background, that does "something" with the throttles. What the purpose is and what it expects us to do, I have no idea. Probably some kind of FADEC simulation?

Haven't looked at the other knobs yet, but I suppose they will be as problematic as the throttles are (BVars probably).

 

Edited June 2, 20224 yr by Lorby_SI

10 hours ago, MindYerBeak said:

I continue to have problems with this software. I have purchased the new honda jet.So ,with aao,heading works, vs works, altitude even with 100 or 1000 to the side of the box does nothing at all. Aileron and elevator work. Throttle does not work at all.Nada. So i tried removing the default sim assignments and tried using aoo.nothing. I tried using "select simulator event" no luck.I tried using "select simulator axis" and again nothing. I mean AOO sees the throttle  as a matter of fact I see the numbers going up and down below the "move joystick axis box" but it does nothing in the sim. If I choose throttle1 from the "simulator axis" and push the throttle  all the way forward ..the engine goes to 50% or so and comes back down to 0% right away.  I checked the manual  but I'm not any wiser ?

I am having the same issue using FSUIPC.  It has to be something with the HJet but not sure what as the throttle wotks fine with the Cessna jet

LouP

Got the throttles working using RPN scripts in AAO and two LVars:

Script Group: Honda

Script Name: ThrottleOne
Script Code: (L:Honda-ThrottleOne)·100·/·(>L:THROTTLE1_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

Script Name: ThrottleTwo
Script Code: (L:Honda-ThrottleTwo)·100·/·(>L:THROTTLE2_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

Be mindful that in AAO the script group name and the script name must be exactly as I specified above or the scripts won't work. The reason is the script variable at the beginning, its name is "L:scriptgroup-scriptname". 

Edited June 2, 20224 yr by Lorby_SI

I've got the scripts built but I'm missing something.  Can't get it to work. Can you elaborate on which axis to set up with 0-100?  "Throttle1_Set"?  Did that and it doesn't work.

No axes set up in MSFS2020, FSUIPC not running.

Thanks.

 

4 hours ago, halobiont said:

I've got the scripts built

How did you do that exactly? The most important thing is that the group and script names must match mine exactly, including upper/lower case, otherwise the scripts won't work.

Then the script itself is assigned to your physical axis on the Add Axis dialog, using the second box from the top. And there you set Axis min to 0 and axis max to 100. These values determine how the input value from your physical axis (0-65535) is translated before it is sent to the script.

Edited December 2, 20223 yr by Lorby_SI

Thank you!

That prompt did the trick.  I didn't understand that I was to assign the script via the add axis dialog.  I thought just having the script in place and assigning Throttle_Set would work.  It's working now.  Thanks again.

Doug