Test Dynasty

Wassup fellas.  While we wait for the named roster set, a potential first patch and just get adjusted to the game in general I have created a test dynasty to allow us to work on a slider set as well as get used to the new dynasty features (coaching tree, new recruiting, etc).

I have sent an invite to everyone that has confirmed they are playing as well as the 3 people on the waiting list.  The league name is AALoATest and there is no password. 

You can choose any team since this is just a test (I chose UConn).  I am currently in the pre-season phase but will advance to the regular season at some point tomorrow morning / early afternoon. 

The advances will be pretty frequent as its not important that everyone gets their games in as this doesn't count for anything.

I have set up the Dynasty with the following slider set:

Offensive Skill	Heisman
Defensive Skill	Heisman
User vs User Skill	Heisman
Speed	Normal
Spd Threshold	40
Penalties
Offsides	50
False Start	50
Facemask	50
Off Pass Interference	50
Def Pass Interference	50
KR/PR Interference	50
Clipping	50
Intentional Grounding	50
Roughing the Passer	50
Roughing the Kicker	50
Sliders
	USER	CPU
QB ACC	10	10
Pass Block	30	40
WR Catch	20	30
RB Ability	40	55
Run Blocking	50	65
Pass Coverage	60	70
Int	30	40
Rush Def	40	50
Tackling	40	50
FG Power	30	30
FG Acc	40	40
Punt Power	30	30
Punt Acc	40	40
KO Power	50	50

 
Getting a feel for Dynasty mode and coming to an agreement on the sliders is the main objective so please feel free to give insights on the sliders after playing your games.  I just threw something together to get us started after messing around with them today.  Let the group know what felt good, what felt cheap, what needs improvement, etc.

Also, if you join before I advance to the regular season I can change your potential early season games vs FCS teams.

If any of you want to play each other, let me know but I was just looking to focus on the User vs CPU games and how they are effected by the sliders.

I will join at some point today.

I have advanced to Week 1.  Also, I altered everyone's schedule to try and get a feel for the sliders.  The first 5 weeks of the season should include for everyone:

2 Games vs teams of similar ratings so it should be a competitive even game.
1 Game vs a team rated higher than yours so it should be a real challenge.
1 Game vs a team rated lower than yours so you should have an easier time with them
1 Bye (I tried to give everyone a bye in Week 4)

Again, as you play your games, feel free to chime in on how the sliders feel, what needs to be adjusted, etc.

Week 1
UConn 27 - BYU 14

This was a pretty good game, or at least it felt good.  Both teams moved the ball well in the first half but ultimately 3 first half fumbles by the BYU QB put them in a big hole.  I recovered the first two fumbles and the third fumble they recovered but it forced them into a 3rd and long.  I turned those 3 fumbles into an early 17-0 lead and 24-7 at halftime.  They would cut the leas to 27-14 but couldn't get any closer.

Stats

UConn (me)
31 rushes for 143 Yards and 3TD
16/20 for 192 yards passing (0INT)

BYU
20 rushes for 122 Yards and 1TD
18/28 for 204 Yards and 1TD/0INT (3 QB fumbles - 2 lost)

Worth Noting

With QB ACC at 10 and WR Catch at 30 for the CPU I saw a couple of dropped passes but not too many inaccurate passes.  With QB ACC at 10 and WR Catch at 20 for User I only dropped 1 pass and completed 80% of my passes.

The CPU QB trucked my DE and/or LB at least 3 times leading to big gains on the ground.

I'll get a game in today. I was in practice mode last night and it was pretty challenging. I doubt this is a fair reflection of the in-game play.  

The pocket collapsed pretty quick on passes forcing you to make quick reads, and I really liked that since it helped mask the broken coverage.  Defensive interceoptions felt pretty high though.  But the running game felt balanced and was yielding runs for losses, short 2-3-4 yard gains and big 10-20 yard gains with only a few big TDs.  Player speed is still off though. Fat DTs were sprinting to catch my fastest offensive players from behind. Not sure if speed threshold will help with that or if it's just part of the difficulty level.

the_EDJ wrote:I'll get a game in today. I was in practice mode last night and it was pretty challenging. I doubt this is a fair reflection of the in-game play.  

