Author Topic: squad ops.. (Read 2283 times)

Chanter · « **Reply #1 on:** October 19, 2003, 07:13:48 PM »

agreed.

ramzey · « **Reply #2 on:** October 19, 2003, 09:31:53 PM »

Flossy · « **Reply #3 on:** October 20, 2003, 01:39:55 AM »

Just what I like to see - constructive feedback!

Anyone care to explain this thread?

SELECTOR · « **Reply #4 on:** October 20, 2003, 02:47:02 AM »

cc flossy i will give you a brief summery as i see it..

first off there has been a few problems with the SEA last week or so (as i see it from a player..discos no vox and stuff like that)
so the scenario was delayed by 25 mins .. we were told to exit the arena while it was re set..(ok no problem so far)..a lot of people including our squad went to ma for a while. once back into SEA we found the event already started (4 mins i belive) now being late is our fault i understand , but we was vulched on the runway by 262s 4 min after the start of the frame. so HMMM is all i could say.

oh by the way , we did get back within the original 25 min.

lucull · « **Reply #5 on:** October 20, 2003, 07:48:25 AM »

- 11 Tempests and 9 Spit14.
- Enemy contact after 5min.
- CiC job assigned to a squad that didn't participate
- 10k alt restriction
- no email contacts in orders for the CiC
- no numbers in the orders
- no front line in orders (that I got for frame 2)
- again MAG33 switched for balancing

The list would be longer, if I wouldn't calmed down over night.

After 20min of event time, many people were flying in the MA and discussing how much they "enjoyed" this event. Lucky for the JBs that they didn't participate!

And I tried to get a new squadron into SSO.

And Viff, IMO it stinks, when the CiC assignes his own squadron all restricted planes, which includes mixing plane types and in the end using more than allowed by orders.

And no, I don't complain about flying 190A5 or wanted to fly a restricted plane. Also, I don't say, you broke any rule.

This scenario was a huge step backward and got SSO again closer to death.

[sarcasm=on]
Well done!
[sarcasm=off]

Dear CM team,

please, you said you want to take care about SSO and bring it back to old strenght and player numbers, so that we all could have more fun (again). You didn't show that in the last series, but I hope you'll do in the next.

Regards

Grayarea · « **Reply #6 on:** October 20, 2003, 09:24:04 AM »

Quote

Originally posted by lucull
- 11 Tempests and 9 Spit14.
- Enemy contact after 5min.
- CiC job assigned to a squad that didn't participate
- 10k alt restriction
- no email contacts in orders for the CiC
- no numbers in the orders
- no front line in orders (that I got for frame 2)
- again MAG33 switched for balancing

The list would be longer, if I wouldn't calmed down over night.

After 20min of event time, many people were flying in the MA and discussing how much they "enjoyed" this event. Lucky for the JBs that they didn't participate!

And I tried to get a new squadron into SSO.

And Viff, IMO it stinks, when the CiC assignes his own squadron all restricted planes, which includes mixing plane types and in the end using more than allowed by orders.
And no, I don't complain about flying 190A5 or wanted to fly a restricted plane. Also, I don't say, you broke any rule.

This scenario was a huge step backward and got SSO again closer to death.

[sarcasm=on]
Well done!
[sarcasm=off]

Dear CM team,

please, you said you want to take care about SSO and bring it back to old strenght and player numbers, so that we all could have more fun (again). You didn't show that in the last series, but I hope you'll do in the next.

Regards

1. There were 6 tempests and 6 Spit 14s. Your numbers are incorrect
2. I cannot control this.
3. 50/50 like hate, what can I do?
4. I cannot control this.
5. I cannot control this.
6. I cannot control this.
7. This is only reasonable.

If squads cannot get on and talk to each other reasonably, this is going to kill the event.

Of all the point you made, the vast majority of the actions are with the players. It is up to you all to make this work.

I really don't understand peoples attitude here, this event will not work unless everyone pulls together. That means flying something you don't like now and then and getting bounced and putting it off to a bad day.

