ArkRoyal

Never mind 'chase plane', I want the Tower View back.

Slightly OT - but was there any improvement/corrections/modifications to the generally poorly received and criticised World Update Italy and Malta?

Completely agree withe the OP. I was astonished the tower and/or flyby views were not incorporated into the original release - and even more so that it now doesn't feature in any of the Asobo 'to do' lists.

You can't see it in the sim but behind the column is a bar that is levered up (manually) to the horizontal and its forward end is lodged (pushed) into a receptacle, for want of a better word. It locks the control surfaces. To release, the column is pulled and the bar drops. Just Flight has simulated this by a click spot which is the hand-held mic on the front of the column, half way down. A click there will either engage or release the lock. When viewing from outside, don't expect to see the control surfaces moving massively. The 146's control surfaces were moved via trim tabs and while their movement can be seen, you have to zoom in to see them moving.

Let me assure you all that the FMC's speed control in 'the real thing' is far from perfect and one has to keep a constant eye on the ASI. However, it handles altitude restrictions pretty well but only, of course, responds to what has been programmed - hard altitude restrictions have to be complied with but there are lots of places where you can tell the aircraft what height/speed you want it to be at to make the approach more manageable. Returning to the sim aircraft, I have had altitude busts by 2-3 hundred feet at times and they haven't been coming from either high climb or descent rates or excessive speed. PMDG need to make some mods to the FMC, without doubt.

Thank goodness, a voice of sanity!

Of a Boeing - never!

'Based on feedback received from players, the team has made a reduction to vegetation density to a more realistic representation of tree size for all Italy photogrammetry cities impacted by the issue in World Update IX.' ...............which begs the question: did none of the 'team' look at their production before release and realise they had messed up the vegetation density?

FCTM: 'Autothrottle use is recommended during takeoff and climb in either automatic or manual flight. During all other phases of flight, autothrottle use is recommended only when the autopilot is engaged in CMD. During engine out operations, Boeing recommends disconnecting the autothrottle and keeping the throttle of the inoperative engine in the CLOSE position. This helps the crew recognize the inoperative engine and reduces the number of unanticipated thrust changes. Note: The autothrottle logic on some airplanes allows the autothrottle to be physically connected during engine out operations.' The document also states ad nauseam to make the point: 'The autothrottle should be disconnected when the autopilot is disengaged.'

Assuming a coupled ILS approach, at 1000' you should be 'stable': landing flap (30 under normal circumstances), gear-down, speed (if not at, then within 10 kts) of Vref +5 (let's not complicate matters about Vapp) and thrust as per the autothrust (55% N1 is a good ballpark setting), landing checks complete. The aircraft will have trimmed itself out and on disengaging autopilot and autothrust, (on a still day) it will almost fly itself with just minimal control input required.

IKOMA NORTH from ROKKO IKOMA EAST from ABPUK

I had it yesterday - and today it's disappeared along with the program not launching.

No - but in the 'real world' on a busy ATC frequency, it's often the case that you have to get your request for descent in a lot earlier than waiting until the T/D. Sometimes you are not able to get a word in edgeways and go sailing past the T/D. On other occasions ATC are unable to give you descent clearance so the general rule of thumb is 'get your descent request in sooner rather than later' - so if you do get it ahead of the T/D, start descent in either Descend Now or Alt Intvn.

I apologise in using 'sloppy' terminology; it should be Top of Descent (T/D) in the cases as given. Descent Point is more pertinent to terminal procedures rather than leaving the cruise phase. It is shown on the map as a green, open circle labelled T/D. With a VNAV path descent planned, VNAV starts an early descent at 1000 fpm and captures the idle descent path. VNAV uses FMC SPD for the autothrottle mode and VNAV PTH for the pitch mode.

Thanks for the pointer - it seems I/we are not alone. Why on earth, after all this development time by PMDG, haven't they offered a customised set of commands - or is it Asobo displaying Gallic stubbornness?

It's probably me - but is anyone else having problems binding any of the Honeycomb yoke and quadrant switches to any of the 737's switches and systems? The only ones I've managed so far are the flight controls (primary and secondary), thrust levers (minus reverse thrust) and some views. Autopilot functions appear to be OK but lights, battery, APU start/stop, Eng Anti Ice etc don't seem to be able to be bound. As an aside, the MSFS systems options appear to be sadly lacking compared to the myriad of those found in X-Plane.

As noted in a previous post - the SOP is 'Gear Down - Flap 15' then bug the 15 speed; no more gear warning horn.

2000 hrs 737 says: 1. Use 'Descend Now' around 10 miles before DP (dependent on wind) to ease the aircraft into the descent at 1000fpm. 2. If descent clearance has been given and set, aircraft will start descent at the DP (with VNAV engaged). 3. Missed the DP and haven't set a lower level: Set lower level, LVL CHG and Speedbrake to regain the descent profile. VNAV in real life is far from perfect and 'Drag Required' will often display.

if you are referring to avwx.info site, I've not been able to access it for several days.

I've downloaded the Xbox App and the sign in email for that is using the same as the purchase from MS. On the MS Store I have a 'Microsoft Flight Simulator' update of 509.8 MB - is this it? Or am I downloading a fresh MSFS for an Xbox I don't possess. Pee up in brewery doesn't come close!

I''l bump this thread. I've just installed MSFS from the Store and have to turn off AVAST in order to start the program. AVAST shows the offending .exe buried away in \GLOBAL ROOT\Device\Harddisk Volume20\Flightsimulator.exe. I've tried to add exceptions the usual way - both AVAST and Defender appear incapable of registering this. I'm also amazed that AVAST has not cleared this .exe as a 'clean' as there must be tens of thousands of AVAST clients MSFS. As an aside, since installing MSFS, my Windows 10 fails to boot first time and has to be brought into life via the reset button.

Vici, vidi - and I've still not downloaded it. I cannot comprehend the incompetence of this development team in their releasing manifestly untested 'updates' that do everything but actually 'update'. It seem pretty obvious that SU5 was a botch (read dumbing-down) to degrade the PC version to allow the X Box launch. That smacks of pen-pushing accountants driving the agenda - which in turn leads to the question as to what kind of regime Asobo is having to work under when quality is sacrificed at the altar of shot-term financial policy.

Loved the shot from street-level between buildings of the 747.

Many thanks to all of you who have replied. I'll give the July update time to bed down and if nothing gets broken I've got a SSD ready and waiting.

I have resisted buying MSFS. I've seen so many new programs have so many problems for months after launch that I decided to sit back and watch the ensuing mayhem - of which there appears to have been much. However, things seemed to have settled now and with the much-heralded performance improvement coming at the end of the month, will it be time to take the plunge? An additional question: if I purchased MSFS after this update, would the download come with this update included along with all the previous updates - or will they all have to bee downloaded separately?