Game 1 in Wooden, and already the new engine is horrible. my 3rd string, Freshman player, played more minutes than the second stringer who had 81 stamina and no fouls. then I lose at the buzzer after my opponent inbounded with 39 seconds to go. It isn't fun paying to be a beta test site.
6/24/2010 10:33 AM
Why is losing at the buzzer when inbounding with 39 seconds to go a broken result?  Forty seconds isn't enough time to run an offense and get a shot?  Obviously they held for the last shot then shot with less than a second left, and the game doesn't show fractions of a second.


 
6/24/2010 10:49 AM
I musta missed something also A/B.  Don't see what the inbounding thing has to do with anything.
6/24/2010 10:51 AM
Shotclock is only 35 seconds and the clock doesn't start until the ball is inbounded. Jetsons point is the last shot had to be taken with at least 5 seconds left and there is no way a shot takes 5 seconds to go in once shot.
6/24/2010 10:54 AM
Ah.

Still, it seems a bit melodramatic.

Just submit a ticket.  Things like that would sometimes happen in the old engine as well.

6/24/2010 10:56 AM
I am sure you have "When winning and the game is out of reach, give more time to backups" checked.  Your 3rd Stringer (assuming it is Thomas Bear, pg) played a bunch of minutes when you were up by 10ish points at the beginning of the game.

You were ahead by 8 at the half.

In the second half, It seems that Bear and Phelps played together a bunch of times to, with Phelps at SG (and you did have SG and SF foul problems).

You can't really complain that the team followed your Depth Chart, unless you don't have Phelps also listed at SG.

There was 4 seconds difference between the shot clock and the game clock at the end of the game.  I am not sure that the play-by-play tells you every single thing that happens if it is not a turn over ... like PlayerA is called for a kicked ball, the shot clock is reset.

There is nothing beta about the new engine now, at least not IMHO.

6/24/2010 11:10 AM
Also - please remember that the play-by-play is generated after the result/box score.  You had already lost by the time that was created. 
6/24/2010 11:38 AM
not sure why everyone is so quick to dismiss this complaint. i don't think it is proof that the engine is horrible, but the end of game issue is a legitimate gripe.

The "kicked ball" answer above is nothing but an excuse to defend the SIM, as is the timing of PBP generation as opposed to the result. With 39 seconds left, I want an explanation of what happens the rest of the way... no matter when it was created, and if something happened to re-set the shot clock, it should be in the PBP. No excuses. I would certainly send a ticket in about this.

as for the playing time thing, i looked through the box score and tend to agree that it was a depth chart/one-guy-at-multiple-positions issue. an anomaly, hopefully, but i'd play with my depth chart if i were you, jetsons, and get them straightened out either with someone set to GT or a switch for the 2nd-stringer...


6/24/2010 12:04 PM
Jetsons do you have that freshman as 3rd string at 2 positions? I know I did that and the 3rd stringer routinely played more minutes than the backups at either position.
6/24/2010 12:12 PM
Posted by acn24 on 6/24/2010 11:38:00 AM (view original):
Also - please remember that the play-by-play is generated after the result/box score.  You had already lost by the time that was created. 
No offense to you personnally acn, but I hate it when people use that rationale. The only tool we have to see the eb and flow of the game is the play by play and its the only way we can see how a game may have been won or lost. The box score doesn't tell us if we lost on a last second 3 pointer or if we were down by 3 the entire half therefore the box score is of no help to us in deciding our late game settings.  If WIS can't get the play by play to make sense and to match the actually simulation then what good is it?
6/24/2010 12:12 PM
Posted by wronoj on 6/24/2010 12:04:00 PM (view original):
not sure why everyone is so quick to dismiss this complaint. i don't think it is proof that the engine is horrible, but the end of game issue is a legitimate gripe.

The "kicked ball" answer above is nothing but an excuse to defend the SIM, as is the timing of PBP generation as opposed to the result. With 39 seconds left, I want an explanation of what happens the rest of the way... no matter when it was created, and if something happened to re-set the shot clock, it should be in the PBP. No excuses. I would certainly send a ticket in about this.

as for the playing time thing, i looked through the box score and tend to agree that it was a depth chart/one-guy-at-multiple-positions issue. an anomaly, hopefully, but i'd play with my depth chart if i were you, jetsons, and get them straightened out either with someone set to GT or a switch for the 2nd-stringer...


I want a lot of things ... a million dollar a year job and a Victoria Secret model for a girl friend, just to name a few. 

The PBP does not have every single event in it ... it has Scores, Fouls, turnovers, etc.  I wish it was better.  It would be nice to have a more detailed PBP.  I would also like to see SIM generated play-by-plays and more details on each shot (who took it, who was guarding him, when guys don't rotate in the zone, etc.).  All of those wants are not how the engine and pbp generation work right now.  It is also not how they worked before.  So, this has nothing to do with the new engine (at least the best I can tell).  PBP verbosity sucked in the old engine as well.


6/24/2010 12:56 PM
not good enough. As far as I can tell, the PBP contains every event which would cause a whistle/stoppage in play. It contains all turnovers, fouls, shots (made or missed). Why would you assume the ball was kicked and the shot clock reset? What makes that more likely than there being an error in the SIM? And, if you are correct, why are you willing to forgive a missing key element of a play in your PBP? What other missing elements of PBPs actually affect game results in a visible manner? Are you willing to forgive those? 

either:

you are correct and the shot clock was somehow reset, but we just don't see it

or: 

there's an error in the engine which allowed this team 39 seconds to take a shot.

There is no way to tell, so if I lost that game I would surmise that it's an error until a developer tells me otherwise. No reason to just assume that they got it right, but not all the way right...

I have always been willing to overlook the details of whether my PG had a 10-second violation vs a double dribble vs a pass out of bounds-- all turnovers, i don't care how the PBP describes it. But if there's an element that affects timing, I want to see it.
6/24/2010 1:10 PM
I agree that this should be looked into a little bit.  39 seconds to take a shot shouldn't happen.
6/24/2010 1:12 PM
I did not say not to ask the question ... I would ask the question.  I just provided one example of how that can happen.

I could also be a bug in PBP generation where something got left out (a shot and rebound).

So, certainly submit a ticket.
6/24/2010 1:17 PM
Posted by wronoj on 6/24/2010 12:04:00 PM (view original):
not sure why everyone is so quick to dismiss this complaint. i don't think it is proof that the engine is horrible, but the end of game issue is a legitimate gripe.

The "kicked ball" answer above is nothing but an excuse to defend the SIM, as is the timing of PBP generation as opposed to the result. With 39 seconds left, I want an explanation of what happens the rest of the way... no matter when it was created, and if something happened to re-set the shot clock, it should be in the PBP. No excuses. I would certainly send a ticket in about this.

as for the playing time thing, i looked through the box score and tend to agree that it was a depth chart/one-guy-at-multiple-positions issue. an anomaly, hopefully, but i'd play with my depth chart if i were you, jetsons, and get them straightened out either with someone set to GT or a switch for the 2nd-stringer...


Didn't dismiss it.  Actually said to submit a ticket.  Just think the response as if this sort of thing is something unprecedented that has only occurred since the inception of the new engine is overwrought.

6/24/2010 1:23 PM
123 Next ▸

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.