He practically plays the game for the first time, so it is a nice glimpse onto the first impressions and what might be confusing for a new player.
I took some notes:
- The paused state of the game upon loading a save isn't clear. Neither is the fact that pause disables the BBS. Maybe we could flash the pause button to draw attention to it?
- Passing mention about the ugly portraits :P
- He discovered the RMB radial menu Autopilot on the body list quickly, but didn't realize that it works on the target name and on the target itself too.
- The cargo capacity bar on the station screens is confusing (cargo/overall capacity) indeed. Maybe we should show cargo capacity only, and the full capacity on the upgrade screen? Or put an indication on the bar that this is where the cargo room ends?
- The classical/piano music seems feel quite out of place. He mentions that quite a few times. I agree, although I usually play without music anyway. With the new music contributions, maybe remove those?
- The hyperpsace range calculation was a bit confusing (more fuel meant shorter range). But I think he figured it out in the end that it is a "mass thing"
- On that note, the knowledge that a bunch of shorter jumps is faster than a singe jump isn't clear. But I think that's not a problem
- The need to select Star A/B/C seems to be understandable from the UI
- The need to add the destination star onto the route wasn't that clear at first, but he figured it out quickly. (While flying and hitting the ground)
- I don't think he noticed it, but it is bugging me for a while now: The hyperspace route is not saved (or loaded) when you save the game.
- Filters for economy and population would be useful for the sector map.
- The function of the trade computer might not be that clear
- Autopilot once crashed into the destination orbital station. It arrived nicely on the second try.
- I noticed that he sometimes left the thrust lever on full after landing, and then slammed into the ground station upon takeoff. Not sure if that counts as a user error or UX issue though. If we consider it an UX issue, a solution could be to ignore any axis inputs upon takeoff until the axis value changes?