The pocket collapsed pretty quick on passes forcing you to make quick reads, and I really liked that since it helped mask the broken coverage.  Defensive interceoptions felt pretty high though.  But the running game felt balanced and was yielding runs for losses, short 2-3-4 yard gains and big 10-20 yard gains with only a few big TDs.  Player speed is still off though. Fat DTs were sprinting to catch my fastest offensive players from behind. Not sure if speed threshold will help with that or if it's just part of the difficulty level.

Ok, let me know after you play your game.  I remember last year the sliders reacted differently depending on whether you were in practice mode, regular play now or in Dynasty.  I have the speed threshold at 40 currently but if we're not seeing the difference between fast and slow players then I'll lower it.  I was able to get the edge with my UConn RB against BYU and like you said the running was pretty even in terms of 4-5 yard runs, some TFL and a 15-20 yard run thrown in there.

Ummmm I just shut out Texas somehow.

Texas Longhorns at Nebraska Cornhuskers
Jan 1,	1ST	2ND	3RD	4TH	SCORE
#15 Texas Longhorns (0-0)	0	0	0	0	0
#22 Nebraska Cornhuskers (0-0)	0	6	10	7	0

Team Stats Comparison
	TEX	NEB
Total Offense	232	291
Rushing Yards	119	147
Passing Yards	113	144
First Downs	9	14
Punt Return Yards	0	35
Kick Return Yards	42	23
Total Yards	274	349
Turnovers	1	3
3rd Down Converstion	2/11	2/10
4th Down Conversion	0/3	0/0
2-Point Conversion	0/0	0/0
Red Zone Touchdowns/Field Goals	1/0-0	4/1-3
Penalties	1-2	0-0
Posession Time	10:24	17:36

Scoring Summary
SECOND QUARTER SCORING		TEX	NEB
3:40	(NEB) FG NEB: Lindsay, 42 Yd FG	0	3
0:07	(NEB) FG NEB: Lindsay, 27 Yd FG	0	6
THIRD QUARTER SCORING		TEX	NEB
4:45	(NEB) FG NEB: Lindsay, 34 Yd FG	0	9
1:41	(NEB) TD NEB: Bell, 20 Yd Pass from Martinez	0	16
FOURTH QUARTER SCORING		TEX	NEB
4:17	(NEB) TD NEB: Abdullah, 2 Yd Run	0	23

Texas Longhorns PASSING C/A YDS TD INT QB D Ash (72.0 QBR) 8/23 102 0 0 P W Russ (192.4 QBR) 1/1 11 0 0 RUSHING ATT YDS AVG TD RB J Gray 21 133 6.3 0 QB D Ash 6 -14 -2.3 0 RECEIVING REC YDS AVG TD WR C Jones 3 61 20.3 0 RB J Gray 4 23 5.7 0 TE M McFarland 1 18 18.0 0 FS J Turner 1 11 11.0 0 WR K Sanders (3 Drops) 0 0 0.0 0 *WR J Shipley (1 Drop) 0 0 0.0 0 *WR M Davis (3 Drops) 0 0 0.0 0 BLOCKING PANCAKE SACK LT D Hawkins 1 0 C D Espinosa 1 0 RT J Cochran 0 1 RG M Walters 0 1 DEFENSE TACK SACK INT TD SS A Phillips 7 0 0 0 OLB P Jinkens 7 0 0 0 *FS Q Diggs 6 0 1 0 CB L Scott 5 0 0 0 *MLB J Hicks 4 0 0 0 DE J Jeffcoat 4 1 0 0 DE C Reed 4 1 0 0 DT M Brown 2 1 0 0 DT A Dorsey 2 2 0 0 CB D Thomas 1 0 1 0 KICKING FG XP PTS LONG K A Fera 0/2 0/0 0 0 PUNTING NO YDS AVG IN20 P W Russ 4 139 34.7 0 KICK RETURN RET YDS AVG TD RB D Johnson 2 42 21.0 0

