Aces High Bulletin Board
Special Events Forums => Friday Squad Operations => Topic started by: FiLtH on July 18, 2009, 10:19:16 PM
-
Im not sure what happened lastnight, whether it was misunderstanding, or people new to the FSO, but when guys are trying to land, and the CV isnt under attack, please dont turn the cv. AFter 3 attempts landing and the cv turning just as I approached, I finally got down and re-armed. We lost a couple guys due to that.
Another thing, make sure everyone knows when killshooter is off, they can kill friendlies. As I was rolling again I saw tracers just off my right wing,a guy was sitting on deck firing his guns, I swerved and almost ended up in the port elevator.
-
I understand your concern and can only say that it's the responsibility of the squad CO or XO to remind/instruct the new guys of the rules and settings of the FSO. And for crying-out-loud...don't let the n00bs take control of a CV!
-
Ordinarily there's one person from one of the defense squadrons assigned by the CiC to drive the boat. I don't know what was happening at C17 where a lot of this occurred, but it sounded like one of the attack squads had a guy take control so they could turn it for their group.
-
Im not sure what happened lastnight, whether it was misunderstanding, or people new to the FSO, but when guys are trying to land, and the CV isnt under attack, please dont turn the cv. AFter 3 attempts landing and the cv turning just as I approached, I finally got down and re-armed. We lost a couple guys due to that.
I saw on Allied country text a certain pilot say "so-an-so's coming in for a landing, quick turn the CV"... I sent an immediate warning to this person that this in an ejectionable offense. I will not tolerate foolish gameplay in my FSO's
Another thing, make sure everyone knows when killshooter is off, they can kill friendlies. As I was rolling again I saw tracers just off my right wing,a guy was sitting on deck firing his guns, I swerved and almost ended up in the port elevator.
Actually, frame 2 killshooter stayed on ( you will kill yourself ) till I got reminded. I just forgot to turn it off after the initial CV launches.
Be carefull!!, you could end someone's night.... and it might be your own.
4XTCH
-
Ordinarily there's one person from one of the defense squadrons assigned by the CiC to drive the boat. I don't know what was happening at C17 where a lot of this occurred, but it sounded like one of the attack squads had a guy take control so they could turn it for their group.
snowball was turning it for the LCA's, there was however probably a dozen or so guys on finals (I had come in with half a dozen other nightmares and was capping while watching this idiocy unfold).
-
snowball was turning it for the LCA's, there was however probably a dozen or so guys on finals (I had come in with half a dozen other nightmares and was capping while watching this idiocy unfold).
Why was snowball driving in the first place? IMO the only people driving the boat should be either the CiC or a representative of the defending squads (which is what USUALLY happens. Actually, in most of the FSO's I've been involved in the CiC had to report who was driving to the CM). That would prevent a LOT of these sorts of problems right away by keeping random people from taking control (which is what DID happen) and moving the CV.
-
I had my squad moving the cvs from time to time. My biggest gripe was with whomever was taking control at any given time, they would not respond to a multitude of players on country or battle channel at all. I had to PM a few guys to finaly get control or get them to turn the ship so it wouldn't leave the combat area out of bounds.
-
should be a rule, if your squad touches the cv without being asked, your out for a month.
-
Why was snowball driving in the first place?
NFI, I was probably the 'so-an-so' 4XTCH was talking about as I had some refined comments on the LCA's landing abilities if they needed someone to line up the CV for them :D
-
May I suggest something that has worked for me as a CIC who has been plagued by this in the distant past?
If a player, other than your nominee, takes control of a cv for any reason, ask him to release it immediately using direct text. If he doesn't respond positively, immediately, ask the CM to eject him. It's effective, simple and definitely to the great benefit of the community.
-
May I suggest something that has worked for me as a CIC who has been plagued by this in the distant past?
If a player, other than your nominee, takes control of a cv for any reason, ask him to release it immediately using direct text. If he doesn't respond positively, immediately, ask the CM to eject him. It's effective, simple and definitely to the great benefit of the community.
Hear hear :rock Kick em out. The CO too for not staying on top of his pilots.
-
If a player, other than your nominee, takes control of a cv for any reason, ask him to release it immediately using direct text. If he doesn't respond positively, immediately, ask the CM to eject him.
It's a little harsh to summarily boot someone who you didn't "nominate" to control a CV. There are plenty of capable people and the CO of a squad knows who can and cannot be trusted with CV duty. There are times when the CO will authorize a squadmate to take control of a CV - squaddie is down and CO is thick in the battle.
You can't assume just because the CO isn't in control of a CV that the CV is in the hands of some total incompetant. Unfortunately, by the time you realize that it is being controled by some banana it's sometimes too late.
-
I was watching my crew of Nightmarez come in for their final and I have never seen a carrier so blatently try to fumble landings and even take offs. The fellow snowball had impeccable timeing to turn the cv the moment a plan places out gear or throttle his engine to take off. I personally watched from the tower's f3 esque veiw as two of my squaddies were forced to ditch or fell of the carrier do to this tom foolery. I only wish I had been filming but I just didnt think to at the time it all was so sudden was to busy trying to communicate danger stranger in carrier.
-
One I would suggest that if you have films of the event to contact the CO of the squad Snowball is in, politely explain what happened, provide him with films, and then let the CO of that squad deal with his pilots behavior.
FSO is a decentralize event to some extent where we all rely on the command staff of a squad to keep their pilots informed of the rules, informed of the objectives, and to make sure their squaddies behave accordingly. I am sure the command staff of Snowball's squad will take such "tom foolery" seriously and explain to their squad that such behavior hurts their team mate and the performance of their side since each plane lost do to such actions is one plane less available for use in on going actions during the event.
You might also wish to CC the admin CM for the event so that he is aware of the particular situation and keep an eye out for it in future frames.
-
It's a little harsh to summarily boot someone who you didn't "nominate" to control a CV. There are plenty of capable people and the CO of a squad knows who can and cannot be trusted with CV duty. There are times when the CO will authorize a squadmate to take control of a CV - squaddie is down and CO is thick in the battle.
You can't assume just because the CO isn't in control of a CV that the CV is in the hands of some total incompetant. Unfortunately, by the time you realize that it is being controled by some banana it's sometimes too late.
But if the banana doesn't respond to your direct PM text he's an idiot and needs to be removed for the sake of the other guys trying to play out the frame. It's not the MA. I know of what Dantoo speaks as I clearly remember the incident he's talking about and it had a serious impact on the outcome of that frame. Had a guy that just wouldn't let the CV go and had one hell of a 'tude about it. I have flashbacks about that every time we have a blue water ops frame since then.
Sometimes ya just gotta do what ya gotta do for everyone else's sake. Harsh--maybe. But as I see it, the banana would be the one making the choice.
Drano
-
I totally agree that a blatent banana should get the boot. I'm just saying, just because someone wasn't the CiC's choice to man the boat, that someone shouldn't automatically get the boot if the CiC sees him in control.
I also agree that the CiC has every right to know who's controlling his forces, and those in charge of a CV who were not the original commander have an obligation to either report in as such, or respond immediately when questioned about it.
-
FSO could use a bit more harshness, imo. :aok
-
FSO could use a bit more harshness, imo. :aok
Amen. When something like this happens it ruins the event for people.People that just might want to sit out the next frame.Or more. I think FSO should have a zero tolerance on these issues and the people or person involved be kicked out. They should also not be able to show up the following week. Or the next ....ect ect ect.
-
The thing is, this is something that should be able to police itself and not even REQUIRE a rule change:
1) CiCs establish at the frame's beginning who is driving the boat. More often then not this will come from the defending squadrons, though I know some CiC's in the past have had a non-flying "command staff" assigned to this. Either way, the commander of the boats should be decided before launch.
2) If the CV commander needs to turn over command to someone else, the CiC and other relevant parties (IE, if more than one defending squadron assigned to the CV, make sure BOTH COs are advised) should be made aware of the change FIRST so he can keep track of who is driving. This IMO is just good etiquette for ANY change in command during the frame. Whenever my squad is assigned by the CiC to command the local defense forces, if I have to log and turn command over to one of my other squad members I make sure to let the CiC and other squad COs in my defense area know. It doesn't take more than just a few keystrokes in the text bar.
-
From this point here is what I would do. As an example, whenever my squad does an internal "squad challenge", we post the rules of the event on our website, and anyone who wants to participate will sign off on it, "I have read the rules and understand". Simple. That said, I would say that before the next event, The CM sends out the rules to all the COs to read again, if they have not already, and sign off on them. Its up to the CO's of each squad to cascade that info to their own squad members. This will show accountability. This should be a pre-requisit for future squads who join. As for CV control, the CiC should determine who controls them. Anyone wishing to take command should PM the CiC directly prior to. I say PM because that stands out a lot better than country or command channels, and the CiC can respond a lot quicker. And in regards to Snowba11, I did get his attention, finaly, and he gave me his reasons for grabbing the CV. At the time he had it heading towards "out of bounds" so I made him turn it to keep it in. He made the set point short which put the CV in a turning motion, and then corrected it. I don't think he was being malicious and I may have made an error there at that particular point. One thing I am not good at is controling the ships, so I will practice this. It's just not something I was really interested in in the MA. But I have squaddies who are proficiant at it. I might suggest that when you are CiC, you designate a squad as owners of the CV and get conformation in the orders sent out. It boils down to communication. If you can clear that hurdle before an event, this should make things run a little smoother during the battle.
My 2 cents. :salute
-
Yeah, what Saxman said!
-
By all means if a players won't relinquish control of a CV when instructed to by his superiors (his squad), another squad command staff, or the CiC and is causing such problems as sited contact the setup CM and he can either remove the player or at the very least remove the player's control of the CV so that somebody else can take control and rectify the situation.