|
#76
|
||||
|
||||
|
Re: Week 1 Analysis
It seems like gameplay here at Central illinois has been much more violent than in years past. Teams realized when they don't have the ball, you double team on defense until you're open. I hope everyone built a physically strong robot.
|
|
#77
|
|||
|
|||
|
Re: Week 1 Analysis
I think there is a misconception among the "kit bot built to defend" populace that defense equals shot blocking (interfering with the ball trajectory).
Many of these robots would have been better suited to avoid building a 60" tall wall that makes their robot top heavy (and the drivers move it around gingerly), but to instead build a basic kitbot with well mounted battery/electronics/etc, a few pounds of ballast, and just get in the way or hit teams as they try to shoot. I haven't seen many (any?) "swats" of balls. The most effective defense has been pushing a robot as it attempts to shoot and altering the shot trajectory, or knocking it loose. Any team can do this effectively IMO. |
|
#78
|
||||
|
||||
|
Re: Week 1 Analysis
After just finishing watching the 118 vs 148 match, it's very disappointing that the human player can not get a ball until after the ref's light up the post, which takes 10-15 seconds. As soon as a cycle is finished, the alliance should be able to get another cycle started right away.
Also, G40 seems to be the main decider of most of these matches... |
|
#79
|
||||
|
||||
|
Re: Week 1 Analysis
OK, I'm confused. What just happened in the alamo regional?
118 sat there for about 10 seconds before the light on the pedestal lit up, and because of that, they couldn't get another shot in before the match ended. Why didn't the pedestal light up? No balls were on the field. This is looking bad. Bad calls everywhere. |
|
#80
|
||||
|
||||
|
Re: Week 1 Analysis
Another question, what was the field fault (alamo)? I'm watching an ad now.
|
|
#81
|
||||
|
||||
|
Re: Week 1 Analysis
refs declared 2 balls dead and then started another cycle
|
|
#82
|
|||
|
|||
|
Re: Week 1 Analysis
I think too much has been put on the refs this year. I saw several matches where low goal scorers had arms inside the low goal directly in front of a ref. not just in, but like 12-15 inches in and no call. Several long delays on lighting the pedestal after a score, lots of high goal bounce outs, and numerous pickups the in no way were 20" or less outside the frame. I also notice a few games that had scores climbing and climbing when multiple autonomous balls were still on the field. Lots of scoring trouble on top of all that. Several matches where no low goals were scored, but scores were odd numbers.
Overall, I think this game could be great with practice. But, we all might have to wait a few weeks to be truly amazed by it. It will take a lot for teams, refs, and volunteers to get the hang of this one. Even more for everyone to all manage it at the same time. |
|
#83
|
||||
|
||||
|
Re: Week 1 Analysis
I'm see alot of week 1 similarities between this year and 2010. Both were penalties are too large and ruining the game. For the past few years, it was fairly easy to make up a foul. a tech foul was hard, but still very doable. This year, unless you are an AMAZING alliance, making up a foul is difficult, and a tech is almost impossible. I wouldn't be surprised to see an update next tues with some major changes to the ways fouls work, because right now, it seems broken.
Also similar, is making up a deficit is very difficult, and i have seen very very few close matches so far, which is fairly different from what we have seen the past few years. Since most of the 2010 students have graduated, most students dont remember how bad that really was, and I see alot of similarities right now. I hope they can get fixed. Something I would like to see, is that if fouls worked like they used to, and took away from your alliance, how many matches would be 0-0. Also, maybe grab that information from the last 2 years, and check those percentages as well. I think those would be interesting to see. Last edited by Thad House : 28-02-2014 at 19:03. |
|
#84
|
||||
|
||||
|
Re: Week 1 Analysis
Quote:
Quote:
|
|
#85
|
|||
|
|||
|
Re: Week 1 Analysis
Quote:
|
|
#86
|
|||
|
|||
|
Re: Week 1 Analysis
You are right, I wrote too fast for my brain to keep up. But I did notice it happening with defensive bots (that may have sustained a little damage) when trying to pick up a ball by the opponents low goal as well. Not very often, but at least three or four times in all of the matches I saw today.
|
|
#87
|
|||
|
|||
|
Re: Week 1 Analysis
Quote:
Not trying to tell you what you saw, but I thought the same thing for a while until I noticed this. I've actually been pretty ok with the assist scoring so far, the slow cycle restarts are a different story though |
|
#88
|
||||
|
||||
|
Re: Week 1 Analysis
I haven't been able to watch a single match due to my day job. But after reading this entire thread, it really seems like typical Week 1 jitters.
Except for that anti-scoring device behind the goal. That really should be fixed. We spend thousands of dollars per year as an organization on FIRST's partners and I'm sure one of them can sponsor a fix. Last edited by JesseK : 28-02-2014 at 20:28. |
|
#89
|
||||
|
||||
|
Re: Week 1 Analysis
Quote:
|
|
#90
|
||||
|
||||
|
Re: Week 1 Analysis
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|