Nebraska Cornhuskers PASSING C/A YDS TD INT *QB T Martinez (126.9 QBR) 14/20 144 1 2 RUSHING ATT YDS AVG TD *QB T Martinez 16 80 5.0 0 RB A Abdullah 13 55 4.2 1 RB I Cross 3 5 1.6 0 WR J Turner 1 7 7.0 0 RECEIVING REC YDS AVG TD *WR K Bell 6 49 8.1 1 TE J Long 2 39 19.5 0 WR J Westerkamp 1 20 20.0 0 WR Q Enunwa 1 14 14.0 0 RB A Taylor 1 13 13.0 0 WR J Turner (1 Drop) 1 7 7.0 0 TE D Sutton 1 1 1.0 0 RB A Abdullah 1 1 1.0 0 TE S Cotton (1 Drop) 0 0 0.0 0 BLOCKING PANCAKE SACK LT A Rodriguez 0 1 LG J Cotton 0 2 RT J Sirles 0 1 RT Z Sterup 0 1 DEFENSE TACK SACK INT TD MLB M Rose 7 0 0 0 OLB Z Anderson 5 0 0 0 FS C Jackson 4 0 0 0 SS H Jackson 3 0 0 0 CB J Rose 3 0 0 0 DT Kevin WIlliams 2 1 0 0 DE J Ankrah 2 2 0 0 KICKING FG XP PTS LONG K S Lindsay 3/3 2/2 11 43 PUNTING NO YDS AVG IN20 P M Bondi 1 44 44 1 KICK RETURN RET YDS AVG TD WR J Turner 1 23 23.0 0 PUNT RETURN RET YDS AVG TD WR J Turner 4 35 8.7 0

>>DROPS: Texas 9 drops (all but 2 of them were bad drops, untouched by defenders)
>>DROPS: Nebraska 2 drops (I felt they were legit drops)

>>I threw at least 5 bad passes with Martinez. Four of them were intercepted, but on two of them, the defender landed out of bounds so they were just incomplete. I think the D's hands are too sticky.

>>Texas had an unstoppable pass rush without even blitzing. I had less than 2 seconds to throw it seemed. I only completed one pass attempt where the receiver was beyond 10 yards before catching it.

>>Fatigue wasn't prevalent at all as nobody had to sub at all unless it was package specific. I'd say raise that.

>>David Ash is AWFUL for Texas. Which is good. 

Just an FYI, I think you need more than one game to accurately judge a set of sliders.  With that said, I am going to keep the current set through the first 3 weeks of the test dynasty.  Those of us that signed up prior to me advancing to the start of the season should have a game in each of the first 3 weeks:

- 1 game vs a lower rated team
- 1 game vs a higher rated team
- 1 game vs an equally rated team

I tried to also give everyone a bye in week 4 so that will be our break point. 

Be sure to give your suggestions, thoughts an insights on the sliders as to how the games feel, what areas need improving and what feels good.  After week 3 we should have a good sample of games to at least judge and adjust the initial set.

Btw, I am loving the new recruiting set up.  I have no idea how effective I'll be as a recruiter but I am referring strictly to the convenience of the new set up.  While recruiting was more in-depth last year I guess, it is definitely more time friendly this year and more user friendly via the website.

Colorado defeats a St. 24-21.

Pretty evenly matched teams and the game results reflected that. The CPU did have a high number of bad drops but the sliders felt good in this first game.

Looks like all the games have been played.  I see some haven't used their recruiting points for the week.  I will be advancing the week after dinner in the next hour or so, so feel free to allocate your points before then.

Also, I will be making one change to the sliders as it relates to the CPU FG PWR and ACC as the CPU was 0-6 kicking FG in Week 1.  I will leave everything else the same thru the first 3 weeks.

Btw, for those that had the CPU miss FG's in their game was it due to not having a strong enough leg or was the CPU inaccurate with their kicks?

truth_n_babylon wrote:Colorado defeats a St. 24-21.

Pretty evenly matched teams and the game results reflected that. The CPU did have a high number of bad drops but the sliders felt good in this first game.

 Thanks for the feedback.

Week 2 Open

Week 2
Clemson 33 - UConn 17

Stats

UConn
16/29 for 240 Yards passing (1TD / 3INT)
20 Rushes for 73 Yards and a TD

Clemson
19/31 for 236 Yards passing (1TD / 2INT)
37 Rushes for 192 yards and 2TD

Notes

- The CPU had a number of dropped passes, including wide open WR, but once again they still managed to complete over 60% of their passes.

- The Clemson Front 7 ate up my OLine as expected on both run and pass plays.  Most of my rushing yards came on a single 40 yard run.

Overall the game felt good.

