Is there anyway for me to  change the elevator  decrements to -0.003 ?

 

Thanks

Depends on how exactly you are doing it. Can you please post specifics? What are you doing how in which simulator with what aircraft that you want to change how?

10 hours ago, Lorby_SI said:

Depends on how exactly you are doing it. Can you please post specifics? What are you doing how in which simulator with what aircraft that you want to change how?

MSFS2020,  cockspur phenom 100. I'd like to be able to increase or decrease how big the increments are.

14 minutes ago, MindYerBeak said:

MSFS2020,  cockspur phenom 100. I'd like to be able to increase or decrease how big the increments are.

OK, but the increments of what exactly? There are half a dozen ways how the elevator (or elevator trim? What exactly are we talking about?) can be moved. It is also important with what device you are moving it.

Please post a screenshot of the actual axis assignment(s) that you have now.

 

Edited January 28, 20242 yr by Lorby_SI

8 minutes ago, Lorby_SI said:

OK, but the increments of what exactly? There are half a dozen ways how the elevator (or elevator trim? What exactly are we talking about?) can be moved. It is also important with what device you are moving it.

Please post a screenshot of the actual axis assignment(s) that you have now.

 

Sorry elevator trim. Yoke. Saitek flight pro

Edited January 28, 20242 yr by MindYerBeak

And how are you setting the elevator trim? Button or Axis, Variable or INC/DEC-Event or AXIS Event? And which one exactly?
Come on, you need to work with me here, there are always a million ways how things can be done with the MSFS SDK, and unless you tell me exactly what you are doing and how I cannot have an opinion about your original request.

In general:

• When you are using INC/DEC, UP/DOWN etc events assigned to buttons, there is nothing you can change or alter. They do what they do, they are assets of the MSFS SDK
• When you are using Axis events or variables, then bear in mind that there is a "natural" fixed ratio between the input from a joystick axis (0-65535) and the output going to the sim (-1.0 to 1.0 or -16383 to 16383). You can only change that by reducing the range on your joystick assignment (=pulling the blue triangles closer together) or setting a curve. This will affect the "increment", but you will lose range on the joystick. Not sure it that is what you are trying to do.

Edited January 28, 20242 yr by Lorby_SI

Ok for now, I use the hatswitch. elev_trim_dn/up, repeat-> fast/medium/slow.

 

What I'm trying to do is this.if you go here->  (from  min 38 on) you'll see the guy, he's using spad, changes the static value. This is basically what I'm trying to do but using aao

 

 

Edited January 28, 20242 yr by MindYerBeak

4 hours ago, MindYerBeak said:

he's using spad

I'm sorry, but I really don't have the the time to do any research on your behalf, especially when other apps are involvded. Either you tell me exactly what you are doing in AAO that you want to work differently - or not.

I've already written about the general principles of how the MSFS SDK works in my last post. The INC/DEC events do what they do, there is nothing to change, alter or otherwise influence. Whatever SPAD does is non-standard, their own internal logic.  The INC/DEC events are not AAO assets, they are "pure" MSFS SDK. AAO is essentially just a bridge between you and the MSFS SDK, nothing more.

If you require anything beyond what the MSFS SDK offers, you will have to use scripts in AAO. I suppose that it is not impossible to read the elevator trim AVar, increment it by an amount of your choice, and then write the result back into the variable. But you have to figure that out yourself, there are no parameters or "static values" in AAO for you to change (because one never knows if custom logic will work for a particular aircraft that usually has custom logic of its own).

The script would probably look something like this (this increments the elevator trim position by a tenth of a degree)
(A:ELEVATOR TRIM POSITION, Radians) 0.00174533 + (>A:ELEVATOR TRIM POSITION, Radians)

Edited January 28, 20242 yr by Lorby_SI

51 minutes ago, Lorby_SI said:

I'm sorry, but I really don't have the the time to do any research on your behalf, especially when other apps are involvded. Either you tell me exactly what you are doing in AAO that you want to work differently - or not.

 

I didn't ask you to do research on my behalf. I posted the YT link because I think I tried to explain what I was trying to with aao . (increase the size of the elevator trim increments). Even if i tried to xplain more than once you still asked me what it is that I was trying to do. I thought I was not clear enough so I posted a link with a video that shows what I was trying to do.Even if the vid was about spad it showed what it is that I was trying to do with AAO.

Edited January 28, 20242 yr by MindYerBeak

Quote

(increase the size of the elevator trim increments).

And again, that is not enough information. There are at least two different standard/SDK ways to do this, and probably half a dozen others. Unless you tell me how exactly you do it with AAO, I can't help you.

Option 1: use the Events ELEV_TRIM_DN and ELEV_TRIM_UP assigned to buttons => there is no way to change their behavior, they are MSFS SDK assets.
Option 2: use the Event "AXIS_ELEV_TRIM_SET" assigned to an Axis => there is no "increment", the whole concept doesn't apply here
Option 3: use the Variable "A:ELEVATOR TRIM POSITION, Radians" assigned to an Axis => there is no "increment", the whole concept doesn't apply here
Option 4: use your own scripts to increment/decrement trim - example has been posted above
Option n: custom logic in the aircraft in question. Especially with MSFS the aircraft are not relying on the SDK events and variables. It is very very common that the SDK events and variables do nothing and that you have to find a solution using IEs, BVars or HVars.

58 minutes ago, MindYerBeak said:

Even if the vid was about spad it showed what it is that I was trying to do with AAO.

And I have answered how this must be done. A script is the way to go. I am not going to watch that video, sorry. I don't care what other apps do or don't do, every developer has to find his own solutions in his own realm. 

As explained above, you cannot change the behavior of SDK events. So when you have assigned for example "ELEV_TRIM_DN" to a button, then it works like it does, there is no way (not even in SPAD) that this can be changed. You have to go around the MSFS SDK, find your own solution using a script. If SPAD already has the necessary code internally, then good for them. In AAO you have to do it yourself. I posted a sample script above what that would look like.

 

Edited January 28, 20242 yr by Lorby_SI