I have often seen complaints here about the inclusion of STARS into an FMC and RC not following them. I have also seen Doug and JD's, and John's) responses that when Approach starts vectoring the STAR "authority" is ended.I have just watched some real world cockpit flights 737 and 757/767 DVDs from Just Planes namely Belair and Hapaag-Loyd Express.Mainly that's the way it is, folks! The pilot starts cranking the A/P (or MCP) altitude, heading, and speed controls which then dominates the FMC (unless you are deviating from accepted parameter limits) and the FMC will update accordingly following your input. I noticed on the EHSI the deviation from the displayed planned track.I have just ordered the two sets of PMDG 737 products and in preparation have read (downloadable from their site) the guide .zip which includes the FMC, take-off, and landing procedures guide. They have set up the FMC to disengage command of each mode as you start to turn the appropriate control.So, I would look ahead if possible at the FMC STARs for the destination airport and enter the expected one based on the anticipated runway into the flight planner that generates the RC .pln file. For VNAV discrepancies (discussed in another thread) fly destination NOTAMS mode but having an arrival chart is a must have, at least the IAP chart showing the MSAs.The RC approach seems real world to me and with the AI pattern sensing coming in V4 to determine the active runway so as not to cause conflicts makes it world class.Just a comment here to those complaining about RC/FMC coordination.

did you get my email that i sent to your email address on record with us?jd

>>The RC approach seems real world to me...;)

I got a message 9/15 quoting and stating a message was in my AVSIM in-box. Nothing was there but the message was quoted as already in V4 plus xxx.Funny delivery service :).Is this what you are referring to? My address has not changed and nothing came direct from you.

send me an email, and i will reply with my message. [email protected]

Done.