Nebraska Cornhuskers at Stanford Cardinal
Jan 1,	1ST	2ND	3RD	4TH	SCORE
#18 Nebraska Cornhuskers (1-0)	3	10	7	3	23
#4 Stanford Cardinal (0-0)	0	10	0	7	17

Team Stats Comparison
	NEB	STAN
Total Offense	420	317
Rushing Yards	148	101
Passing Yards	272	216
First Downs	21	9
Punt Return Yards	3	13
Kick Return Yards	94	22
Total Yards	517	352
Turnovers	3	2
3rd Down Converstion	6-11	5-12
4th Down Conversion	0-0	1-2
2-Point Conversion	0-0	0-0
Red Zone Touchdowns/Field Goals	7/2-3	2/1-1
Penalties	0-0	0-0
Posession Time	17:25	10:35

Scoring Summary
FIRST QUARTER SCORING		NEB	STAN
2:21	(NEB) FG NEB; Lindsay 19 Yd FG	3	0
SECOND QUARTER SCORING		NEB	STAN
3:34	(NEB) FG NEB; Lindsay 27 Yd FG	6	0
2:59	(STAN) TD STAN: Cajuste 72 Yd Pass from Hogan	6	7
:31	(STAN) FG STAN; Williamson 36 Yd FG	6	10
:06	(NEB) TD NEB; Abdullah 7 Yd Pass from Martinez	13	10
THIRD QUARTER SCORING		NEB	STAN
5:17	(NEB) TD NEB; Martinez 7 Yd Run	20	10
FOURTH QUARTER SCORING		NEB	STAN
6:28	(NEB) FG NEB; Linsday 27 Yd FG	23	10
:53	(STAN) TD STAN; Cajuste 23 Yd Pass from Hogan	23	17

Nebraska Cornhuskers PASSING C/A YDS TD INT *QB T Martinez (118.6 QBR) 19/33 272 1 3 RUSHING ATT YDS AVG TD RB A Abdullah 10 67 6.7 0 *QB T Martinez 20 61 6.1 1 RB I Cross 8 19 2.3 0 WR Q Enunwa 1 6 6.0 0 RB A Taylor 1 -5 -5.0 0 RECEIVING REC YDS AVG TD *WR K Bell 6 101 16.8 0 WR Q Enunwa 5 71 14.2 0 WR J Turner (1 Drop) 3 65 21.6 0 TE S Cotton 2 17 8.5 0 RB A Abdullah (1 Drop) 2 12 6.0 1 WR J Westerkamp 1 6 6.0 0 RB A Taylor (1 Drop) 0 0 0.0 0 TE J Long (1 Drop) 0 0 0.0 0 BLOCKING PANCAKE SACK C C Pensick 0 1 FB A Janovich 0 1 DEFENSE TACK SACK INT TD *CB C Evans 5 0 0 0 MLB M Rose 5 0 0 0 OLB Z Anderson 3 0 0 0 SS H Jackson 3 0 0 0 DE J Ankrah 2 1 0 0 CB A Green 2 0 1 0 KICKING FG XP PTS LONG K S Lindsay 3/3 2/2 11 28 PUNTING NO YDS AVG IN20 P M Bondi 1 44 44.0 0 KICK RETURN RET YDS AVG TD WR J Turner 2 93 46.5 0 TE S Cotton 1 1 1.0 0 PUNT RETURN RET YDS AVG TD WR J Turner 1 3 3.0 0

Stanford Cardinal PASSING C/A YDS TD INT *QB K Hogan 9/23 216 2 1 RUSHING ATT YDS AVG TD *RB A Wilkerson 21 109 5.1 0 *QB K Hogan 1 -8 -8.0 0 RECEIVING REC YDS AVG TD WR D Cajuste (3 Drops) 3 101 33.6 2 TE L Kaumatule (2 Drops) 3 69 23.0 0 WR T Montgomery (1 Drop) 1 24 24.0 0 WR K Young (1 Drop) 1 15 15.0 0 *RB A Wilkerson 1 7 7.0 0 BLOCKING PANCAKE SACK FB L Ward 3 0 FB R Hewitt 1 0 RG K Danser 1 0 RT C Fleming 1 1 DEFENSE TACK SACK INT TD FS E Reynolds 12 0 1 0 *MLB S Skov 6 0 0 0 SS J Richards 6 0 0 0 *MLB A Tarpley 3 0 1 0 DT D Parry 3 1 0 0 OLB J Vaughters 3 1 0 0 CB U Amanam 3 0 0 0 CB A Carter 3 0 0 0 CB W Lyons 3 0 1 0 KICKING FG XP PTS LONG K J Williamson 1/1 2/2 5 37 PUNTING NO YDS AVG IN20 P B Rhyne 4 145 36.2 1 KICK RETURN RET YDS AVG TD WR T Mongomery 1 22 22.0 0 PUNT RETURN RET YDS AVG TD WR K Young 1 13 13.0 0

