Someone let me know when we're close or ready to advance (we're probably not close), I'll be working in my office most of the weekend.
Upvote
0
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
jwinslow;1508805; said:Someone let me know when we're close or ready to advance (we're probably not close), I'll be working in my office most of the weekend.
jwinslow;1509011; said:That UTEP is one tough cookie to crack, huh? :p
What? Are we allowed to restart games against the CPU if we start off poorly or have an injury? I'm not following here.CentralMOBuck;1509026; said:Hell yes they are. I had to restart the game. Miles got hurt(shocking right?) and Comer had a case of the fumbles early on. Before I knew it I was down by two scores. The second game I got up 21-0 and they stormed back to take a 28-21 lead early in the the third. So I decided to super sim the rest of the game starting in the 4th. Got it tied up on the next time I had the ball and then scored another TD on the next drive. In both of my games my defense was torched in the passing department! Oklahoma is going to steam roll me and I might have to reschedule a ton of recruits visits for that game.
It probably doesn't help that I haven't played a game in a few days.
You might as well just play the PC. I doubt it would even be worth your time playing against me!jwinslow;1509067; said:Yeah, you're not supposed to restart games against the computer... particularly not to undo injuries or losing.
The Shark will exact vengeance upon Boobie next week. He wasn't gone for the year until the later game injury
BrutuStrength;1509059; said:I just survived some of the most unbelievable comeback AI I have ever faced... against Army!
First, there was BS from the beginning. Their QB threw for over 300 yds against me. Army's freakin 79 OVR QB picked me apart!
The worst part about it was how absolutely unbelievably blatant the AI was. One particular 3rd down, when I had him dead to rights for a sack, he spun off of 2 my DL and got past the line of scrimmage. So I'm thinking he'll be tackled well short of the first down marker by one of my LBs or DBs that have him surrounded (at least 4 of them). Nope, he bounced off of them until he got past the marked and then he would let me tackle him.
Another 3rd down play. 3rd and about 18 or so. He completes a pass to the middle of the field, still short of the 1st by 8 yds or so. Then his receiver turns into the super-QB from the aforementioned play (I dunno, maybe their the freakin Wonder Twins or something) and bounces off of my numerous defenders until passing the first down marker, where he was also willing to let me tackle him.
Then, late in the game, after I down a punt inside his 5. I call a zone play with an OLB blitz. I'm controlling the OLB and have him dead to rights for a safety. I dive at the QB, and not only do I not sack him, but he remains unencumbered by my being right in his face and launches a 30 yard completion. Didn't throw a quacker at all. Total BS given the normal occurrence.
Oh, and did I mention the CPU was 2 for 2 on recovering onside kicks, or that after I scored a defensive TD late in the game, it returned the ensuing kickoff for a TD (and then recovered it's 2nd onside kick!)? I won, but it was an ugly mess of AI BS.
The only redeeming aspect (outside of the win) was that I knocked their stud RB out for the next 7 weeks or so.