Since these new, slick & cool graphs have one drawback (no average line smoothing) I suggest that this trend line should be used to depict the value of RAC. It would be great if it could track historic changes of RAC, but this would probabbly add way too much load to database.
But even adding one straight line at the level of current RAC could add some usability to graphs. Why not give it a try?

First of all: it's not a trend line. A trend line would be very interesting to add as well, as it shows if you're improving, or leveling out. Basicly, a trend line is a straight line, no curves.

What you saw in the 'old' graphs is called a DeCasteljau/Bezier line.

About the idea: I have build no histories for RAC up till now. I can add this, but it'll take some time to show something interesting.

And should that be project-RAC, or BOINCstats-RAC?

whats the difference?

Project RAC stays like it is until the next credit is granted, so if you stop crunchuing it will never go back to 0.

BOINCstats RAC is calculated according to the formula in the FAQ here based on the real credit performance, and hence it's 0 for me @Seti, whereas the Project still has me on 20 since several month.

Always wondered that one thanks I would go for BOINCstats RAC then seen as though it reflects RAC more accurately (well my opinion anyway)

Forgot to state that: I second that!
I don't want to have my 20 in there were there's supposed to be a bid fat 0.

You're sure about this?
So how about this?

Perhaps some projects have done something about it, but it's not the stock setup. Look at my Seti, this still is 20, and the last WU I delivered was sometimes in January afaik.

I just saw my CPDN has vanished to 0 as well, and that's fine as I don't do it atm (my puter setup is too volatile), so they have done something as well.

I wouldn't mind, if they didn't... Because of my 0 RAC i am unable to post in the message boards of these projects :/

There is actually a standard script that updates RAC, however most of the projects do not run it because of the impact on the database.