I am the advisor for a university sci-fi club, and we ran an EE night at the club meeting a few weeks ago to familiarize folks with it, and then had it available all day in its own room as an activity at our local free sci fi convention. Following are some notes and feedback from the two events; I've got another event coming up soon as well. They are in no particular order.
Version was 2016-09-02, almost entirely Windows. We did have one person who (with some effort) managed to get a working and compatible Linux version, and a semi-successful attempt to get it running on Mac OS X that was aborted due to lack of time.
I want to point out that despite considerable frustration, when things were working people had a lot of fun.
* Instructions for cloning from the repo are out of date; and the one person who managed to get it to compile themselves had some issues. Among other things, it's apparently not immediately obvious how to get a version that properly matches a particular version of the pre-compiled download version. (Also, the error messages for incompatible versions were not as clear and obvious as they could be.)
* Both the server and client seem to demand more system resources than it seems like they ought, and are significantly unstable on weaker systems. Slow is OK, stuttery is even OK, but it shouldn't just lock up or crash on a slower system. We had several laptops that could play perfectly fine for a few minutes with no signs of problems, but would just crash before 15 minutes were out. (Leading to various jokes about officers having apparently been yanked out of a bar when the alert was called, as they would go unresponsive randomly as they kept having to restart the client and get back in.)
* The server, even if running on a decent system, seems to be intolerant of network issues and crashing clients, and locks up. (Unresponsive, only way to get out is to kill it from Task Manager.) I had an arrangement with a small form factor (SFF) desktop as the server & display, a good laptop, and a decent laptop to run clients, all with dedicated NVIDIA graphics and hardwired through an Ethernet switch; this was stable indefinitely (several hours on at least one occasion). However, when we threw a WiFi network or lower-power clients (which would themselves crash every so often) into the mix, the server would just lock up every so often. My best guess is that the error handling / rejection for malformed, bad, or out of sync packets is insufficient (or lacking).
* As far as I could tell, the GM screen can only be brought up on the system that is running the server. I can sort of see why that might be done that way, but it's operationally inconvenient. Consider a separate password for GM functions?
* Middle mouse button functionality on the main screen controls (switch between directional 3D and various radar views) was erratic. In particular, it seemed to mostly be able to switch to the tactical radar, but not to the longer range one.
* A "look in the direction of the targeted ship" mode readily available for the main screen would be very handy.
* The tutorial needs serious help. It's far too slow and tedious. My most significant short-term suggestion is to break it into separate segments based on stations / functionality; so new folks can check out the one for the station they are trying, and so that when the client crashes you don't have to start over from the beginning. We had several people who tried for almost an hour and were never able to get all the way through due to crashing, despite multiple tries.
Secondly, significantly up the power of the beams, or reduce the shields / hull of the target, in the weapons segment. Many people thought it was broken, because nothing seemed to be happening for quite some time, as the feeble beam plinked at the target to no apparent effect; and you don't seem to be able to move on until it's been killed.
* The default ships are hard to use for people who don't know what they are doing. The first session I was the only one with any serious experience with EE; we tried various default things, and it never really jelled. In particular, broadside torps are hard to use for inexperienced helm and weapons, and the limited arcs of fire, weak weapons, and slow turn rate means that the "action" is not very action-filled.
Over the next couple of nights I created a "beginner's cruiser" to use at the bigger con event, and it went over *far* better. Significantly inspired by Classic Trek but with influences from various other genres, it has the following layout:
Spinal Mass Driver: 0 deg, centerline forward (HVLI only; dead ahead, unguided)
Torpedo tubes, multi-purpose: canted 15 deg. port and starboard of centerline forward (Homing, EMP, Nuke; 15 and 345)
Mine dropper: 180 deg, aft (Mine only)
Port + forward medium range (2000) beam, 120 degree arc (270 to 30)
Starboard + forward medium range (2000) beam, 120 degree arc (330 to 90)
Forward long range (3000) beam, 60 degree arc (330 to 30)
Aft short range (1000) beam, 180 degree arc (90 to 270)
This gives at least *some* close in beam fire in all angles, so that fights against fighters aren't quite so annoying; but with plenty of interesting tactical variation; in particular, what players started calling the "cone of death" where (by deliberate intent on my part), the PF, SF, and F beams overlap. There's some vague balance logic, in that the narrower the cone, the longer the range. I considered adjusting beam power as well, but left it at the default, which seemed to work well enough.
* Many people asked about how to shoot down incoming missiles; the tutorial should probably mention that there is no point-defense in the game (yet).
* Major point of frustration: Enemy AI ships get *way* too close to stations, frequently ending up clipping inside them partly or even entirely, which makes it very difficult to hit them as you just end up hitting the station. Is there a setting in the files somewhere that can adjust their stand-off distances in the short term? Player beam weapons should probably not fire when there is a friendly object occluding the locked target; or at least this should be a difficulty option in scenario setup. Eventually, some AI tweaks are needed here.
* The homing process for homing missiles was a bit opaque; folks gradually learned to work around it, but it never felt really solid. I think missiles should perhaps be faster; opponents should be possibly out-maneuvering missiles, but not simply outrunning them. (There is also a psychological presumption of sorts, due to historical performance of real-world missiles and games based on them, that homing missiles should do better if you get on someone's tail; the EE ones seem to do particularly poorly in a stern chase by contrast.)
* The arbitrary limitations on which console combinations can be used together were regularly annoying. We rarely had a full crew, and the fact that some console sets simply don't have certain options is not immediately obvious.
Short term, simply having a tab that has all the possible consoles listed to pick from would be very helpful. For instance, when I was testing solo on my laptop, I would run the server in one window with Solo Pilot; but have to start a second client process and window to be able to pick Weapons, Relay, and Science to test all the functionality.
* IIRC, despite sort of combining Relay and Science, Operations+ doesn't have all the functionality to conduct full drone operations. As it's usually the first stations to be combined if we are short handed, this was irritating.
* In the rare cases when we had extra folks, everyone thought that the stand-alone power management screen was far less useful than the power management screen from the Engineer station.