First off, the help text was well-appreciated (although the html table of the digits needs to be fixed, otherwise the table 'wobbles' when numbers change a lot)
[x] spacesim members noted that the numbers in the text display have too many significant digits, although they also noted that they would sometimes need a bit more accuracy. But most of the time, lots of wildly-changing numbers is a readability issue. Maybe bigger numbers? We'll have to investigate what legacy orbit/KSP do.
[x] spacesim members noted that there was a lot of whitespace. Once we fill in more text fields, we should check the general clutter and figure out how to sectionize the GUI text fields.
[x] Spacesim members were confused that headings are taken relative to Solar west, instead of e.g. pitch above the reference object.
[x] Heading can't get higher than 360 (well only for a frame or two) but it might be able to get very negative
[x] Spacesim members at this specific demo expressed that they found legacy orbit's text readouts are familiar and should be preferred when designing the new GUI (although for example, the vectors display in legacy orbit's sidebar aren't used, instead people just zoom in to see where the habitat is pointing. So not all text fields are mandatory)
[x] A possible solution to an confusingly-rotated viewpoint could be a "revert to default top-down view"
[x] Spacesim members (and also honestly sometimes us) were confused that player input sets the warp to 1x. We should either make it obvious that it does this, or remove this behaviour. I think a feature toggle is too much, we should have it or we should not have it.
[x] The test pilot kept on changing time warp, and requested a keyboard shortcut to change timewarp
[x] specific text fields that were requested were Vcen, Vtan, Apoapsis, and Periapsis
[ ] it was noted that the current landing graphic does not make it obvious that you're moving tangentially to the surface of the earth
[ ] also it's confusing that a landing graphic has the same texture as the planet
[x] orbit projects were requested, but we know this is something we need to do
[x] It was requested that engines be in the range of [-100%, 100%]
[x] it was pointed out that trails are not important
[x] we should check that ref Vo changes with altitude
[x] for AYSE, try to represent the painting in MC, although we should also make it obvious from the top-down view where you can dock with AYSE
[ ] the test pilot pointed out that labels are covered up by planets. We shouldn't put essential information in these labels
First off, the help text was well-appreciated (although the html table of the digits needs to be fixed, otherwise the table 'wobbles' when numbers change a lot)