balus

Has anyone else had issues with a low initial altitude followed by a large STEP climb? On a flight out of EGLL, with an initial altitude of FL230 followed by a STEP to FL350 after DVR. The aircraft climbed OK to FL230 but then ignored the remainder of the STEPs. I retried the flight with an initial altitude of FL330 and it appears to be climbing ok. EGLL/27L N0419F230 DET2G DET L6 DVR/N0489F350 UL9 KONAN UL607 KOK DCT MATUG DCT BOMBI DCT TENLO DCT DEXIT DCT BEGLA DCT DEGET DCT SOKRU/N0490F370 DCT LUGEB DCT UDROS UM859 KARDE UL851 TBN UM11 REBLO P130 MAMED B449 RANAH/N0484F390 L750 MERUN G452 LKN R460 CEA L507 IGONI DCT WILLA WILA2C VTBS/19 FL STEPS EGLL/0230/DVR/0350/SOKRU/0370/RANAH/0390

Now that's a bit better, still got a stray jetway though, at 555 in from KMIA.

Just removed and reinstalled EGLL and the GSX profile and it seems to be working.

Sitting at gate 307 at EGLL and trying to connect jetways I get an error, see attached - doesn't matter which door or jetway I choose, none of them work.

thank you, I was going around in circles looking for it.

yes, see my response to Kyle

Just had the time to try again with an autosave, double checked that pause at TOD was enabled, same deal, straight past TOD and ended up circling the destination at FL400. Flightplan is WSSS/02L AROSO3E AROSO Y513 KALIL Y501 RINBA Y503 VPL P628 RK G202 ZB L750 RANAH B449 ETRAP B447 KRS B143 TUNEK A909 RODAR M11 REBLO UM11 CRM UL746 ODERO DCT OPT DCT SOKRU DCT BEGLA DCT DEXIT DCT INBED DCT BOMBI DCT ADKUV DCT SOGRI DCT DENUT L608 LOGAN LOGAN2H EGLL/27L and I added waypoint RICHY after LAM to setup the approach to 27L, no disco's

I'm going to restore the oldest autosave later today and see how it goes.

Just had a totally unsatisfactory flight, STEP climbs were ignored as was the pause at TOD, even though both options were selected. Was operating a 12 hour flight at 4x and came back to the computer and was circling the destination at FL400.

But it only reacts to a mouse click, not a key - and yes I thought about the view selection keys, but it works now, without changing anything. I checked the mouse left click and yes there are 2 interactions bound to it, but that's the same with all other aircraft, and I don't have the same issue with them. I also created a new mouse profile and cleared everything, same issue.

Ok, I may have resolved this, but I'm unsure as to how. When I load a new aircraft the first thing that I generally do is define camera views and then use the ALT key to access the views. For the lower part of the pedestal I generally use ALT4. While trying to work out what was happening I used the CTRL keys to select a view and then zoomed out and navigated down to the SD controls and clicked on one of them, no pump failure. So I then hit CTRL+ALT4 to reset the view and it seems to be working. I want to do a restart and another flight before I am convinced - I'm currently enroute to KDFW from YSSY, so I've had plenty of time to experiment :)

But how, no keys or buttons are being used simply a mouse click? And it is only the SD control section, mouse clicks anywhere else function as expected.

Thanks for your opinion, however it is not really relevant to the issue being discussed.

I have noticed this when switching views - from external to internal for example, they only stay on for a couple of seconds though.

Neither do I, are you having the same problem?