Hello, Tim.

The last thing I want to do is to park this aircraft on hangar forever and I have to last assure there is no interface problem - that one between pilot seat and yoke.  8-)

For example, now I can deal quite well with descent speed as I noticed that flaps 1 can do much better than speedbrakes (that is ineffective, as I stated before). But this is another thread.

There is no reason for, when you choose an ILS approach, as per manual example, to FMC modifies speeds and altitudes, and not giving you the waypoints expected for that specific landing.

I've made this procedure with many other add-ons literally dozens of times and no one does this. It might be a bug on this aircraft.  :(

And, yes, you may insert some extra waypoints and the FMC shall accept them normally, specially if you set altitude/speed constraints, not doing a mess that we can see on this aircraft.

Example: I made my approach to KDFW by south to land on RWY17L and I could not choose ILS17R approach as FMC did not set the waypoints for this landing.

So I chose 17L - just the runway, and FMC set correctly waypoints, altitudes, speeds. When checking route (plan mode) you can see that you get a very 'tight' base leg, just inside the glide. So I inserted two more waypoints north inbound, to have enough room for wind leg, base leg and align.

When you do this, FMC shall accept the new waypoints and, until you make manual changes, it recalculates automatically speed and altitude to fit with original approach.

At this time, FMC deletes approach waypoints and set cruise speed and altitudes.  :o

There is no reason for that and, believe me, although I learn new things every day I am really confident on using FMC.

Cheers

Schmid