>>Super Psychic coverage was prevalent in the game. A MLB was 5 yards behind my TE with his back turned to the QB on a short hitch route and warped in for a pick. A CB was sprinting down to the flat to cover my RB or TE shallow, but instantly turned on a dime to cover the post downfield for a pick. (Third pick was all on me  ) Other than stick hands, the coverage was inconsistent. Either in turbo mode chasing everything down or in lala land letting WRs do whatever.

>>Just a funny/weird moment, but in Cover 3 zone in the red zone at the end of the game when Stanford scores during no huddle, my entire defense flanked outwards and up field leaving the middle of the field completely uncovered while my deep safety was just standing all the way back with the goal post ignoring the WR standing right in front of him for the TD.

>>MY RBs feel like they're running in quicksand pretty often. Martinez and my WR take off. But my speedy Abdullah and powerful Cross feel like they're just chugging along a bit. Not sure if it's me or what. 

>>Check the dynasty from your end. My router is dropping connection every 10 minutes or so. BUT, I signed back in before quitting the game and it uploaded the results and highlights after reconnecting. Hope it sticks!

>>Most if not all of the Stanford Drops were bad ones.

>>No subs were used due to fatigue.

I think the sub in/out is controlled by the user.  I tried checking the settings and the only thing the user can adjust is whether Fatigue is on or off, and its on.

I will be advancing tomorrow (Tues) at some point.

So far through the first week and half of games the issues that have come up are:

- CPU WR Drops, perhaps too many.

I will say that there are more drops than usual, however with the exception of EDJ's opponents the CPU still seems to be hitting the 60% completion mark.  One thing to take into consideration is that CPU QB Acc (at 10) is low and the passes are still pin point.  I tried lowering it to 5 and both User and CPU were missing wide open passes at an alarming rate.  So while the CPU drops are high, it is almost like the CPU's way of compensating for the super accurate CPU QB.  If the drops were resulting in CPU QB completing under 50% then I'd be more concerned. 

EDJ - are you adjusting any in particular such as the defensive gameplans?  I noticed that there seem to be more drops and much worse completion % in your games.  It could just be that you're better at defense than we are.

- The CPU kicking was off as no CPU kickers made any week 1 kicks. 

I raised the CPU KPW and KAC and it seems they were able to make kicks in week 2.

- Fatigue was not a factor and subs are not being made by the CPU.

As I stated above I don't think I can change that as the commish (although I will check again next time I go on).  I believe the only adjustment I can make is whether to turn fatigue on or off (and its on).

Make sure to keep the comments/suggestions/feedback coming so we can get to a solid slider set.

FYI, I am going to advance the week around 10:15-10:30PM EST tonight.

I have advanced to Week 3.

I sent invites to Buckeye, Ken, illmatic and Nick for the test dynasty.  The invites for illmatic and Kick got rejected however due to no account (I'm assuming you guys haven't gotten the game yet).

Steel Pitt wrote:- CPU WR Drops, perhaps too many.
EDJ - are you adjusting any in particular such as the defensive gameplans?  I noticed that there seem to be more drops and much worse completion % in your games.  It could just be that you're better at defense than we are. 

I havne't touched game-planning outside of Tempo turning it down to conservative to run out the clock at the end of games.  My play-calls center around Man, Zone, and Blitzes much like any game I play, human or CPU. As I noted the majority of the drops are bad ones, untouched hitch routes and such. If everyone else is getting balance, it could just be the QBs I was facing.

Steel Pitt wrote:- Fatigue was not a factor and subs are not being made by the CPU.
As I stated above I don't think I can change that as the commish (although I will check again next time I go on).  I believe the only adjustment I can make is whether to turn fatigue on or off (and its on).

 I haven't checked myself, I knew in Madden I could alter fatigue, so that's what my comments were based off.  I know I can set my own team's substitution pattern. But it stands out when only the first string is on the field at all times.

