Well, I just reinstalled the 767 and took it for a 1-hour test flight from Sydney to Melbourne without my joystick, and it cruised along at FL360 with no problems.  It did shake a bit during the climb, but I'll attribute that to turbulence from ActiveSky.  However, I did notice a few problems, particularly on the arrival.

1) I could not get the software to apend the STAR (LIZZI 7A ILS-Y 16) to the route after ML (I would copy LIZZI over to where it appears on the airway after inserting the STAR, as I do on another company aircraft).  I eventually had to manually program the waypoints.  By setting the altitude restrictions as published, I was able to create the T/D (which was not present on departure), and VNAV took me down as expected.

2) When it came time to intercept the ILS, the aircraft completely missed the glide slope.  I had to do a FL/CH just to get me down low enough to capture it from above.  Once established, the aircraft could not seem to maintain the approach course and slope, with wild deflections both vertical and lateral, even though it was on all three autopilots and LAND3 was armed.  Since I did not have my joystick (it's coming Tuesday, just in time for CTP :P), I pretty much relied on autoland to take me down - which it did, but poorly.  It might be a result of my system's piss-poor graphics handling (<15 fps in the default trike with default scenery), but the fact that other payware aircraft (another company, Airbus X, and another company E-Jets) perform auto-landings flawlessly makes me believe it's a fault of the CS aircraft itself.

3) The FS Tooltip On Stab Trim bug persists.  When I set my trim to 1.3 at the start of the flight, the tooltip registered -7.2, the STAB TRIM light on the overhead was illuminated until I engaged the left autopilot, and the TO CONFIG WARNING HORN sounded as I advanced the throttles for departure with the message STAB TRIM.  This problem applies to all CS aircraft I own or have owned (757, 767, and 777).  It may be related to the fact that my OS is Win7x64SP1.  I'd appreciate any help in fixing this problem once and for all.  I really don't want to give in and leave the trim at its default value as Markoz suggests.

4) At this point, I'm nitpicking, but I'd really like it if the dials worked as expected.  On other aircraft I'm able to operate the dials using my mouse wheel.  When I roll my wheel up, the dials turn clockwise, and vice versa.  This allows me to quickly set altitudes, headings, speeds, frequencies, etc.  On the 767 and others by CS, the mouse wheel only turns dials in one direction: counterclockwise.  And once they start, they're hard to stop.  The only way to reliably set the MCP is by clicking and holding as the altitude bug slowly climbs from 5000 all the way up to 36000, 100 feet at a time.  I really wish CS would fix this, as it has been bothering me for over a year now, same as the tooltip bug (#3).

If this post is better placed in its own thread, please let me know.