Transair

I use Spad to replicate checklist events. Pushing a button activates the C/L Menu on the FMS and the menu appears on the ECAM. Prior to updates 1.2.7 and 1.2.8, the Pedestal 'tick' and 'up/down' roller could be mapped onto buttons/knobs too. However, with the updates, now the checklist menu items will not scroll or show 'completed' with or without SPAD. I.e. the variables in the aircraft no longer work. Has this changed at all?

Yesterday departing LFPG in BAW 35K, I received a V1 call at proper speed (~150knts) and another V1 call just airborne (~160 knts).....not sure why the second one occurred..

yes, can definitely hear and they're quite loud - probably too loud!!

yes me too. Downloads to 1.24 GB and stops, then says Install, then it is disabled. When re-enabled, it says it is still on 1.0.4 and needs update.

I have found Flaps 2 does not emit a sound at all, whereas 1,3,4 do,

Orbx' not good?

Yes Impulse have this one their plan

hi Sorry no pics, but having set up Star/App into EGBB, the TOD kept changing every 1-2 secs between waypoints, and hence times to descent point. It seemed to be recalculating continuously, resulting in these variations. I elected to descend using the first TOD and the variations then stopped. (The second calculated TOD wouldn’t have worked due to distance required anyway).

Yes, can confirm I get a premature rotation on every takeoff now well ahead of V1. in the 900 or 1000..

1. I've also noticed that on winding down the altimeter to set descent target level, the TOD indication vanishes from both the FMS and the ND 2. I also get a 'Speed limit' row in the FMS which commands a higher level (in this case 10,000) in the midst of a descent profile having lower levels, so the aircraft climbs during descent. 3. In the attached, the FMS shows very low levels inconsistent with the STAR, so had to set VNav manually. 4. Despite update 1.2.3., there still seem to be numerous problems with the V Nav. Hopefully this is getting extensive, urgent treatment!!

yes...totally agree with this....happened to me on two successive flights today.

Had my first WASM crash last night for ages after being airborne 2 1/2 hrs in A359 SQ, Inibuilds livery, while inputting Transition point into FMS after STAR/RWY…….sorry no files to attach….. Each of my WASM crashes has occurred during data entry into the FMS if that’s of any use to you..

maybe some connection with the TM. I had this with the TCA which went berserk flying the 350. So I disconnected the USB, then re-connected, and into a different port. No trouble ever since - poss dirty/poor connection. try that..

ok...just a long shot. Using GSX sometimes causes this, and all that needs to be done is to stop Coutl. OK in your case. Does the thrust increase if you power up?

did you use GSX to push?