I'm going to advance the week to Week4 at some point tomorrow (Friday).  I will also adjust the sliders based on the feedback so if you can play your week 3 game and provide additional feedback that would helpful.

I have advanced the Dynasty to Week 5 (everyone had a bye in Week 4 and OSU played an FCS team).  Based on the feedback thus far the issues I've heard were:

Too Many bad WR Drops.

- I have raised the CPU WR CTH from 30 to 40.

CPU Kickers not making any kicks.

- I have raised the CPU FG Power from 30 to 40 and the FG Accuracy from 40 to 50.

Fatigue not a factor.

_ I checked again and there is no way to adjust this from my perspective as the only Commissioner Options are to turn Fatigue on or off.  You can, however, adjust the Offensive and Defensive substitutions in the Coach Philosophy section.  I believe the default is Offensive (65) and Defensive (45).  We could have everyone adjust there's to a lower level to ensure that we see some substitutions, although there is no way to check and confirm that everyone is abiding by that.

If you have the time, please try and play a game or two under the new sliders and see what the results are and how the game feels.  Please provide feedback so that we can agree on a slider set that will make the game challenging and fun for everyone.

I played two halves vs Tenn and had to stop at halftime each time.  Both games played well but it was only a half of football.  I will say it is going to be very annoying this year playing CPU controlled teams that run no huddle as the CPU doesn't even allow you to pick a play at times and barely enough time to pick when the play call screen does pop up.

Yeah hurry up is very difficult to stop the only way I stopped it when I was bama vs Oregon was when the WR would drop the ball.

Steel Pitt wrote:I have advanced the Dynasty to Week 5 (everyone had a bye in Week 4 and OSU played an FCS team).  Based on the feedback thus far the issues I've heard were:

Too Many bad WR Drops.

- I have raised the CPU WR CTH from 30 to 40.

CPU Kickers not making any kicks.

- I have raised the CPU FG Power from 30 to 40 and the FG Accuracy from 40 to 50.

Fatigue not a factor.

_ I checked again and there is no way to adjust this from my perspective as the only Commissioner Options are to turn Fatigue on or off.  You can, however, adjust the Offensive and Defensive substitutions in the Coach Philosophy section.  I believe the default is Offensive (65) and Defensive (45).  We could have everyone adjust there's to a lower level to ensure that we see some substitutions, although there is no way to check and confirm that everyone is abiding by that.

If you have the time, please try and play a game or two under the new sliders and see what the results are and how the game feels.  Please provide feedback so that we can agree on a slider set that will make the game challenging and fun for everyone.

 Note I have also decreased the speed threshold from 40 to 30 to see if speed makes a bigger difference and RB spot getting chased down by DL too easily.

Has anyone played against Oregon with these sliders? 

I just lost 49-35 at home to them, some Oregon stats:

351 rushing yards, 5 TDs
Mariota had 183 yds on 15 carries
Thomas had 168 yds on 12 carries
They only threw 5 passes, all completions on slant routes

They basically ran the same read option no huddle play over and over and it was unstoppable, ripping off on average 15 yds per play... Just wanted to see if anyone had played them..

BK_Buckeye wrote:Has anyone played against Oregon with these sliders? 

I just lost 49-35 at home to them, some Oregon stats:

351 rushing yards, 5 TDs
Mariota had 183 yds on 15 carries
Thomas had 168 yds on 12 carries
They only threw 5 passes, all completions on slant routes

They basically ran the same read option no huddle play over and over and it was unstoppable, ripping off on average 15 yds per play... Just wanted to see if anyone had played them..

No, I haven't played Oregon yet, but I have played teams that run hurry up no huddle and that in general can be pain.  The Read Option by the CPU can be tough especially when you don't have enough time to pick the play you actually want.

FYI, the sliders being used right now are:

Speed Threshold: 25

	USER	CPU
QB ACC	10	10
Pass Block	30	40
WR Catch	20	35
RB Ability	40	55
Run Blocking	50	65
Pass Coverage	60	70
Int	30	40
Rush Def	40	50
Tackling	50	50
FG Power	30	30
FG Acc	40	50
Punt Power	30	40
Punt Acc	40	50
KO Power	50	50