After the release of SP1 (v1.10) of Aerosoft AirbusX Extended, flaps cannot be set to 2, 3 or 4. (they work for 1)

 

Steps to reproduce:

 

- have flaps in 0 or 1 position (or 1+F)

- say a simple command "flaps 2" or "flaps 3" or "flaps 4"

 

Behavior:

- the FO will normally acknowledge

----> if at 0 -> flaps will go to 1+F

----> if at 1 (or 1+F) -> flaps will not be changed

 

Expected behavior:

- flaps should go to the commanded level (2, 3 or 4)

 

 

 

PS: My guess is they changed something at SP1 regarding the 1+F position (perhaps an extra intermediate value of the variable) and that messed up things.

 

Of course, everything worked fine before SP1.

 

After the release of SP1 (v1.10) of Aerosoft AirbusX Extended, flaps cannot be set to 2, 3 or 4. (they work for 1)

 

Steps to reproduce:

 

- have flaps in 0 or 1 position (or 1+F)

- say a simple command "flaps 2" or "flaps 3" or "flaps 4"

 

Behavior:

- the FO will normally acknowledge

----> if at 0 -> flaps will go to 1+F

----> if at 1 (or 1+F) -> flaps will not be changed

 

Expected behavior:

- flaps should go to the commanded level (2, 3 or 4)

 

 

 

PS: My guess is they changed something at SP1 regarding the 1+F position (perhaps an extra intermediate value of the variable) and that messed up things.

 

Of course, everything worked fine before SP1.

 

This has been reported by many users via e-mail.

 

Now fixed in latest build uploaded today.

 

There are also improvements to Radar Contact interfacing.

 

http://www.multicrewxp.com/Downloads.html