As a community we cannot accept the current CPU QB play.

[JayhawkerStL]

Re: As a community we cannot accept the current CPU QB play.

Yet when playing MUT, QB's play WAY smarter on Competition mode then they do in Simulation mode. Huh.

I noticed in one of my MUT Solo challenges that it was actually Sim mode, not Competitive. I have not checked to see if that is common. Playing H2H is definitely Competitive.

[xSABOx]

Re: As a community we cannot accept the current CPU QB play.

Another part of the problem stems from the play calling... I think patching in the ability to assign custom playbooks to CPU would be just as beneficial...

[KingV2k3]

Re: As a community we cannot accept the current CPU QB play.

Just get rid of 4 vert play. It has been a horrible play since ever!


Sent from my iPhone using Tapatalk

This is one of the main reasons I use custom playbooks:

http://forums.operationsports.com/forums/madden-nfl-football/913734-simulation-football-playcalling-18-fixing-cpus-predictable-gameplans.html

[aholbert32]

Re: As a community we cannot accept the current CPU QB play.

Can't use formation subs with custom play books and that why I can't use them for my cfm.


Sent from my iPhone using Tapatalk Pro

[callmetaternuts]

Re: As a community we cannot accept the current CPU QB play.

Can't use formation subs with custom play books and that why I can't use them for my cfm.


Sent from my iPhone using Tapatalk Pro

Let's just stop and think about what we're talking about here in the last 2 posts. We are talking about a BASIC element of SIM football. Players subbing in and out of games due to fatigue/injury, etc. We are also talking about formation subs and packages being used by USER and CPU. Lastly, we are talking about the CPU calling 4 Verts all too often and taking ridiculous sacks.

These are all core elements of SIM football. You know, if its in the game........ We have a sim mode, for a supposedly sim game (or at least a portion of the game is supposed to be sim) and we are talking about ridiculous workarounds or having to sacrifice one element for another. We aren't asking to play basketball, or to have 13 men on the field.

The CPU QB play has been and is terrible. The outcomes if you looked at just a box score over a 6 min quarter game may be acceptable, but the animations and how they happen are not. Then, we haven't even talked about scaling this to longer quarters.

The SIM mode that they touted doesn't have some of the core sim functions. I have no idea honestly if ARCADE and COMP are different, and they may be great, but we are missing some key items here.

Playcalling by CPU, formations and subs, fatigue, and QB logic (both in throwing decisions and in general logic like scrambling). No QB in the NFL rolls to his right all the way to the sideline and throws it to the other sideline. Doesn't happen.

I know they've seen the tweets aboutt QB stuff, mainly from this thread, but it doesn't seem to be gaining traction. Do we have any SIM gamers that are game changers that can champion this? The zone issues were caught because A) everyone saw it (game changer wise) and it impacted all communities (sim, comp etc).

[KingV2k3]

Re: As a community we cannot accept the current CPU QB play.

Can't use formation subs with custom play books and that why I can't use them for my cfm.


Sent from my iPhone using Tapatalk Pro

Actually, you can...

1) Create the opposing HC

2) Set Formation Subs

3) "Retire" HC

4) Create 3rd String QB and implement custom playbook protocol

Formation Subs (as well as scheme changes) stick after "retire"...

If you play a divisional opponent as second time, you don't have to adjust their Formation Subs again, because they're already there...

If you're on PS4, you can keep an eye out for V2 of the roster lined below, which intends to l have fatigue ratings adjusted for player rotation...

HB1 / HB2 as well as DL, etc.

http://forums.operationsports.com/forums/madden-nfl-football-rosters/913634-simulation-football-roster-madden-18-ps4.html

[StefJoeHalt]

Re: As a community we cannot accept the current CPU QB play.

Actually, you can...



1) Create the opposing HC



2) Set Formation Subs



3) "Retire" HC



4) Create 3rd String QB and implement custom playbook protocol



Formation Subs (as well as scheme changes) stick after "retire"...



If you play a divisional opponent as second time, you don't have to adjust their Formation Subs again, because they're already there...



If you're on PS4, you can keep an eye out for V2 of the roster lined below, which intends to l have fatigue ratings adjusted for player rotation...



HB1 / HB2 as well as DL, etc.



http://forums.operationsports.com/fo...en-18-ps4.html

King beat me too it..this works. Plus he explained it better then I would have! Lol


Sent from my iPhone using Operation Sports

