Marcus, two things I want to point out here:Marcus Arilia wrote:By the very nature of large fleet fights there’s commonly an information overload for the FC. They cannot possibly remember everything, and other experiences FCs or fleet members may remember things you’ve forgotten. With more advanced players the best thing for the FC to hear is “already done” when asking for something, because a competent pilot anticipated the FCs/fleet’s need (i.e. bubbles, boosts, mobile cyno inhibs, tackling things, etc). It severely reduces the gap of the FC not remembering as quickly or being able to say it fast enough. It speeds up the action and makes the fleet more efficient. It’s also extremely common in more advanced fights. Yeah you’ve got an FC, but an experienced pilot knows how to act semi-independently at the same time.Please, do not make decisions on behalf of the FC.
Legit concern, but the fastest way to solve is to grab an empty squad and set up shop there.Cause it is not possible to understand how many pilots you have with you by checking the number of pilots in the fleet
First, I think you misunderstand the complaint. It's not about ppl anticipating the FC's needs, it's about ppl other than the FC or other designated ppl in the chain of command giving orders. That is confusing as hell and may run counter to the FCs orders or complicate them. Especially in newbro heavy fleets that might struggle to get the basics right instead of being concerned with efficiency.
Second, I think Ares explained this point already, if you have a disciplined fleet this is a good option, but if you don't and you can't trust ppl to get themselves sorted properly, then you might as well not do it. In general I think you two just have two different approaches to FCing and are probably used to a different kind of fleet member.
Asuka, since both of those issues are aimed in my direction, I'd like to respond.Asuka Rossi wrote:I must say, this was a massacre.
The keres loss could be avoided too, the use of damps for approaching was a good idea but approaching straight is not....u dont know how many sensor booster he have fitted, and was at range too. so as he locked you....poof. The MWD excuse dont apply if u burn in a straight line, its a turret ship. Transversal is what counts. the MWD bloom your sig, that is true, but arty tracking is not that good....some transversal would've helped. A little class on spiraling and tackling should help for that.
[...]
For movement tho was not that great. In the 1st part as (silent) LC i tried to get the logi anchored on me, then i tried to anchor on the FC to micromanage more the reps. But DPS was too close to the targets and i lacked to give prop commands, one logi got caught and we lost another. After Logi commander changed and the 2nd engagement started i got recalled because was moving out of logi range. was not my fault guys, u were SITTING STILL. when i got recalled the 2nd time tho i approached my friends and died because the Nightmare was in scram range of the Logi. The armageddons were there too. Logi should play more safe and STAY AWAY FROM DANGER. More spatial awarness is the key to play safe, armageddons have long range neuts yes, but getting scrammed and webbed is a thing that should not happen for a logi wing.
For the first issue I am not sure what you were seeing, but I was actually spiraling in on the Machariel, instead of burning in a straight line, like you say. Your advice is generally very good, but it was also already applied. In this case the Mach repositioned via MJD directly in front off my current direction without loosing target lock and because of my running MWD my turn radius was too wide to adjust my trajectory in time, which resulted in a glancing blow that was enough to kill the Keres' paper tank. Sometimes you just get unlucky. If there was a mistake here, it was that I didn't realize the direction and range of his MJD spoolup would place him directly in front of me. It was very well done by the Mach.
For the second issue, you are absolutely correct, I totally botched the movement part on being LC. Instead of moving us around to keep us safe from the enemy ships and tackle while still staying in rep range, I closed the range to our DD too much. I attributed an insanely fast failing tank to us being too far into falloff, which we weren't but what might have been a missing hardener instead, and anchored us on the FC. I then promptly forgot about it in the confusion. My priorities were off, range control should have been at the top, while in the moment it was an afterthought for me. I was more concerned about the logi being too spread out, which is also an issue, but wasn't the mein issue here.
Lessons learned: Keep moving when anchoring logi. I will also keep in mind that as the FC has a 2IC, a logi squad should have a designated 2IC. When the role was thrust upon me when our LC died, I was not prepared and to be honest was scrambling.