Perhaps it's already been answered, but I couldn't find an answer, so I'll ask anyway.After the initial descent, the FMC will calculate a constant descent for the rest of your route. So, for example, if I'm told to cross such and such fix at FL240 the first step down from cruise to FL240 will be, ideally, a N2-idle descent, right? And then if the next expected crossing restriction on the route is 10,000, the VNAV profile will set a constant descent from the FL240 point to 10,000, regardless of how shallow the descent might be? Is there a way to override this and ask the FMC to compute another ToD?In my first several flights I'm finding that ATC (VATSIM) give me descents to FL240 to switch me over to the low altitude sectors, who then give me the crossing restrictions. ATC is planning on leveling me off at FL240 for the hand off though... meanwhile I'm overshooting the planned VNAV profile. After being cleared for the descent, "George" races down to catch the profile then shallows it out to a long, torturous 500fpm descent. I descend faster in my little Piper Archer!Thanks in advance guys, I'm sure this is one of many silly questions to come from me. 5 days, about 15 hours in the plane, and I'm loving every second of it!Steve Perry

Steve,You've found the main reason why VNAV isn't always the best A/P mode to use for your descents. The FMC computes the VNAV path in a perfect world (without ATC) and no delays. ;-)For descents where ATC instruct you to level off at different altitudes for hand-offs and such, I would chose another mode for my descent. I would go with a VNAV path descent to my first level off. From there on I would possibly use V/S and my SPD to keep ATC happy during my continuing descent.Hope it helps,