Ah, OK. The answer is now: yes you can but not easily . First some background.I guess what I'm asking is, how do I adapt the pitch, roll, and yaw values in the flight plan to attitude mfd.
Attitude MFD only supports a limited number of reference attitudes:
1. Attitude (inertial reference frame aligned with Orbiter's global frame)
2. Velocity (rotating reference frame aligned with velocity vector and orbital angular momentum vector)
3. Target (rotating reference frame aligned with target vector and local horizon*)
4. Entry Interface (inertial reference frame aligned with the velocity vector at predicted entry interface and orbital angular momentum vector)
Apollo used a number of inertial reference frames called REFSMMATs (Reference to stable member matrix). These were typically aligned with the target spacecraft attitude at certain critical events. For example, at lift off they used a REFSMMAT that was aligned with the target orbital plane and the local horizontal at the targeted liftoff time. At LOI, the REFSMMAT was aligned with a retrograde attitude at the targeted LOI TIG. This made it easier for the crew to read off any attitude errors from the FDAIs. (Read more about REFSMMATs here: http://en.wikipedia.org/wiki/Refsmmat)
Apollo REFSMMATs can be simulated in Attitude MFD by going to Attitude mode. If you know what the orientation of the REFSMMAT is to the Orbiter global frame than you can enter that in for the attitude offsets (Set Pitch etc) in Orbiter and then read your attitude relative to that from the attitude errors lower down on the MFD page. TBH, I don't know of a source that lists the orientation of the Apollo REFSMMATS with regard to any particular inertial reference frame. I expect that it could be determined from the flight plans and the angles to the navigation stars. The Project Apollo guys would know more about that from their work with the Virtual AGC (you can do fully simulated REFSMMAT re-alignments with it). I've done it before and, if you are looking for immersion, I strongly recommend it. Very cool stuff.
HTH.
*Not 100% on this one since I have looked at that bit of code for a while, going from memory.