Landeye's CPU vs. CPU slider set (using editor)

**Landeye** · 11-20-2016, 05:30 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Since I'm bored at work I'll explain what I think these settings do.

(Edit: I'm going to update this post with new findings as I figure stuff out)

GOPT Tab

OACA (50 default) is pass coverage awareness. when it's turned up you will notice players playing zone coverage better. Players will move more in their zone and cover multiple people in the same zone better. For instance a CB will press the WR at the line and move back into his zone and if a receiver runs an out behind them they will back up to better cover both players. When it's turned up too high players will be psychic and cover players behind them without looking (you'll notice it with LB covering the middle mostly) I like 55 I think it makes zone coverage tighter without making defenders too aware.

OARN (50 default) is ball carrier vision. pretty straightforward. I noticed in my old slider set even with it turned up to say 157 you would still see players will low BCV hit the wrong hole and make bad decisions. but overall the vision for all players is better with it higher. Right now 77 seems fine but I'll probably adjust this as needed as I make other changes.

OCVW (0 or 1 default) as far as I can tell this affects WR's catching. This is one I changed from looking at other threads where people had it at 255. What i noticed is that receivers will move towards the ball slightly to make the catch. You'll see it the most on hitch routes when the receiver is waiting for the ball to get to them they will inch towards the ball (more so when the defender is close). They don't take steps but seem to kinda just slide forward barely. but it can make a difference.

UOPT Tab

OAFI/OAFO (defense 80/offense 65)
This is basically a circle or sphere of awareness surrounding the player in which once a player enters this area the other player will know they are there and react to them. However it doesn't seem to matter if they are looking at them or not. it's almost like a psychic field of awareness. Even with these at 1 players won't just run into each other like they're blind it feels like this is separate from players "seeing" the field.

Now I used to crank both of these up to 127 but what I noticed is that while it can make some things look/play better a lot of times it messes the players up more than helps them. The biggest reason I've decided to go to a lower number is for pass/run blocking. So normally when the ball is snapped you will notice the O-line get out of their stance and turn to the person they will block. Sometimes (especially vs. the blitz) you'll notice a lineman not blocking the person in front of them and instead going to block someone else which will cause another lineman to move over to block the original rusher. It always irked me that most of the time if they had just stayed in their original spot the first rusher would be blocked by the closest guy and the other lineman would either block someone near him or move to the middle waiting for someone to get beat. I used to think it was just linemen with low blocking stats "missing" assignments so I would raise the pass blocking slider to help it but it would still happen, but I'm now convinced it's because OAFO set to 65 is actually a little too high and lineman are just too aware of blitzers coming at them from everywhere. With it at a lower number you might notice CB blitzes working a little better since the Tackles won't see them blitzing at first until they get closer but by then they've started blocking someone else. Run blocking will be improved as well where you won't see so much of blockers running past people to block the person behind them.

UINF Tab

PSfi/PSfo (defense 80/ offense 65)
These I'm less sure about but someone else described them as basically making players react to things closer or farther away from them. For example if PSfi is set to a lower number the receiver will react to the long throw from farther away so you may see them abandon the route and stop to catch the underthrown ball rather than keep running downfield. I think it might also affect how quickly defensive linemen realize that the Rb doesn't have the ball on playaction.

One thing i noticed too is that it seems to affect how the QB hands off the ball to the RB. With this at 1 it's a smooth animation but with it at 255 the rb looks like he bumps into the QB and then is handed the ball. I think this is what causes the botched handoffs on some run plays where the QB just stands there afterwords until he gets hit. You'll rarely see it on default but I used to have these both at 255 and I would see that a lot.

(EDIT 11.21.16) Huge finding last night testing! So have you ever wondered why the O-line always gets such a big push at the line of scrimmage even if they're lower rated than the defender across from them? It's because PSfi and PSfo are reaction sliders. I've been testing them but have been setting them both to the same number so I never noticed. I changed PSfo to 63 and PSfi to 66 and I noticed that the D-line was slower to react to the ball being snapped then the offense. On default the PSfi is 15 points higher than PSfo and this is what causes the unnatural o-line push. I figure I'll either set these equal from now on or have PSfo 1 point lower than PSfi since the 0-line would technically know the snap count and have a little natural advantage.

Also I think I might be onto something with making qbs more inaccurate. Right now it's either completion, drop, swatted pass, or interception. Unless you have qb accuracy below 10 you won't really see missed passes (but under 10 the misses you do see are usually 15 yard overthrows or passes that go directly to a defender). I've been messing with CSLV in the GOPT Tab and I'm becoming more and more convinced it affects CPU AI (at least the QB). So I was wondering if I have this set higher and then turn qb accuracy down will the two settings work together to make qbs less accurate but not dumb as they can be with lower QBA. I put CSLV at 25 and then played around with QBA, when I had QBA set to 25 I saw some misses! Out routes being thrown too far and going out of bounds and one time a WR ran a long comeback route to the right sideline and the Qb threw it off target to his left. both QBs had accuracy ratings in the 80s and they were throwing good passes too. I didn't have time to continue messing with this last night but I think this could be huge.

**Landeye** · 11-22-2016, 02:32 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

I would highly recommend anyone using the editor to try turning on CSLV and seeing what you get. It's set to 0 default and can go up to 127. If I had to guess I'd say this adjusts the differences between ratings kind of like threshold does for speed. I felt like at 127 if a defender with say 85 block shedding went up against a lineman with 84 pass blocking he would shed the block as if he was rated 15-20 points higher. Also at 127 It felt like the qbs were throwing with less throw power than normal, almost like it adjusts the scale of ratings so now their 84 throw power rating is less than it was before but the difference between 84 and 86 throw power would be a bigger gap now. It's definitely doing something I just can't put my finger on what exactly.

**return.specialist** · 11-22-2016, 05:56 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

I will flirt adjustments to the CSLV field.

**Landeye** · 11-23-2016, 05:14 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by return.specialist

I will flirt adjustments to the CSLV field.

Thanks for the help! Seeing a good variety of accurate and inaccurate passes with CSLV at 15 and QBA at 45. I've already tried CSLV10/QBA40 but I'd like to keep QBA as close to 50 as possible for all the other effects QBA has besides pure passing. Think I might try CSLV17/QBA47 next. Also I dont know if you're using the other settings too but I changed some things in the first post and updated the second post with some new info.

**return.specialist** · 11-23-2016, 06:24 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Landeye

Thanks for the help! Seeing a good variety of accurate and inaccurate passes with CSLV at 15 and QBA at 45. I've already tried CSLV10/QBA40 but I'd like to keep QBA as close to 50 as possible for all the other effects QBA has besides pure passing. Think I might try CSLV17/QBA47 next. Also I dont know if you're using the other settings too but I changed some things in the first post and updated the second post with some new info.

Unlike other avid users, I am unable to remain focused through an entire game in coach-mode. With that stated, I use a RTG OLB to limit human-decisional influence on situational play calling, offensive audibles, and QB behavior. The RTG is in the third season and was created using unadulterated default roster. All sliders remain at default settings and games are played on the Varsity setting. There is additional info contained within the spoiler that should be noted by the OP but may be of interest to others.

Spoiler

I set CSLV to 127. I definitely noticed greater variability in passing errors. The QBs (Oregon St., FIU) still completed an appropriate number of passes but I noted more short and overthrown incompletions than is typical; fewer inane drops also. The QBs also seemed to make better decisions when making checkdowns.

Although our run defense has been suboptimal this season, I observed the running by opposing RBs and scrambles by opposing QBs to be more deliberate; as if they were running with a purpose or to a destination. I noted this also with WRs and, especially, with TEs on catches underneath zone coverage--as if they would fight through the whistle.

When O-linemen were in the position to make a block, say, in the open field, it appeared they at least would attempt to block instead of running obliviously and precisely linearly toward the endzone. Perhaps there were less suction blocks but I am unsure.

Lastly, I did have 18 and 16 solo tackles in the two games. Before implementing the CSLV adjustments, I was averaging 9-11 with a career-high of 13 earlier in the season. I forced 2 fumbles in one game on big hits (FIU) and had 4 sacks in the other (Oregon St.).

I hope my observations are helpful. I will play more games and provide additional reports.

**skaithius10** · 11-24-2016, 10:16 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

i am trying these out tonight

**Landeye** · 11-24-2016, 11:48 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by skaithius10

i am trying these out tonight

I'm thinking having PSfi and PSfo so close together is making the pass rushing and run defense a little overwhelming. I've been testing PSfi at 69 and PSfo at 64 and OAFI at 68 with OAFO at 63. This way the defense has a little bigger awareness circle but reacts slower than the offense. I can see now why they had PSfi and OAFI set higher than the offensive counterparts but 15 points higher is too much.

**Brock** · 12-01-2016, 05:10 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Where are you at now with these sliders? Are they complete or are you still testing? Also would these work better in dynasty than play now?

I simulated VTech vs Clemson in play now and it played pretty good (albeit I rarely play '14 so I couldnt really say his much better it played versus the other sliders I used) I did notice the defense seemed almost nonexistent.

**Landeye** · 12-01-2016, 07:11 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Brock

Where are you at now with these sliders? Are they complete or are you still testing? Also would these work better in dynasty than play now?

I simulated VTech vs Clemson in play now and it played pretty good (albeit I rarely play '14 so I couldnt really say his much better it played versus the other sliders I used) I did notice the defense seemed almost nonexistent.

Im definitely still testing. When I figured out what OAFO/FI and PSfo/fi did I guess I thought figuring some of the other hidden fields (CSLV,etc.) wouldn't be so difficult. But after messing with that I still dont have a definite idea of what its doing. Im reluctant to use things when I dont know what they do exactly, since it could affect other sliders without me realizing it. This is what made me want to start over in the first place.

I used to have PSfi/fo at 255 which made the reaction time equal for both sides of the ball but with it being so high toss plays are pretty much always huge gains since the linebackers react so slow. to counter this i had run defense up to about 57 to boost reaction time but then that caused more issues in other aspects of the game. Had I known what PSfi/fo were doing from the beginning I never would have had them set that high.

Basically my game plan is to get all the settings in the profile save done first and then move on to penalty sliders and gameplay sliders (if need be) since I can mess with them in-game.

But yeah I kinda took a little break after doing a LOT of testing the past couple weeks but this game always manages to suck me back in I don't think I've not played it for longer than 3 weeks since it came out. As far as play now vs. dynasty I don't really know I always play in dynasty.

EDIT: Oh and what exactly made the defense so bad? reaction time? playcalling? Tackling? Curious of what you're seeing.

**Brock** · 12-01-2016, 09:31 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Landeye

Im definitely still testing. When I figured out what OAFO/FI and PSfo/fi did I guess I thought figuring some of the other hidden fields (CSLV,etc.) wouldn't be so difficult. But after messing with that I still dont have a definite idea of what its doing. Im reluctant to use things when I dont know what they do exactly, since it could affect other sliders without me realizing it. This is what made me want to start over in the first place.

I used to have PSfi/fo at 255 which made the reaction time equal for both sides of the ball but with it being so high toss plays are pretty much always huge gains since the linebackers react so slow. to counter this i had run defense up to about 57 to boost reaction time but then that caused more issues in other aspects of the game. Had I known what PSfi/fo were doing from the beginning I never would have had them set that high.

Basically my game plan is to get all the settings in the profile save done first and then move on to penalty sliders and gameplay sliders (if need be) since I can mess with them in-game.

But yeah I kinda took a little break after doing a LOT of testing the past couple weeks but this game always manages to suck me back in I don't think I've not played it for longer than 3 weeks since it came out. As far as play now vs. dynasty I don't really know I always play in dynasty.

EDIT: Oh and what exactly made the defense so bad? reaction time? playcalling? Tackling? Curious of what you're seeing.

I just got my elgato today and decided to test out both that and your sliders, if you want can link you to the video. But my suggestion would probably be to drop qba, rba, and maybe wr catching to 45.

I saw a ton if broken tackles from both Gallman and vtechs rb and even qb. Tons of big plays with the passing. And not a single sack, which is weird for the Clemson defense. Mind you, I've only played one game (probably should have played more before I posted) and I didn't play in dynasty mode (not sure if there's a gameplay difference).

I also played with fatigue off, should it be on? I wasn't sure what "mm" meant. But the sliders seem to have potential.I really liked how the running looked. I'll test out Alabama/Florida tomorrow.

**Landeye** · 12-02-2016, 09:27 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Brock

I just got my elgato today and decided to test out both that and your sliders, if you want can link you to the video. But my suggestion would probably be to drop qba, rba, and maybe wr catching to 45.

I saw a ton if broken tackles from both Gallman and vtechs rb and even qb. Tons of big plays with the passing. And not a single sack, which is weird for the Clemson defense. Mind you, I've only played one game (probably should have played more before I posted) and I didn't play in dynasty mode (not sure if there's a gameplay difference).

I also played with fatigue off, should it be on? I wasn't sure what "mm" meant. But the sliders seem to have potential.I really liked how the running looked. I'll test out Alabama/Florida tomorrow.

Yeah dude I would love to see the video and thanks for trying these out. Definitely will probably lower QBA and maybe WRC and RBA depending on other things. I would go ahead and raise Holding to around 85, that is probably what it will end up around and it should help with the sacks. The "mm" meant main menu. In the community sliders thread it was discovered that profile sliders and dynasty sliders can impact each other so having it off in the profile and on in the dynasty was a way of getting the benefits of both. I'm wondering though if we could keep it on and maybe mess with OAFT as well.

**Landeye** · 12-02-2016, 09:35 PM

Re: Landeye's CPU vs. CPU slider set (using editor)

Updated OP

**Brock** · 12-03-2016, 12:38 AM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Landeye

Yeah dude I would love to see the video and thanks for trying these out. Definitely will probably lower QBA and maybe WRC and RBA depending on other things. I would go ahead and raise Holding to around 85, that is probably what it will end up around and it should help with the sacks. The "mm" meant main menu. In the community sliders thread it was discovered that profile sliders and dynasty sliders can impact each other so having it off in the profile and on in the dynasty was a way of getting the benefits of both. I'm wondering though if we could keep it on and maybe mess with OAFT as well.

https://www.youtube.com/watch?v=QcTXL5_weTo

I did the alabama/florida game, and it was really good. Florida was dominating a bit earlier on, but Alabama came out with the win in double overtime. I'm currently processing that video. But it seemed pretty accurate for the most part, both qb's struggled and it was a defensive game for the most part until the end it got a bit more offensive.

One thing I noticed the second time around and really liked, was when you said the receivers would stop their routes and come back to the ball to make a catch. I saw that a couple of times and thought it was really cool.

Also, I had fatigue on in the exhibition play. Don't really play '14 at all, so not sure what effects having them on or off really are.

**Landeye** · 12-03-2016, 02:27 AM

Re: Landeye's CPU vs. CPU slider set (using editor)

Originally posted by Brock

https://www.youtube.com/watch?v=QcTXL5_weTo

I did the alabama/florida game, and it was really good. Florida was dominating a bit earlier on, but Alabama came out with the win in double overtime. I'm currently processing that video. But it seemed pretty accurate for the most part, both qb's struggled and it was a defensive game for the most part until the end it got a bit more offensive.

One thing I noticed the second time around and really liked, was when you said the receivers would stop their routes and come back to the ball to make a catch. I saw that a couple of times and thought it was really cool.

Also, I had fatigue on in the exhibition play. Don't really play '14 at all, so not sure what effects having them on or off really are.

I'm at halftime on the video and it looks pretty awesome. I noticed you have edited rosters which reminded me that most of the time custom rosters can have ratings very different from what cpu generated players will have (usually slightly higher than normal and certain ratings much higher like WRs run blocking ratings). Since I plan on using these for 20+ year dynasties I try to set the sliders to work well for these cpu generated players. Not a big deal or anything but just something to keep in mind.
I think holding up higher will make a big difference in what you're seeing and I definitely see what you mean about Qba wrc. I've been testing with lower rates players so it hadn't been an issue yet. For the Alabama/Florida game did you use the same settings for the Clemson/VT game? The updated settings in the OP should help get the WRs to make more contested catches as well, and I would go ahead and set DPI to 51 with OPI at 84. Also set KRI and facemask to 49. On WR screens vs press the dbs will almost always intercept the ball if there's no one assigned to block them. With KRI at 49 they will hesitate just enough that the WR has a chance. With facemask lower you see more wrapping up and less shoulder tackles. I think it makes break tackle animations play out faster as well. Oh and what did you have CSLV set to for the VT game?

Landeye's CPU vs. CPU slider set (using editor)

Recommended Videos

Landeye's CPU vs. CPU slider set (using editor)

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment