User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > Team Quits in Second Half (Cruise Control Issue?) - ISSUE RESOLVED
Page:
 
Catch22
offline
Link
 
Hmmm, I'm wondering if for some reason cruise control isn't turning off after the score gets back to within "range" - I've seen a couple other games like that (including this beauty of a test server game I ran today - not sure if you all can see it but basically the CPU Test Team was down 94-35 and outscored the human team 97-0 in the 4th quarter):

http://test.goallineblitz.com/game/game.pl?game_id=2372

Speed Data

POS - Last Score to go up big/Score withing 50/Score now close
DE2 - 28.5/7.5/17.68
DE4 - 32.6/11.18/20.16
LB1 - 34/20/27.04
LB6 - 31.82/10.61/16.01
LB5 - 36.06/13.46/No Data
SS2 - 26.93/18.03/16.77
FS2 - 26.93/19.53/12.75
CB2 - 29.26/20.62/20.16
CB3 - 30.92/21.21/17.68

I'll have Bort take a look at it and see if he can figure out if there is an issue.
 
AirMcMVP
Mod
offline
Link
 
Originally posted by alindyl
Don't worry about arguing with people trolling. Post your data, let the bug mods see what they think. That definitely is an odd game. Those two kickoff plays had nearly identical players and they were definitely behaving much differently. On the kickoff team only one DT was different, on the return team there was a LB/FB switch in one spot. Otherwise the lineup's were the same.

It seems like cruise control kicked in overdrive and never turned off. Interestingly, it appears that the issue even started before that kickoff. Watch the extra point try's in these two plays


This is when you were leading by 57 points
http://www.goallineblitz.com/game/replay.pl?game_id=1281311&pbp_id=2292923 Notice your players holding up at the line fairly well (no revcakes)
Then this XP when you went up by 63 point
http://www.goallineblitz.com/game/replay.pl?game_id=1281311&pbp_id=2293335 Nearly every player on your line was revcaked

Both XP teams were exactly the same players.

The trouble with this bug is going to be replicating it.


Agree. Fortunately three games have been identified, showing its a repeating problem.

EDIT - And one on the test server. Definitely a repeating issue...finding the cause could be the real issue.
Edited by AirMcMVP on Jul 28, 2010 14:15:49
 
We_Rule
offline
Link
 
Ty catch.... to me it seems like there HAS to be some issue here in our game. Our whole team was not even tired after the game except for a couple of select positions, and obviously ours was not the only game showing something goofy in this regard.

Edit: TBH, it still doesn't answer the other question though : why are there even ANY CPU owned teams in USA Pro or any other Pro league? Can other teams not be promoted today if you wanted them to?
Edited by We_Rule on Jul 28, 2010 14:17:19
 
Hcreek27
offline
Link
 
With the new morale system to control death spirals, is there even a need for cruise control anymore?
 
VolBrian
Rocky Top
offline
Link
 
Marking admin response while Catch investigates
 
Bort
Admin
offline
Link
 
It's cruise control reacting with the recent "play at your opponent's level" update for CPU teams. The bug is that a full CPU team will appear to be level 1 when scaling for cruise control, while the team with human players will not.

I've got a fix set up I am about to test.

And yes, we still need cruise control for games where you play a bunch of lowbie human players to keep them from taking 10 hours to finish.
 
Dpride59
offline
Link
 
Originally posted by Bort
It's cruise control reacting with the recent "play at your opponent's level" update for CPU teams. The bug is that a full CPU team will appear to be level 1 when scaling for cruise control, while the team with human players will not.

I've got a fix set up I am about to test.

And yes, we still need cruise control for games where you play a bunch of lowbie human players to keep them from taking 10 hours to finish.


or this
Edited by Dpride59 on Jul 28, 2010 14:30:51
 
Gee Money
offline
Link
 
we were up by 63 and then we could not do anything...someopne pointed out that our FG team was kicking from our 40 every time. funny thing is our FG was set at 47 yds so not sure why this took place.

also we got up by 63 and then we could do nothing

http://goallineblitz.com/game/game.pl?game_id=1290823
 
AirMcMVP
Mod
offline
Link
 
Originally posted by Bort
It's cruise control reacting with the recent "play at your opponent's level" update for CPU teams. The bug is that a full CPU team will appear to be level 1 when scaling for cruise control, while the team with human players will not.

I've got a fix set up I am about to test.

And yes, we still need cruise control for games where you play a bunch of lowbie human players to keep them from taking 10 hours to finish.


Thanks Bort!
 
bobdakota
offline
Link
 
Originally posted by Dpride59
Originally posted by Bort

It's cruise control reacting with the recent "play at your opponent's level" update for CPU teams. The bug is that a full CPU team will appear to be level 1 when scaling for cruise control, while the team with human players will not.

I've got a fix set up I am about to test.

And yes, we still need cruise control for games where you play a bunch of lowbie human players to keep them from taking 10 hours to finish.


or this


Wish I knew what you said before the edit. I will save this one for when Dpride says he was never wrong
Edited by bobdakota on Jul 28, 2010 14:36:15
 
AirMcMVP
Mod
offline
Link
 
Actually, one more question Bort (if you're still around)...

Why wouldn't cruise control turn off? The biggest issues I saw was that even when the score got close (or they took the lead) we never returned to "normal".
 
Bort
Admin
offline
Link
 
Originally posted by AirMcMVP
Actually, one more question Bort (if you're still around)...

Why wouldn't cruise control turn off? The biggest issues I saw was that even when the score got close (or they took the lead) we never returned to "normal".


Just the way that it happened to work with the logic. It caches stats, and the (perceived) level difference caused an issue.

CPUs thought they were level 1, and the other team was higher level, so there's nowhere to scale down from there.
Edited by Bort on Jul 28, 2010 14:48:29
 
Gee Money
offline
Link
 
Originally posted by Bort
Just the way that it happened to work with the logic. It caches stats, and the (perceived) level difference caused an issue.

CPUs thought they were level 1, and the other team was higher level, so there's nowhere to scale down from there.


So from the sounds of it, games against CPU players this season should be closer, but this HUGE swing is now fixed????
 
Bobmachinegun
offline
Link
 
I'm hoping a season delay if this isn't fix by the actual start of it.
 
Gee Money
offline
Link
 
Originally posted by Gee Money
So from the sounds of it, games against CPU players this season should be closer, but this HUGE swing is now fixed????


Bort, Catch22,

Can we get a confirmation on this??
 
Page:
 


You are not logged in. Please log in if you want to post a reply.