Anyone got the idea how to ? 

 

Couldn't find any manual for this plane after purcahse.

You have AxisAndOhs, right? Then you can make scripts that increment/decrement any amount you want. FSS are using an LVar that contains the altitude value, and that can be incremented at will.

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·100·+·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·100·-·100·max·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·1000·+·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·1000·-·1000·max·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

 

Edited April 20, 20242 yr by Lorby_SI

Or use your own LVar to switch between 100 and 1000

Example:

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·(L:MyAltInc)·0·==·if{·100·}·els{·1000·}·-·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·(L:MyAltInc)·0·==·if{·100·}·els{·1000·}·+·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

And you set (L:MyAltInc) to 0 for 100 increments and 1 for 1000 increments.

1 hour ago, raam123 said:

Anyone got the idea how to ? 

 

Couldn't find any manual for this plane after purcahse.

On the top of the altitude selector the cursor turns into an upwards arrow. Click that, and then you can change in 100s. Back to 1000s with another click on the upwards arrow.

Also, the documentation is online:  https://docs.flightsim-studio.com/v/e-jet-series

21 minutes ago, Lorby_SI said:

Or use your own LVar to switch between 100 and 1000

Example:

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·(L:MyAltInc)·0·==·if{·100·}·els{·1000·}·-·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

(L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)·(L:MyAltInc)·0·==·if{·100·}·els{·1000·}·+·(>L:FSS_EXX_FGC_ROT_VAL_ALT,·Number)

And you set (L:MyAltInc) to 0 for 100 increments and 1 for 1000 increments.

All fixed ty.

 

20 minutes ago, Fiorentoni said:

On the top of the altitude selector the cursor turns into an upwards arrow. Click that, and then you can change in 100s. Back to 1000s with another click on the upwards arrow.

Worked as well ! Thx !

 

18 minutes ago, richbonneau said:

Also, the documentation is online:  https://docs.flightsim-studio.com/v/e-jet-series

Couldn't find it on the online manual....

 

Is there any LVAR list for the FSS ? So I can assign for example AUTOBARKES ?

 

Thx

Never the less I can't see FSS LVARs in AxesAndOhs any idea how to had them ? import script or something ?

13 minutes ago, raam123 said:

Never the less I can't see FSS LVARs in AxesAndOhs any idea how to had them ? import script or something ?

Careful with LVars. They are just variables, there is no guarantee that changing their value will do anything useful. With MSFS, try Input Events first (they are in the event group "MSFS Input Events" when you are sitting in the cockpit).

All others, BVars, LVars, HVars, if you know their names, you can just use in scripts, AAO doesn't have to know them in advance.
There is an option in the Scripting menu to read all LVars from the sim (just be aware that there are LOTS, as they are primarily used for animations and internal coding), or you use the MSFS developer mode "Tools->Behaviors". The latter has the added benefit that you can call up the behavior code for the controls in the cockpit by hovering the mouse over them and pressing Ctrl-G. Then look at the Asobo_GT_Interaction...LeftSingle/Wheel/Drag etc. which contain the code that you want to replicate in the app.

Edited April 20, 20242 yr by Lorby_SI

14 minutes ago, Lorby_SI said:

Careful with LVars. They are just variables, there is no guarantee that changing their value will do anything useful. With MSFS, try Input Events first (they are in the event group "MSFS Input Events" when you are sitting in the cockpit).

All others, BVars, LVars, HVars, you can just use in scripts, AAO doesn't have to know them in advance. There is an option in the Scripting menu to read all LVars from the sim (just be aware that there are LOTS, as they are primarily used for animations and internal coding), or you use the MSFS developer mode "Tools->Behaviors".

Ok, copied.

Any idea how to set the AUTOBRAKES using  : LVAR:FSS_EXX_AUTOBRAKE ??

n·(>L:FSS_EXX_AUTOBRAKE,·Number)

n goes from 0 to 4 for the 5 positions of the selector

The actual solution will depend on what control you want to assign to it (button, axis, rotary encoder..?)

For example, this script is a one button toggle that cycles through all positions of the autobrake selector

0·1·2·3·4·3·2·1·(L:FSS_EXX_AUTOBRAKE,·Number)·(L:EJET_AB_IDX)·8·iseq·(>L:FSS_EXX_AUTOBRAKE,·Number)·(>L:EJET_AB_IDX)

 

Edited April 20, 20242 yr by Lorby_SI

13 hours ago, Lorby_SI said:

n·(>L:FSS_EXX_AUTOBRAKE,·Number)

n goes from 0 to 4 for the 5 positions of the selector

The actual solution will depend on what control you want to assign to it (button, axis, rotary encoder..?)

For example, this script is a one button toggle that cycles through all positions of the autobrake selector

0·1·2·3·4·3·2·1·(L:FSS_EXX_AUTOBRAKE,·Number)·(L:EJET_AB_IDX)·8·iseq·(>L:FSS_EXX_AUTOBRAKE,·Number)·(>L:EJET_AB_IDX)

 

BTW why can't I find 

FSS_EXX_AUTOBRAKE

in AxesAndOhs ? I can see it in SPAD ... Can you advise please ?

26 minutes ago, raam123 said:

in AxesAndOhs ? I can see it in SPAD ... Can you advise please ?

AAO and SPAD are not related.

As I wrote above, AAO doesn't know and doesn't care about custom variables. As every aircraft developer can just invent them, there is IMHO no point in even trying. 
When you know their names, you can just use the variables in Scripts or add them to the database manually if you really want to. AAO doesn't have to know them in advance, they just work - as you can see in the scripts above.

If you insist on seeing a list of the LVars, use "Scripting->Read LVars from sim" in AAO. This will add all currently available LVars to a group called "Local Simulator Variables". Just be aware that there is A LOT of them. 

Using the MSFS developer mode / Tools->Behaviors / Ctrl-G method to find out about the actual control in question is way better. Mostly because LVars are not the recommended choice for operating controls - that they sometimes work is often more of an accident (again IMHO). Look for "MSFS Input Events" first, which are in the Event treelist anyway in a group of the same name (if the developer chose to implement them)

 

Edited April 21, 20242 yr by Lorby_SI