Setup the CDU in the usual Boeing way, with your route and the SID's and STAR's at both ends, and then enter your performance parameters (it may be OK without the STAR, but this is how I have managed VNAV using the CDU at this time).

Configure the MCP correctly with RW heading and V2 + 20kts, plus the first altitude constraint in the windows.

Start your take-off roll, rotate as normal, and engage the AP during your climb out with LNAV and VNAV - the trick with the VNAV is to click the VNAV button but keep holding the mouse button down, then slide the cursor off the VNAV button, and only then let go of the mouse button.

Right, VNAV should be ON, and the CS777 should be on AP with LNAV & VNAV. VNAV may disconnect when you reach a constraint, so just re-engage it as above.

I had trouble with the rest of the climb, as the aircraft climbed far too slowly (500 ft/min), and the TOC was just a few waypoints before my descent. What I then tried was to cut the corner off the STAR (DCT next waypoint), and then enter your next step altitude or cruise level into the MCP.

I've tried this a few times with good success.

I'm asking others to see if this or something similar works, and for us to gradually get an idea of how to enable VNAV.

I believe VNAV works, but we have the figure out the tweaks to get it to work reliably for us.

Also, I use AS2012, and I had too much wing rocking, so I implemented the [custom autopilot] aircraft.cfg tweak with excellent results; change these values, but make backups first:
Custom Autopilot]
AP_Roll_speed=4
AP_Roll_window=7
AP_Roll_controlstep=1500

Finally, the aircraft hasn't changed its thrust rating from TO to CLB, but this can be done within the CDU thrust page by clicking on the LSK next to [arm] cruise. The CS777 will, however, change from CLB to CRZ. This does not stop the engines red lining, so look away, and remember that you won't be paying the maintenance bill.

Good luck, but please add your comments and ideas to this post.

I went through my setup again, and this time found a disco, which, when fixed, allowed VNAV to work again.

It seems hit and miss though, but I'm getting there.

I've completed three very nearly perfect flights in the CS777 today, and I think it comes down to very careful CDU setup and route planning. Make sure the waypoints and their speeds / altitudes are correct, and then be vigilant with the VNAV button, as this tends to disconnect during the climb as and when waypoints are reached.

I'm not saying that it's more difficult to setup than any other aircraft, but I double check my flight plans and entries, and I don't rely on on SID's / STAR's in case there's a clash, alt discrepancy etc.

I'm just beginning to really enjoy this aircraft.

Sorry Markoz, don't follow your post (re. fuel flow).
What I did discover is that engine start should auto-enable pitot heat, but it doesn't (CS said they'd try to implement this in time for the last update), and as there is no pitot heat switch, my Saitek switch panel came in very handy for the icing conditions that I encountered (which took out my airspeed and affected VNAV).
However, I'd prefer pitot heat to be correctly modelled.

That's interesting.

As part of my cockpit prep, I make sure that my Saitek mixture lever is full rich, then I make sure the fuel start levers are off. Then all will be well with engine start.

Does anyone else have issues with probe icing and anti-icing systems?

I was trying to figure out VNAV in this thread.