TeamFirstly, i couldn't find any notes / posts on the above.I will also only make it a short note as i continue to log any further examples ... given i have only done about a dozen flights so far (waited for SP1). Flying KJFK to KDORD, before TOD, I selected an RNAV28 Approach from the PAITN star. This Star has a few (real world) speed & altitude restaints not included by Navigraph.I thus made (& apparently had accepted ??) those vertical revisions but the VNAV Path did not recalculate. The FMC kept the original constant descent profile to the Approach IAF that it calculated before the revisions.I completed the flight using V/S and Speed.The next time I flew the same route, I selected the ILS28 Approach (which has the same transitions, fixes etc. as the RNAV) and the same PAITN STAR, then added the vertical revisions to see the revised step VNAV Path correctly calculated. This flight I completed in VNAV Path mode even the approach.So somehow, selecting an RNAV seems to interfere with calculation of revisions to the STAR.Has anyone else noticed / have advice on this ?

There was another thread where folks were having problems on STAR's with more than 4 fixes. I'm having problems as your are with the TOD not changing after adjusting altitude constraints, etc...I'm flying more often with FL CHG and V/S since the VNAV is so unreliable. Unfortunately, this is one giant wart on a great addon.

Before I go "The problem is on your end", the more than 4 fixes thing never applied here. Just to check the OP's problem, I tried a rnav approach to Guarulhos SBGR, via Poços 12 Star connecting with Rnav 09 procedure, and everything went by the book. And just to mention, it the star has more than 10 fixes and lot's of soft constraints. Maybe, I say again, maybe, whatever revisions you intend to make so the star matches it's real life counterpart, do it before the TOD. And also, before the TOD as well, fill in the forecast page, that always helps the FMS to calculate a nice descent path.Fly safe.