If you cannot accept this then it will not work.

lucull · « **Reply #7 on:** October 20, 2003, 09:31:47 AM »

As I didn't number my points, could you please assign your answers, so we don't talk at cross-purposes. TY

lucull · « **Reply #8 on:** October 20, 2003, 09:34:51 AM »

I took the numbers of Tempests and Spit14 from the logs which are provided by innomi8 after someone told me in the MA, that he saw about 11 Tempests.

Puudeli · « **Reply #9 on:** October 20, 2003, 09:38:42 AM »

There definitely was more tempests than those 4 allowed...

ViFF · « **Reply #10 on:** October 20, 2003, 09:54:17 AM »

Quote

Viff, IMO it stinks, when the CiC assignes his own squadron all restricted planes, which includes mixing plane types and in the end using more than allowed by orders.

Sorry, CiC privledges

When you CiC next time you can assign your squadron the best planes, and give 101 Sqn the worst planes.

We went over our restriction by 1x 262, which was a mistake on my part. Instead of having 4x 262 we had 5, thats all.

I did not recieve any info on how many tempests the allies would be able to field, so I can't comment if they went over their allotment or not.

Anybody know if they did ?

Grayarea · « **Reply #11 on:** October 20, 2003, 10:08:08 AM »

Quote

Originally posted by Puudeli
There definitely was more tempests than those 4 allowed...

There were six allowed and used. I don't know how you could know how many were allowed?

lucull · « **Reply #12 on:** October 20, 2003, 10:11:42 AM »

It's the CiC's duty to assign planes, not the privelege.

And I talk about 5x262s AND 4x190D9 you assigned your squad. Of course with "it stinks", I don't mean using 5 262s.

Quote

When you CiC next time you can assign your squadron the best planes, and give 101 Sqn the worst planes.

It's not my style to abuse the CiC's duty.

lucull · « **Reply #13 on:** October 20, 2003, 10:21:42 AM »

Innomi8's logs show more Tempests because he counts every spawned plane, but if someone, like it happenend yesterday, spawns, goes back to tower and spawns again, it is counted as 2 Tempests instead of one, which would be correct.

Quote

Originally written by Grayarea
Given the way this frame went I am feeling likely to increase the number of restricted planes for the Allies while leaving the Axis numbers alone. What are peoples views on the following for the next frame.

Spit XiV 6 (was 4)
Tempest 6 (was 4)

190D9 4
262 4

Gremlin · « **Reply #14 on:** October 20, 2003, 10:54:26 AM »

IMHO this was one of the best SSOs in a long time. Here are my reasons for saying that.

1. Great plane match up with numbers of unbalancing planes kept to just the right level.

2. 12k Alt limit worked well, meant the perk planes had to work hard and stay sharp. As this was a jabo scenario there would have been nothing served by having 35k tempests and 262s whizzing around doing SFA.

3. Targets for each side where acheivable with a moderate amount of good planning.

I really enjoyed this one. It seems to me those who didnt are in the minority.

Quote

Originally Posted By Lucull
I took the numbers of Tempests and Spit14 from the logs which are provided by innomi8 after someone told me in the MA, that he saw about 11 Tempests.

You must be kidding,somone in the MA told you, and on the basis of that you then come to this and some other pretty unsubstantive opinions you come to this board and slam the whole SSO??

There were 6 tempests allowed and there were 6 tempests flown. They were all assigned to No56 Firebirds and I led them into battle.

As far as I see it its the CiCs sole discretion as to how he assigns the available planes, there is nothing the SO CMs can do about that.

As far as orders were concerned you were given your assignment in good time. WHy does CiC's contact details (or lack thereof) make for a bad SSO? ALl your other issues are just issues with the CO. There is not one single issue that you lay out and substantiate that the SSO CM team could do anything about.

Isnt it true that what this really boils down to is that when some people dont perform to their undoubted potential then they blame the event??