[aholbert32]

Re: As a community we cannot accept the current CPU QB play.

Actually, you can...

1) Create the opposing HC

2) Set Formation Subs

3) "Retire" HC

4) Create 3rd String QB and implement custom playbook protocol

Formation Subs (as well as scheme changes) stick after "retire"...

If you play a divisional opponent as second time, you don't have to adjust their Formation Subs again, because they're already there...

If you're on PS4, you can keep an eye out for V2 of the roster lined below, which intends to l have fatigue ratings adjusted for player rotation...

HB1 / HB2 as well as DL, etc.

http://forums.operationsports.com/fo...en-18-ps4.html

My man. I REALLY appreciate this.

[chunt04]

Re: As a community we cannot accept the current CPU QB play.

I mean if he wants a break down:

1. CPU teams calling 4 Verts, PA Verts, or any long PA pass that has a "streaks like route" is usually where the breakdown is.

2. Pocket Passer QB's should throw the ball away if possible. Balanced QB's should behave more like Aaron Rodgers where he throws it away some and runs some. Mobile QB's should be scrambling and making defenses pay for the great coverage downfield.

3. QB's running toward the LOS with daylight in front of them only to pass it back across their body is a serious legacy issue.

4. The QB traits are not working as they should. QB's are more aggressive with the Conservative Force Passes trait than without it. This has been tested thoroughly.


We can start there. If we can get that to Rex somehow. Problem is there's only a limited amount of text you can send in a tweet.

We need to keep things in a tidy list format for the devs to easily scan over (think like a resume for a job application). This list is spot on. This is exactly what is needed until things can be cleaned up in later iterations of the game.

[roadman]

Re: As a community we cannot accept the current CPU QB play.

any news on tuning cpu qb logic and qb traits? Lengthy forum about it on operation sports

Clint: no news. Investigating. We'll keep you posted if something happens.

John White said they will look into it.

[SyncereBlackout]

Re: As a community we cannot accept the current CPU QB play.

any news on tuning cpu qb logic and qb traits? Lengthy forum about it on operation sports



Clint: no news. Investigating. We'll keep you posted if something happens.



John White said they will look into it.

To be honest it's several issues. I'm pretty interested to see how they can fix it. And the domino effect it'll have on something else that currently works perfectly fine.


Sent from my iPhone using Tapatalk

[timhere1970]

Re: As a community we cannot accept the current CPU QB play.

To be honest it's several issues. I'm pretty interested to see how they can fix it. And the domino effect it'll have on something else that currently works perfectly fine.


Sent from my iPhone using Tapatalk

Yeah, I think it will take a lot more than tuning to fix qb ai problems. It may take some a lot of work.

[schnaidt1]

Re: As a community we cannot accept the current CPU QB play.

any news on tuning cpu qb logic and qb traits? Lengthy forum about it on operation sports

Clint: no news. Investigating. We'll keep you posted if something happens.

John White said they will look into it.

we need to spell out for them that its in CFM...its my guess they just fire up play now mode and look and see...

CFM plays completely different and as JoshC found out, the traits dont carry over the same. someone needs to make sure they test this in CFM and not play now...otherwise they will just come and tell us they dont see an issue

[bad_philanthropy]

Re: As a community we cannot accept the current CPU QB play.

we need to spell out for them that its in CFM...its my guess they just fire up play now mode and look and see...

CFM plays completely different and as JoshC found out, the traits dont carry over the same. someone needs to make sure they test this in CFM and not play now...otherwise they will just come and tell us they dont see an issue

It's mot just CFM. The issue with traits may be the case (I don't know myself), but the crappy and weird QB ai is present (possibly different, but still crappy) in both play now and CFM.

[SyncereBlackout]

Re: As a community we cannot accept the current CPU QB play.

we need to spell out for them that its in CFM...its my guess they just fire up play now mode and look and see...



CFM plays completely different and as JoshC found out, the traits dont carry over the same. someone needs to make sure they test this in CFM and not play now...otherwise they will just come and tell us they dont see an issue

This. And although it may seem like one thing I wouldn't bet on it. Following the thread it doesn't seem like everyone opinion is using the same settings to test against 31 qbs. Can't tell who is usering one DL against what OL using what play or # of rushers and what those persons overall is since we have OL boosts now.

Since play calling is based on down and distance I don't know situationally when the sacks are happening.

It's. confusing.


Sent from my iPhone using Tapatalk