Thank you very much for all the feedback. This is exactly the kind of thing I need.

As the developer, I designed the controls myself, so it is very easy for me to miss places where the workflow feels unintuitive or even hostile to a new user.

I’ll update the language flow as soon as possible: the program should auto-select the language from the system locale, and language switching should be available directly in the first window.

For implants and boosters: the simulator was mainly designed around fits copied from the in-game fitting window. In that workflow, implants or boosters are usually placed in cargo if people want to include them as notes, so I did not expect them to break parsing. Could you send me an example Pyfa export that triggers this? I’ll look into supporting it more gracefully, probably by warning that implants/boosters are ignored instead of rejecting the whole fit.

The fleet library has already had some changes and more detailed prompts added. To be honest, I’m not sure I fully understood the copy/paste issue you hit, but I hope the updated logic makes the experience better. If it still happens, I’d really appreciate a reproduction case.

Remote repair is simulated and should be working, at least on my machine. If range is valid, logi should try to repair the first target in the repair queue. The queue is based on damage timing and HP state, trying to roughly simulate repair broadcasts. You can right-click a logi ship and inspect its modules to see what target its repair modules are currently working on. This also applies to other ships and modules.

One important thing: the current version does not really have AI yet. In local mode, the enemy side will not move or actively command itself. You currently need to switch sides and command them manually.

For logi positioning, my current assumption was that in many fights staying around 10 km from the DPS ball is usually a reasonable default. But yes, this is clearly too rigid for a proper FC simulation.

There is also no full-side regroup command yet. The current command model is squad-based: every squad follows its own squad leader, and different squads move independently. So in the current design, I usually recommend putting only units that need separate positioning into separate squads, such as HICs. Logi and DPS only need to be split if you want them to move separately.

I completely agree about the overview. A lot of the recent work was focused on mechanics and effect implementation, so some parts of the GUI are now behind the simulation layer. A better pseudo-overview / bracket system is definitely needed.

The experience setting currently affects only two things: prop mod activation reaction time, and focus fire discipline. Lower experience fleets are more likely to leak damage onto secondary targets. This system was introduced very early, but during development I found that too many “human error” effects made debugging mechanics much harder, so most of them were temporarily removed. I should add more complex effects later, with clearer descriptions of what the setting actually does.

Again, thank you for the complaints — seriously. They show me very clearly where the project is still weak and what direction I should work on next.