I think the Apollo missions are in some dire need of improvement to the logic of what is highlighted when a checklist has been "RUN". There's so many items during the academy lessons when you run a checklist that say to "verify..." or "check... is set to..." and nothing is highlighted. When you're first learning the spacecraft, you need more direction as to where to look to verify values. These checklists assume you know where all the gauges and meters are. There's also a lot of instances where the checklists tell you to arm something or verify that something is armed, RHC and THC for example, but again don't show you where to look to do this. Lots of steps in these Apollo checklists need to operate as they do in Mercury and Gemini. It's the biggest game inconsistency that I've noticed at the moment.
#Apollo Checklists and Paperwork Improvements
tawny pelican
strange lotus
For me the Entry PAD suggest to autofill when i received the data from ground. Make sure you clear the form before clicking it though.
tall loom
There is a autofill feature for pads if you don’t understand how to read them or just want the info filled out Instantly
tawny pelican
I must have missed the auto fill feature. I didn't see it when I was running the scenario, will look again! Thanks!
queen bobcat
Every pad has this little button "autoplot" at the top right (in case you have trouble finding it)
somber agate
No I agree. There needs to be more direction on where yo look on what to monitor and maintain
uncut sorrel
I think the Apollo missions are in some dire need of improvement to the logic of...
I totally agree. There are too many exceptions and different ways of describing operations and commands. Sometimes AGC interactions are described key-by-key (annoying) other times as a single instruction (better, but no automatic progression after operation executed). Many checklists are way different between interactive run mode and mission pad written version. Usually the written version is way more clear and discoursive, easier to navigate. Sometimes they are totally incongruent between each other and many steps are just skipped in the interactive version.
One example is the P40 checklist. (I only figured the right procedure after maybe 10 executions) only to discover that SPS Deorbit & Entry (used in one academy lesson), while contains the P40 entire procedure, it just skips some steps. The first time was very confusing and the gimbal motor didn't set up properly. I had to execute the plain P40 checklist instead of the one suggested in the lesson
tawny pelican
It's really just a matter of consistency and commonality through every space craft. Base functions all work very well, just needs some tweaking!